Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.

Why is my API key not working?

Fixes for invalid key, wrong organization, revoked keys, and missing permissions.

When a key fails, the problem is usually a typo, a revoked key, the wrong organization, or a missing permission. Work through the checklist below before assuming the API is down.

Quick checklist

1. Confirm you copied the full key when it was created. Keys are shown once and start with sk-wl-api01-. 2. Check that the key was not revoked on API keys. 3. Confirm you are using the organization that owns the key. See Which organization does my API key belong to?. 4. Make sure the call includes an Authorization Bearer header with the key. 5. If the error mentions permissions or forbidden, the key may not be allowed to do that action. See What can my API key do?.

Common messages

| What you see | Likely cause | What to try |
| --- | --- | --- |
| Invalid or missing API key | Typo, truncated key, or revoked key | Create a new key and replace it |
| Unauthorized / 401 | Same as above | Confirm Bearer header and key value |
| Forbidden / 403 | Key lacks the needed capability | Use a key from a role that can do that action, or change the integration |
| Too many requests / 429 | Rate limit or free quota | See [Too many requests and rate limits](/help/api/rate-limits-and-429) |
| Payment required / 402 | Billing block or spend limit | See [Payment required messages](/help/account/payment-required) |

Still stuck

Check Service status. If the service looks healthy, send the exact error text and timestamp to [support@worklittle.com](mailto:support@worklittle.com). Do not include the full API key in that email.