Skip to content
Cyoda Documentation
Settings

BAD_REQUEST — malformed or invalid request

cyoda-go version 0.6.2

errors.BAD_REQUEST

Section titled “errors.BAD_REQUEST”

NAME

Section titled “NAME”

BAD_REQUEST — the request body, query parameter, or header is malformed or structurally invalid.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Fired when the server cannot parse or structurally process the incoming request. Common triggers include invalid JSON, missing required fields, unsupported format specifiers, or mutually exclusive parameters being set simultaneously.

Not retryable. The same request produces the same error.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.VALIDATION_FAILED

See also

Section titled “See also”
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help errors VALIDATION_FAILED — Unlike BAD_REQUEST (which covers parse failures), this error is returned when the payload is parseable but violates the registered model schema — for example, a required field is missing, a value is out of the allowed range, or a workflow guard condition is not satisfied. The error detail includes the specific validation failure.

Raw formats

Section titled “Raw formats”