Skip to content
Cyoda Documentation
Settings

INVALID_CONDITION — request condition could not be parsed

cyoda-go version 0.8.2

errors.INVALID_CONDITION

Section titled “errors.INVALID_CONDITION”

NAME

Section titled “NAME”

INVALID_CONDITION — a request body condition (AbstractConditionDto) was malformed and could not be parsed.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 400 Bad Request. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Endpoints that accept a search-style condition in the request body — grouped statistics and the conditional form of delete-by-model — reject a body whose condition cannot be parsed. The condition type is unrecognised, a nested clause is malformed, or the JSON does not match the expected condition envelope.

To resolve: correct the condition body to a valid AbstractConditionDto (see cyoda help search).

SEE ALSO

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

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 BAD_REQUEST — 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.

Raw formats

Section titled “Raw formats”