Public APIError codes
Public APIError codes
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.
- HTTP status: 400
- Problem type URI: https://nowgetitdone.com/docs/api/problems/validation-failed
What it means
The request body or query failed schema validation. The errors array names each offending field by JSON Pointer.
Likely causes
- A required field was missing or had the wrong type.
- A value fell outside its allowed range or enum.
- A cursor was reused with different filters than the page it came from.
How to fix
- Read the
errorsarray — each entry has apointer, acode, and amessage. - Fix the named field and retry. The request was never applied, so retrying is safe.
Example problem+json
{
"type": "https://nowgetitdone.com/docs/api/problems/validation-failed",
"title": "Request validation failed",
"status": 400,
"code": "validation_failed",
"request_id": "req_a1b2c3d4"
}Related
Read this page as Markdown — plain text for AI agents. Every guide at once: llms-full.txt.
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.
resource_not_found (HTTP 404)
resource_not_found (HTTP 404) from the GetItDone API: No resource with that id exists inside the credential’s organization.