Skip to content
Cyoda Documentation
Settings

BAD_REQUEST — malformed or invalid request

cyoda-go version 0.8.4

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, unsupported format specifiers, a parameter outside its allowed range, and mutually exclusive parameters set together.

A payload that parses and then fails against the registered model is not this code — that is VALIDATION_FAILED, or INCOMPATIBLE_TYPE for a leaf whose DataType does not fit.

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, bad parameters, and unstorable bytes), this error is returned when the payload parsed and then failed against the registered model. On an entity write that means:

Raw formats

Section titled “Raw formats”