API reference

Error code: invalid_value_type

invalid_value_type returns HTTP 422 with type: invalid_request_error. A field value was the wrong type. Branch on this code — it is stable — and apply the fix below.

2 min read

422HTTP status
invalid_value_typeerror.code
FixHandling

What triggers it

A field value was the wrong type. A nested object or array inside fields, which only accepts scalar values.

Example response

{
  "error": {
    "type": "invalid_request_error",
    "code": "invalid_value_type",
    "message": "A field value was the wrong type."
  }
}

How to fix it

Flatten the value to a string, number or boolean.

This is deterministic: the same request will fail again until fixed. See the HTTP 422 page for the class.

In practice

In a well-built client, invalid_value_type is handled by branching on error.code rather than on the human error.message, which may be reworded over time. The HTTP status (422) gives the broad invalid_request_error class; the code gives the specifics; and, on field errors, error.param pinpoints the input to fix.

This code is deterministic — retrying the identical request reproduces it — so keep it out of your retry path and instead map it to a clear, actionable message. See Map errors to user-facing messages and Read the error envelope for the pattern.

Frequently asked questions

Is invalid_value_type safe to retry?

No. It is deterministic; retrying the identical request produces the identical error. Fix the cause first.

Will this code ever change?

No. Error codes are stable contract. The human message may be reworded, but the code you branch on will not change.

Do I branch on the code or the HTTP status?

Both — the status for the retry-or-not decision, the code for the specific behaviour. See the error envelope.

Funding for UK limited companies

Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.