Skip to main content

Errors

Every v1 API error comes in the same envelope:

{
"error": {
"code": "INSUFFICIENT_SCOPE",
"message": "This token was not granted write access to this resource.",
"details": { "required": ["write", "all"], "granted": ["read"] }
}
}

Compare code, which is stable. message is for people and may change. details appears when there is something to detail.

Codes​

StatuscodeWhen
400VALIDATION_ERRORinvalid body, filter, sort or cursor
401INVALID_TOKEN, INVALID_AUDIENCE, INVALID_ISSUER, TOKEN_EXPIRED, TOKEN_REVOKEDaccess token problem (Authentication)
403UNKNOWN_ORGANIZATIONthe token's organization is not in Kadu
403INSUFFICIENT_SCOPEthe token lacks the route's scope (Permissions)
403USER_PERMISSION_DENIED, NOT_A_MEMBERthe role of the token's person does not allow it
403FEATURE_NOT_ENABLEDKobana has not enabled this operation for the organization
403ENTITLEMENT_REQUIREDrun without Kadu in the organization's plan
404NOT_FOUNDthe resource does not exist, was removed or belongs to another organization
409CONFLICTstate conflict (for example, environment name already in use)
409IDEMPOTENCY_KEY_REUSED, IDEMPOTENCY_REQUEST_IN_PROGRESSsee Idempotency
413PAYLOAD_TOO_LARGEbody above 1 MiB
422MISSING_SECRETSrun with required secrets that have no value in the environment
422ENVIRONMENT_REQUIREDrun without a valid environment
422COST_LIMIT_REACHEDthe organization reached the monthly cost cap
429RATE_LIMITEDrequest limit (Limits)
500INTERNAL_ERRORour failure. The message never carries internal details.
503AS_UNAVAILABLEtoken verification is unavailable. Try again after Retry-After.

Besides these, a route may return its own code, documented in its reference.

What to do​

StatusRetry?
4xxNo: the same request will fail again. Fix the cause.
409 IDEMPOTENCY_REQUEST_IN_PROGRESSYes, after a few seconds, with the same key.
429Yes, after Retry-After.
5xxYes, with increasing wait and the same X-Idempotency-Key on writes.

The run endpoint uses the same envelope, with the lowercase codes listed on its page.