Deleting Objects

Deletes Cascade

When deleting an object on the MX platform, all objects belonging to that object are also deleted in a cascading fashion. For example, deleting a member deletes not just the member, but all associated accounts, transactions, holdings, etc. Deleting a user also deletes all members associated with it, and so on.

warning

Deleting a user is permanent. Deleted users can never be restored.

Soft Deletes and Purges

Deleted objects are "soft-deleted" first and later purged. The timeframe for purging objects is roughly two weeks, with the exact time depending on technical factors.

A soft-deleted object cannot be explicitly restored via API, but MX may restore a soft-deleted member in some cases.

Purged objects can never be restored.

Restoring Soft-Deleted Members

When a member (either OAuth or Non-OAuth) is deleted, it goes into a soft-deleted state. If a new member is created for the same user, on the same institution, and utilizing the same credentials, the soft-deleted member is purged, and the new member is created.

Once a member has been fully purged, it cannot be restored. To restore a soft-deleted member, a client must contact support prior to it being purged.

When a PENDING OAuth member is deleted by MX, it’s immediately purged and cannot be restored. When an OAuth member in any other state is deleted, it will be soft-deleted and can be restored.

User Deletes are Permanent

Deleting a user is permanent. Deleted users can never be restored.

Blocked Accounts

Blocking an account soft deletes the account, but immediately and permanently deletes all data belonging to the account, in other words all transactions, holdings, statements, etc.