invalid_request_parameter
Error cause indicating one or more request parameters contain invalid values that violate format, type, or business logic constraints.
What this means
The parameter you provided exists in your request and is recognized by the Commerce API, but its value doesn't meet the endpoint's validation requirements. This is the most common error cause you'll encounter during integration. Validation failures can occur for many reasons: the value is out of the acceptable range (like page_number: 50 when the maximum is 10), the format is incorrect (a malformed email address or invalid currency code), the type doesn't match expectations (providing a string where an integer is required), or the value violates business logic (attempting to pay an order that's already completed).
For example, scheduling a payout with currency: "XYZ" where XYZ isn't a supported currency code, or paying for an order with a payment_method_id that has been deleted. The error detail field provides specific information about what's wrong with the parameter and what constraints it violated, enabling you to correct the value and retry successfully.
Example error response
{
"error": {
"type": "invalid_request_parameter",
"cause": "invalid_request_parameter",
"code": "1528",
"message": "payment method not found",
"detail": "The payment method `pm_xyz789` does not exist or does not belong to your application. Verify the payment_method_id is correct.",
"fix_code": "change_request_parameters",
"url": "https://commerce.zebo.dev/e/1528"
}
}
Related errors
- invalid_request_parameter - Error type for this cause
- change_request_parameters - How to fix
- missing_request_parameter - Related validation issue