Skip to content
GitmoapAPIBeta
Schema

ErrorBody

Shape

  • codestringThe coarse category, tied to the status: NOT_FOUND, CONFLICT, INSUFFICIENT_SCOPE. Every error has one; the API reference's error catalogue lists them all.
  • messagestringWhat went wrong, for a person. Written to be read, not parsed: match on reason or code.
  • fieldstring or nulloptionalOn a 400 that refused one field's value, the field, as its JSON path: email, items[0].name. Put the message under that input. Absent on every other error.
  • reasonstring or nulloptionalThe specific code, when the error has one: LAST_ORGANIZATION_OWNER, BRANCH_PROTECTED. The message starts with it too. Match on this when it is present, and on code otherwise.
  • required_scopestring or nulloptionalThe scope the access token was missing, on INSUFFICIENT_SCOPE.
  • violationsanyoptionalPresent on the structured-validation errors (PROVIDER_VALIDATION_FAILED per-node, PIPELINE_VALIDATION_FAILED DAG): a JSON array of the offending elements, so a caller can fix every one in a single round-trip. Absent (omitted) on every other error.

Example

Synthesized example
{
"code": "code-b5da",
"message": "Pin a page's payload to the build that rendered it",
"field": "field-0b20",
"reason": "reason-2b11",
"required_scope": "required-scope-789f",
"violations": null
}

Graph

Used inside
Contains

No named schema inside.

Used by

Sent by 0 operations

No operation takes it as a request body.

Returned by 0 operations

No operation returns it directly.