Skip to main content
All API requests are authenticated with API keys. Include your key in the Authorization header as a Bearer token:

Creating an API Key

1

Open Settings

Navigate to Settings → API Keys in your Hado SEO dashboard.
2

Create a key

Click Create API Key and give it a descriptive name (e.g., “CI/CD Pipeline” or “CMS Webhook”).
3

Copy your key

Your full API key is displayed once at creation. Copy it and store it securely — you won’t be able to see it again.
API keys are shown only once at creation. If you lose a key, revoke it and create a new one.

Key Format

API keys use the prefix hado_sk_ followed by 48 hex characters:
The prefix is visible in your dashboard for identification. The full key is never stored — only a secure hash is kept on our servers.

Plan Limits

API access — including the MCP server — is available on every plan. Plans differ by monthly call quota: The key cap is your account’s site capacity plus 8, so extra-domain add-ons raise it automatically (middleware setups use one key per site, and the headroom keeps room for your own keys). The monthly call quota is shared across all of your keys, and only successful requests count against it.
Need a higher monthly limit? Contact support.

Key Scopes

Keys carry scopes that limit what they can do: Pick the permissions when creating the key — choose Read-only for anything you don’t fully control, like AI agents, third-party integrations, and shared scripts. A key without the needed scope gets 403 insufficient_scope. You can also narrow an existing key to read-only from the key list (Make read-only). Permissions only ever shrink: a key can’t regain write access — create a new key instead.

Revoking a Key

You can revoke an API key at any time from your dashboard. Revoked keys immediately stop working and cannot be restored. Create a new key if you need to replace one.

Security Best Practices

  • Never commit API keys to source control. Use environment variables or a secrets manager.
  • Use descriptive key names so you can identify which integration uses each key.
  • Rotate keys periodically — revoke old keys and create fresh ones.
  • Use one key per integration so you can revoke a single key without disrupting other workflows.