Skip to main content

parameter_unsupported

HTTP 422, type invalid_request_error.

The parameter is part of the published contract, but this endpoint does not honour it yet.

Why it happened​

The field is valid and the request is well formed, but the endpoint does not act on it yet, so it is refused by name rather than ignored. Today this code is raised for body fields, on POST /payments and POST /checkout_sessions. Unimplemented query parameters on list and retrieve requests are handled differently, and not the same way on every request: These requests refuse them with parameter_invalid: ending_before and expand[] on GET /payments, GET /checkout_sessions and GET /customers; expand[] on GET /customers/{id}; limit, starting_after and ending_before on GET /payments/{id}/attempts; and ending_before on GET /events. These requests do not read them today, so they have no effect: limit, starting_after and ending_before on GET /payments/{id}/refunds; ending_before and expand[] on GET /payment_instruments, GET /plans, GET /subscriptions and GET /subscriptions/{id}/billing_cycles; and expand[] on GET /payments/{id}, GET /checkout_sessions/{id}, GET /payment_instruments/{id}, GET /plans/{id} and GET /subscriptions/{id}.

How to fix it​

Remove the field named in param and send the request again. If you depend on it, contact support to ask when it will be available.

Retrying: retry only after fixing the request, by removing the field named in param. This request is refused before its Idempotency-Key is claimed, so send the corrected request with the same Idempotency-Key.