API Key Not Working

Common issues

• Key format: Use the full key, which starts with sf_live_. The dashboard shows only the first few characters, followed by ....
• Authorization header: It must be exactly Authorization: Bearer sf_live_your_key, with a capital B and one space after Bearer.
• Key revoked: Check the API Keys list in Settings > Developer. If the key is gone, create a new one. Keys are removed automatically when the team member who created them is removed from the team or changed to the Editor role.
• Product turned off: Requests to a product that's turned off return 403 with a message such as ChangeForge is disabled for this account. Turn the product on in Settings > Products & Plans.
• Plan downgraded: Existing keys keep working after a downgrade, and keys never expire. You need a Pro plan only to create new keys.
• Rate limited: A 429 means you sent too many requests. See API Rate Limits.

Testing your key

Try a simple GET request:

curl -H "Authorization: Bearer sf_live_your_key" \
  https://statusforge.net/api/settings

A working key returns your account details as JSON, including your account name and slug. This works for every account, whichever products you use. A 401 with {"error":"Unauthorized"} means the key is wrong, was revoked, or the header is malformed.