StatusSupportGet API keyDashboard
AccountDelete the account (after a grace period)

Account

Delete the account (after a grace period)

Use with AI

DELETE /v1/account

Locks the account at once (every key revoked, the owner's sessions ended, jobs and webhooks stopped) and deletes it for good after grace_s (7 days), unless its owner signs in again and chooses it; unspent credits are forfeited. Its people on other accounts stay on those. The owner only, with a fresh sign-in. Free.

Auth: the dashboard session cookie.

Example

cURL
curl -X DELETE 'https://socialtap.dev/v1/account' \
  -H "x-api-key: $SOCIALTAP_API_KEY"

Authorizations

The dashboard's session cookie, not an API key.

Response

application/json

202

Delete the account (after a grace period)

dataobject
ShowHide 5 child fields
account_idstring

The account being deleted.

credits_forfeitedinteger

The balance when the deletion was asked for: forfeited, with no refund, when the account is deleted.

deletes_atstring date-time

When the account is deleted for good, unless its owner signs in before then (which cancels the deletion), RFC 3339 UTC.

objectstring

Always account_deletion.

One ofaccount_deletion

requested_atstring date-time

When its deletion was asked for, RFC 3339 UTC.

metaobject

The shared route meta (see the API reference introduction).

401

401 Unauthorized.

unauthorizedNo retry

The x-api-key header is missing, or its key is unknown or revoked. On the dashboard's routes: the session cookie is missing or expired.

Send a valid API key in the x-api-key header. No key yet? A person gets one at details.signup_url; an AI agent follows details.agent_auth_url.

403

403 Forbidden.

forbiddenNo retry

The API key is valid but may not make this request, and details.reason says why: the account is suspended, the key lacks the route's scope, waits for its owner to confirm it by email, has expired, or was used from an IP outside its allowlist, or a rotated key's previous secret was used for a call that needs the admin scope. A running job stops with it too when its account is suspended or the key that created it is revoked or expires. It is about the key, never the item: a private item is private_or_unavailable, also 403, so branch on the code.

Act on details.reason. suspended: contact support. scope: use a key with details.required_scope. previous_secret: use the new secret. key_pending: have the owner open the emailed link. key_expired or key_revoked: create a new key. ip_not_allowed: call from an allowed IP.

429

429 Too Many Requests.

rate_limitedYes, later

The account passed its runaway-protection ceiling: a high per-account limit that stops a broken client loop (plans have no rate limit). Requests without an API key (signup, the MCP server's tool listing and find_endpoint) are limited per IP address instead. It also stops an account whose failed requests in the last hour cost far more than its successful ones paid for: failures are free within a limit (the message says so), and successes raise it.

Wait the seconds in the retry-after header, then retry. If your steady traffic needs more, ask support to raise the ceiling; without an API key, send one.

operationId account.delete