API reference

API keys

POST/api/v2/api-keys

Manage API keys from code, for example to give each of your servers its own key. All three endpoints need a full access key.

Create a key

POST /api/v2/api-keys

FieldDescription
nameRequired. Up to 100 characters, for example Production web server.
permissionfull (default) or sending.
modelive (default) or test.
domain_idOptional. Limit the key to one sending domain (its id from Domains).
curl -X POST https://robustemail.com/api/v2/api-keys \
  -H "Authorization: Bearer $ROBUSTEMAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "Web server", "permission": "sending", "mode": "live" }'
{
  "id": "6ad9a0c1e2f34",
  "token": "rb_live_..."
}

The token is returned only once. Store it straight away.

List keys

GET /api/v2/api-keys returns your active keys. Tokens are never returned, only their first characters:

{
  "object": "list",
  "data": [
    {
      "object": "api_key",
      "id": "6ad9a0c1e2f34",
      "name": "Web server",
      "token_prefix": "rb_live_a1b2c3",
      "permission": "sending",
      "mode": "live",
      "domain_id": null,
      "last_used_at": "2026-10-25T09:30:12+00:00",
      "created_at": "2026-10-01T08:00:00+00:00"
    }
  ]
}

Revoke a key

DELETE /api/v2/api-keys/{id}

curl -X DELETE https://robustemail.com/api/v2/api-keys/6ad9a0c1e2f34 \
  -H "Authorization: Bearer $ROBUSTEMAIL_API_KEY"
{ "object": "api_key", "id": "6ad9a0c1e2f34", "deleted": true }

Requests made with a revoked key fail with 403 invalid_api_key.