Parameter rejected

When the ILSA API rejects one of your parameters it will return a HTTP 422 Unprocessable Entity or HTTP 400 Bad Request. The Content-Type of the response is application/problem+json.

We return a HTTP 400 when we think you sent us a bad request that you should not have sent us. We think this is a bug in your application. You should not try to parse the response, because we make no stability guarantees. Please contact us if you feel it is not a bug on your side. If we agree we’ll likely change the response code to 422.

The responses are according to RFC 9457. The type is guaranteed to be stable and for parameter-rejected errors, the parameter will always be set.

This snippets below are examples and not exhaustive.

unknown-postal-code

The postal code given in the _location parameter does not exist in our database. You should handle this and ask your customer for another postal code.

HTTP 422 Unprocessable Entity
Content-Type: application/problem+json

{
    "type": "https://docs.ilsa.cloud/parameter-rejected/#unknown-postal-code",
    "parameter": "_location",
    "detail": "Country code or postal code unknown"
}

invalid-int

The parameter should have been an integer, but we couldn’t parse it as such.

invalid

The parameter was invalid. Depending on the parameter this will be a HTTP 400 or 422.

HTTP 400 Bad Request
Content-Type: application/problem+json

{
  "type": "https://docs.ilsa.cloud/parameter-rejected/#invalid",
  "parameter": "_location",
  "detail": "_location should be 'lat, long' or 'countryCode digits'"
}

duplicate

You passed multiple values for parameter, which doesn’t support that. This is always a HTTP 400.

HTTP 400 Bad Request
Content-Type: application/problem+json

{
  "type": "https://docs.ilsa.cloud/parameter-rejected/#duplicate",
  "parameter": "sales_conditions.pricing.asking.general.in_eur.amount",
  "detail": "range field sales_conditions.pricing.asking.general.in_eur.amount received two filters"
}

unknown-field

You’re trying to filter on or request the dropdowncontents for an unknown field. This is always a HTTP 400.

HTTP 400 Bad Request
Content-Type: application/problem+json

{
  "type": "https://docs.ilsa.cloud/parameter-rejected/#unknown-field",
  "parameter": "general.category",
  "detail": "general.category is not a searchable field in the config"
}

missing

The parameter was required, but not given.

unknown-locale

You should check the locale before passing it to us. This is always a HTTP 400.

unknown-audience

You should check the audience before passing it to us. This is always a HTTP 400.

unknown-region

You should check the region before passing it to us. This is always a HTTP 400.