Trash

List items in the trash

platform.trash.list

Lists what was deleted in the last 30 days and can still be restored, from any module (CRM deals, persons, companies, prospects, activities, pipelines, custom fields; tasks, projects, forms, campaigns and every entity whose delete keeps a copy), newest first. Use it to find something deleted by mistake before restoring it with platform.trash.restore. Only owners and admins can see the trash. Expired and already-restored items are not listed. Filter by module (the module that owns the record: crm, task_management, web_forms…) and/or by entity_type to narrow it. A record that lives under another one (a comment, a keyword, a campaign row of a plan, a reply) says whether that parent is still there: parent_trash_item_id when it is in the trash too (restore that one first), restorable: false with not_restorable_reason parent_gone when it is gone for good. Module: Organization (organizations), even though the id starts with platform.; any valid credential can read it. With Google Ads, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted, and their records are left out of the response (the permissions guide lists what each platform allows).

Scope

organizations:read

Permission

View the module · Only owner, admin

MCP tool

platform_trash_listOn the full surface; on the compact one, mb_execute_operation with id: "platform.trash.list".

Declared cost: up to 1501 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/trash" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/trash" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Restore an item from the trash

platform.trash.restore

Restores a deleted record from the trash to the place it was deleted from, together with anything a cascade deleted with it. Name it by item_id (the trash_item_id its deletion returned, or the id of platform.trash.list; in REST it goes in the path) or, through the MCP, by entity_type + entity_id (what it was and the id it had: its newest copy in the trash). If the original id is already taken by a newer record, the item is restored with a new id (restored_as_new_id). A person is re-linked to the deals and lists they were removed from, and a label goes back on the records that had it: relinked counts them. When the copy could not keep everything (linked_truncated in platform.trash.list), only part of it comes back and the response says linked_truncated: true. Fails if the item expired, was already restored, or is not restorable (trash_item_not_restorable, details.reason: merged or reference_only), and with 409 before writing anything when bringing it back would clash with what exists now (trash_restore_parent_missing when what it belonged to is gone: details.parent_trash_item_id names the trash item to restore first, and details.parent_restorable: false means it cannot come back, so neither can this one; lead_source_exists when the WhatsApp line of a lead source already has another active source). If the record came back but something after it failed (a linked record or a module side effect), the response says partial: true with how many linked records came back; the item is not reopened and the failure is reported to MB Suite. Owners and admins only; the caller (and the credential) also needs write access to the module the record belongs to. Module: Organization (organizations), even though the id starts with platform.; the credential needs the write scope of the module that owns the record (for example crm:write for a deal). With Google Ads, Google Business Profile, LinkedIn, TikTok or YouTube, their terms limit it through the API and the MCP: what they do not allow answers 403 platform_terms_restricted (the permissions guide lists what each platform allows).

Scope

organizations:write

Permission

Edit in the module · Only owner, admin

MCP tool

platform_trash_restoreOn the full surface; on the compact one, mb_execute_operation with id: "platform.trash.restore".

Declared cost: up to 160 reads and 5160 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/trash/{item_id}/restore" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X POST "https://api.mb-suite.com/v1/trash/{item_id}/restore" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Permanently remove an item from the trash

platform.trash.purge

Deletes the trash copy for good, before the 30-day window ends, together with what the delete had kept aside for the restore (the items and views of a project, the comments of a task, the stored file of a Media Library item, the knowledge files of an AI agent). Use it only for a legal or privacy request (the data must not be recoverable). Irreversible: there is no copy after this. Owners only; the caller and the credential also need write access to the module the record belongs to, and the credential must allow deletion. Outside the screen it requires a dry run and a confirm_token. Module: Organization (organizations), even though the id starts with platform.; the credential needs the write scope of the module that owns the record (for example crm:write for a deal) and permission to delete.

Needs confirmation: first dry_run: true (preview and confirm_token, valid 10 minutes and for one run), then the same body with confirm_token. In a few operations only with certain data: the description says when. Why and how: Dry run and confirm_token.

Scope

organizations:write and “Allow deletions” (organizations:delete in OAuth)

Permission

Edit in the module · Only owner

MCP tool

platform_trash_purgeOn the full surface; on the compact one, mb_execute_operation with id: "platform.trash.purge".

Declared cost: up to 10 reads and 2000 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl -X DELETE "https://api.mb-suite.com/v1/trash/{item_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl -X DELETE "https://api.mb-suite.com/v1/trash/{item_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'