Skip to content

Delete Agency Client

Permanently delete a client workspace and its data.

DELETE/api/v1/agency/clients/{client_id}

Requires an API key with the write scope.

Only API keys of an Agency workspace can call this endpoint (403 agency_required otherwise). The call always runs in the key's own workspace; X-Workspace-Id is ignored. Writes also need a key created by the agency workspace owner (403 agency_owner_required otherwise).

This cannot be undone. The workspace is removed with its leads, campaigns, email accounts and every other record. A key cannot delete the workspace it belongs to (400 cannot_delete_own_workspace), and personal workspaces cannot be deleted.

Path Parameters#

client_idstringpathrequired
The client workspace id.

Response#

dataobject
Show data
idstring
The deleted workspace id.
deletedboolean
Always true.

Each delete is recorded as an audit.agency_client.deleted event on the agency workspace before the data is removed.

Errors#

StatusDescription
401Missing, invalid, revoked or expired API key
403API key does not have the required scope: write
400cannot_delete_own_workspace, or the workspace is personal
403agency_required or agency_owner_required
404The workspace is not owned by the agency owner

Rate Limit#

  • 120 requests per minute, shared by every write call in your workspace. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (unix epoch seconds) and X-RateLimit-Bucket (write).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).

For client-side patterns, see Rate Limiting.

Was this page helpful?
View as MarkdownLast updated November 4, 2026