Skip to content
Dashboard
Theme
Theme

parameter_invalid

Developer and IT administrator messages for parameter_invalid.

View Markdown

Since API version 1.0.

Field Value
Type invalid_request
Status 400
Surfaces api
Retryable No

A value in the request is not valid. The message names the field and says what is wrong with it, such as the wrong JSON type or a body that is not valid JSON. param names the field when OhAuthCat knows it.

  • A field has the wrong JSON type, for example a number where the schema expects a string.
  • The request body is not valid JSON, or it was cut off.
  • The body has an unknown field, a duplicate key or trailing data after the JSON object.
  • A value breaks a rule of the operation, such as a length limit or a format.
  • Read message and param, then compare the field with the operation’s schema in the API reference.
  • Send Content-Type application/json and a single JSON object with no trailing data.
  • Use an official SDK where possible; it builds bodies that match the schema.

HTTP status 400 for a body whose name is a number:

{
"error": {
"type": "invalid_request",
"code": "parameter_invalid",
"message": "`name` has the wrong type: expected a string, got a JSON number",
"param": "name",
"doc_url": "https://docs.ohauthcat.com/errors/parameter_invalid",
"request_id": "req_01J9Z3K5V7W8X9Y0Z1A2B3C4D5"
}
}

A value sent isn’t valid; param names its field when it is known

One of the values sent isn’t valid

The hosted portal shows these machine translations, which native speakers have not reviewed yet. Placeholders and identity provider console labels stay in English.

  • de: Einer der gesendeten Werte ist ungültig
  • es: Uno de los valores enviados no es válido
  • fr: L’une des valeurs envoyées n’est pas valide
  • ja: 送信された値のいずれかが無効です
  • pt-BR: Um dos valores enviados não é válido