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.
- HTTP status: 403
- Problem type URI: https://nowgetitdone.com/docs/api/problems/feature-not-enabled
What it means
The operation belongs to a capability the current plan does not include — a PLAN gate, distinct from a used-up allowance.
Likely causes
- Outbound webhooks were called on a Free workspace (they are Pro+).
How to fix
- Upgrade the workspace to a plan that includes the capability.
- Check the operation’s entitlement note on its reference page.
Example problem+json
{
"type": "https://nowgetitdone.com/docs/api/problems/feature-not-enabled",
"title": "Feature not enabled on this plan",
"status": 403,
"code": "feature_not_enabled",
"request_id": "req_a1b2c3d4"
}Related
Read this page as Markdown — plain text for AI agents. Every guide at once: llms-full.txt.
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.
validation_failed (HTTP 400): meaning and fix
Fix: read the errors array, correct each field its JSON Pointer names, and retry safely. validation_failed (HTTP 400) means the request failed schema checks.