This article describes common errors you may encounter when integrating with the SpurrOpen Partner API, along with their causes and recommended resolution steps.
- 401 Unauthorized
Cause:The request is missing a valid authentication token or the token is invalid.
How to fix:Ensure the Authorization header is included with every request using the format Authorization: Bearer YOUR_PARTNER_TOKEN. Verify the token matches the environment being used. - 400 Bad Request
Cause:The request payload is malformed or required fields are missing.
How to fix:Review the request body and confirm all required fields are present and correctly formatted. - 400 Bad Request – Amount Mismatch
Cause:The payment amount submitted does not match the order total calculated by SpurrOpen.
How to fix:Always use the exact total returned from POST /orders/preview when collecting and confirming payment. Do not recalculate totals manually. - 404 Not Found
Cause:The requested resource does not exist or the ID is incorrect.
How to fix:Verify that the event ID, ticket ID, or order ID exists and belongs to your partner account. - 409 Conflict – Order Already Processed
Cause:An attempt was made to confirm an order that has already been confirmed.
How to fix:Confirm each order only once and avoid retrying confirmation unless the order status is unknown. - 409 Conflict – Insufficient Inventory
Cause:Ticket availability changed before the order was created or confirmed.
How to fix:Refresh ticket availability, reduce the ticket quantity, or prompt the customer to select a different ticket type. - Reservation Expired
Cause:The reserved tickets were released because payment was not confirmed within the allowed time window.
How to fix:Create a new order and re-reserve inventory. Confirm payment immediately after a successful transaction. - 500 Server Error
Cause:An unexpected server-side error occurred.
How to fix:Retry the request after a short delay. If the issue persists, contact SpurrOpen support with the error details.
When contacting support, include the endpoint used, request payload, error message, timestamp, and your Partner ID to help expedite troubleshooting.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article