InvalidRequest

Andromeda answers 400 with the problem type https://uri.etsi.org/ngsi-ld/errors/InvalidRequest. The request can't be parsed as the operation defines it. The problem is the framing around your data, not the data itself, so fix the framing and send the same data again. The specification defines this type and binds it to 400.

When this comes back

• The body isn't valid JSON, trailing content after the value included, or an empty array stands where the operation needs a body. See Request bodies.
• An object names the same JSON member twice, in any request body. JSON leaves the meaning of a repeated name undefined, so Andromeda refuses rather than pick one.
• A query parameter is unknown or misspelt, on every endpoint, including those that take no parameters at all.
• An options or format token is unknown, valid only on another operation, repeated, or in conflict with another, as in normalized,concise. See Query parameters.
• A parameter depends on another one the request lacks, or contradicts it, such as aggrMethods without aggregatedValues, joinLevel without join, or type=* with local=false.
• Content-Length is malformed or zero. A missing Content-Length gets a bare 411 with no body instead.
• A structured body carries a member the specification doesn't define for it, such as in the Query body, a Snapshot or EntityMap body, or registration management.
• A request made under an Entity map uses filter parameters other than those of the request that created it.

A name in a query parameter that breaks the name grammar, such as attrs=speed-limit, isn't this error. It is BadRequestData, as it is in a body.