parameter_missing
HTTP 422, type invalid_request_error.
A field this endpoint requires was not in the request.
Why it happened
The same rule as an unknown field, in the other direction: the request shape is checked rather than guessed at. A missing required field has no safe default we could supply on your behalf.
The param in the error names the field.
How to fix it
Add the field named in param and send the request again. If you are sure you sent the field, check that Content-Type is application/json: today a JSON body sent as text/plain is not reliably read as JSON: on some endpoints its fields are reported missing, and on others it is accepted.
{ "error": { "code": "parameter_missing", "param": "amount" } }
It is safe to retry with the same Idempotency-Key after adding the field: a request refused for
its shape is refused before the key is claimed, and it never reached a provider. If the missing
parameter is the Idempotency-Key header itself, there was no key to reuse: add one.
Related codes
parameter_unknown-- a field we do not define