Delete the account (after a grace period)

Locks the account at once (every key revoked, every session ended, jobs and webhooks stopped) and deletes it for good after grace_s (7 days), unless its owner signs in again; unspent credits are forfeited. The owner only, with a fresh sign-in; the account guide has the details. Free.

Auth: the dashboard session cookie.

Example

cURL

curl -X DELETE 'https://staging.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)

Field	Type	Description
`data`	`object`
`data.account_id`	`string`	The account being deleted.
`data.credits_forfeited`	`integer`	The balance when the deletion was asked for: forfeited, with no refund, when the account is deleted.
`data.deletes_at`	`string` (date-time)	When the account is deleted for good, unless its owner signs in before then (which cancels the deletion), RFC 3339 UTC.
`data.object`	`string`	Always account_deletion. One of `account_deletion`
`data.requested_at`	`string` (date-time)	When its deletion was asked for, RFC 3339 UTC.
`meta`	`object`	The shared route meta (see the API reference introduction).

dataobject

Show 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.

Code	HTTP	Retry	Meaning	What to do
`unauthorized`	401	No	The x-api-key header is missing, unknown or revoked (or, on the dashboard's routes, the session cookie is missing or expired).	Send a valid API key in the x-api-key header; without one, get a key at details.signup_url (AI agents: POST details.agent_signup_url).

unauthorizedNo retry

The x-api-key header is missing, unknown or revoked (or, on the dashboard's routes, the session cookie is missing or expired).

Send a valid API key in the x-api-key header; without one, get a key at details.signup_url (AI agents: POST details.agent_signup_url).

403

403 Forbidden.

Code	HTTP	Retry	Meaning	What to do
`forbidden`	403	No	The API key is valid but may not make this request: its account is suspended, its scopes do not include the route, it is waiting for its owner's email confirmation, it is past its expiry, or the request came from an IP its allowlist does not include; or the request used a rotated key's previous secret (or one no longer current) for something that needs the admin scope. A running job stops the same way 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): branch on the code.	Do what details.reason says: if suspended, contact support; otherwise use a key whose scopes cover the route (details.required_scope) or the key's new secret after a rotation, have the owner confirm the emailed link, create a new key, or call from an allowed IP.

forbiddenNo retry

The API key is valid but may not make this request: its account is suspended, its scopes do not include the route, it is waiting for its owner's email confirmation, it is past its expiry, or the request came from an IP its allowlist does not include; or the request used a rotated key's previous secret (or one no longer current) for something that needs the admin scope. A running job stops the same way 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): branch on the code.

Do what details.reason says: if suspended, contact support; otherwise use a key whose scopes cover the route (details.required_scope) or the key's new secret after a rotation, have the owner confirm the emailed link, create a new key, or call from an allowed IP.

429

429 Too Many Requests.

Code	HTTP	Retry	Meaning	What to do
`rate_limited`	429	Yes, later	The account exceeded its runaway-protection ceiling: plans do not limit request rate, but a high per-account safety ceiling stops broken client loops. Support raises it on request. Without an API key (signup, the MCP server's tool listing and find_endpoint), requests are limited per IP address instead.	Wait for the number of seconds in the retry-after header, then retry; ask support to raise the ceiling if your sustained traffic needs more (calls without an API key: use one).

rate_limitedYes, later

The account exceeded its runaway-protection ceiling: plans do not limit request rate, but a high per-account safety ceiling stops broken client loops. Support raises it on request. Without an API key (signup, the MCP server's tool listing and find_endpoint), requests are limited per IP address instead.

Wait for the number of seconds in the retry-after header, then retry; ask support to raise the ceiling if your sustained traffic needs more (calls without an API key: use one).

operationId account.delete