API Reference

Delete API key

DELETE /api-keys/:id — dashboard-only. Keys are revoked in the dashboard; an API key cannot revoke a key.

DELETE/api-keys/:id

Dashboard-only. Keys are revoked on the website. A request authenticated with an API key is refused with 403 dashboard_only — "API keys can only be created, edited and revoked from the MailBlastr dashboard, not with an API key." — no matter what permission that key holds. Revoke a key from the dashboard under API Keys; revocation there is still immediate.

This is a breaking change. Automation that used to revoke keys with a full_access key now receives 403 dashboard_only. If you suspect a key is compromised, sign in and delete it from the API Keys screen — that is the fastest path, and it takes effect on the key's next use. The official SDKs deliberately expose no method for this endpoint.

Revokes an API key immediately. The key stops working on its next use. The reference below describes the request the dashboard makes on your behalf with a signed-in session — it is not callable with an API key.

Path parameters

idstringrequired

The API key ID as returned by `GET /api-keys` — a numeric string (e.g. 1042), not a UUID. A non-numeric id returns not_found (404).

Response

{
  "object": "api_key",
  "id": "1042",
  "deleted": true
}

Response to an API-key caller

{
  "statusCode": 403,
  "name": "dashboard_only",
  "message": "API keys can only be created, edited and revoked from the MailBlastr dashboard, not with an API key."
}

Errors: dashboard_only (403) for every API-key caller — this check runs before the key is looked up; not_found if the key does not exist or is not yours.