Public APIError codes
Public APIError codes
insufficient_scope (HTTP 403)
insufficient_scope (HTTP 403) from the GetItDone API: The credential is valid but was not granted a scope this operation requires.
- HTTP status: 403
- Problem type URI: https://nowgetitdone.com/docs/api/problems/insufficient-scope
What it means
The credential is valid but was not granted a scope this operation requires.
Likely causes
- The API key was minted without the needed scope (e.g.
tasks:write). - An OAuth grant requested read scopes only, then attempted a write.
How to fix
- Re-mint the API key with the scopes the operation lists under “Required scopes”.
- For OAuth, request the missing scope during authorization.
Example problem+json
{
"type": "https://nowgetitdone.com/docs/api/problems/insufficient-scope",
"title": "Insufficient scope",
"status": 403,
"code": "insufficient_scope",
"request_id": "req_a1b2c3d4"
}Related
Read this page as Markdown — plain text for AI agents. Every guide at once: llms-full.txt.
invalid_token (HTTP 401)
invalid_token (HTTP 401) from the GetItDone API: An OAuth 2.1 access token was supplied but is expired, malformed, or revoked.
feature_not_enabled (HTTP 403)
Fix: upgrade the workspace to a plan that includes the capability (webhooks are Pro+). feature_not_enabled (HTTP 403) is a plan gate, not a used-up allowance.