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?

Fix invalid, revoked, wrong-organization, and under-permissioned keys.

Key failures are almost always a typo, a revoked key, the wrong organization, or a missing permission.

Checklist

1. Confirm you copied the full key. Keys start with sk-wl-api01-. Copy it again from API keys with the copy icon next to the key. 2. Check that the key was not revoked on API keys, and that its Expires date has not passed. An expired key gets "This API key has expired". Create a new key, or run worklittle login again if the CLI made it. 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 is not allowed to do that action. See What can my API key do?.

Error messages

| Message | Likely cause | Fix |
| --- | --- | --- |
| Invalid or missing API key | Typo, truncated key, or revoked key | Create a new key and replace it |
| Unauthorized / 401 | Same as above | Confirm the 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 failing

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.