Ticketmaster Error Responses

This page outlines common Ticketmaster error codes, their potential causes, and recommended actions. While some errors originate from system-specific behaviours or temporary issues, this guide offers additional insights and context for resolution. Use this as a supplemental guide to troubleshoot and address issues specific to your implementation.

You will find these details as part of API response under PARTNER_ERROR and PARTNER_ERROR_DETAILS fields, as in the example below:

Error Response example
    
{  "error" : {    "code" : "UNAVAILABLE",    "message" : "Partner Error",    "data" : {      "PARTNER_ERROR" : "[TicketmasterAPI] error: httpStatus: 503, errorCode: 503, errorMsg: dc.availability.ismds.error, resp: {\"error\":{\"message\":\"dc.availability.ismds.error\",\"code\":503,\"http_code\":503,\"severity\":\"ERROR\"}}, additionalErr: response status code is 503",      "PARTNER_ERROR_DETAILS" : "ticketmaster.httpStatusCode:503; ticketmaster.errorCode:503; ticketmaster.errorMsg:dc.availability.ismds.error",      "PARTNER_ERROR_INCORRECT_RESPONSE_CODE" : "got 503 Service Unavailable Error, expected one of [200 201]",      "PARTNER_ERROR_RETRYABLE" : "false",      "PARTNER_NAME" : "Ticketmaster"    }  },  "meta" : {    "reqId" : "bde70208eeca08e627ef46e076f9f7ce"  }}
Copy

Similar error responses might appear under different codes or messages because they can occur at various stages or in different stacks within Ticketmaster's system.

Error Code	Error Message	Cause	Action
400	Items in reserve must all be of the same inventory type	Different inventory types (e.g., Standard, Resale, Platinum) in the same reserve request.	Use only one inventory type per reserve request.
400	Json body formatted incorrectly	System overload on the Ticketmaster side.	Allow some time for the Ticketmaster system to stabilize and retry the request later.
400 / 500 / 503	dc.availability.ismds.error	The Ticketmaster system is likely undergoing scheduled maintenance. According to the API reference, maintenance typically occurs between 2–4 AM in the event's timezone but is usually completed sooner. Once the system is back online, you may proceed with your request.	Retry the request after a reasonable wait time or inform the customer that inventory is temporarily unavailable and advise them to try again later. If the issue persists, contact Redeam for assistance, and we will coordinate with the Ticketmaster technical team to resolve it.
400 - 10002	Event capacity reached, your order cannot be processed	Total number of tickets available has been exceeded.	Inform the end user of capacity limits.
400 - 10161	Ticket limit reached error	It is a fraud prevention measure by Ticketmaster. This can occur if the same guest details are used for multiple bookings and if the number of guests reach the maximum allowed per customer (whether with single or separate bookings).	This error is a fraud prevention measure by Ticketmaster. It can occur if the same guest details (e.g., phone number, email) are used for multiple bookings, or if the data provided is invalid or improperly formatted. Recognize that Ticketmaster has blockers in place to prevent ticket abuse by customers making repeated purchase attempts. Review booking practices to avoid triggering these controls. Ensure the phone number field is valid. If no valid phone number is available, leave the field empty rather than using default or placeholder values. Be aware that the Ticketmaster system removes non-alphanumeric characters from these fields, and if the resulting value is empty, the booking will fail. If attempting a test booking, use a different phone number and email address than those used in previous test bookings.
400 - 20009	Cart cannot be completed until balanced	Price changes or discrepancies during hold and booking.	Verify the price details and retry the request. If the issue persists, contact Redeam for further assistance.
400 - 20052	No inventory found to match request	Requested inventory is no longer available or restricted (e.g., leaving single seats). Can also occur if the number of available continuous seats cannot be fulfilled.	Verify availability before placing holds. We recommend performing a last-minute availability check and reviewing the `restrictSingle` flag, which indicates that no single seats can be left unoccupied.
400 - 20118	Customer information data rejected	Invalid customer data, such as missing alpha characters. Ticketmaster's system removes non-alphabetic characters, and if the remaining value is empty, the booking request will fail at one of its validation steps. Fail example: "last_name": ".323$^!@%" Success example: "last_name": ".323$^!@%J",	Ensure customer fields contain valid characters.
400 - 20228	Reserve request not processed	From past experiences, this error occurs due to Ticketmaster's rules for validating tickets added to the cart. For example, child tickets cannot be sold without accompanying adult tickets. These validation rules are controlled entirely by Ticketmaster, and Redeam does not have visibility into their specific implementation or when they change.	If this error occurs, it may indicate a change in Ticketmaster's validation rules. Contact Redeam to investigate and coordinate with Ticketmaster to address the issue.
400 - 20231	Inventory authorization failure due to limit violation	Misconfigured ticket types or exceeding cart limits.	Review ticket configurations and ensure compliance with Ticketmaster's and Redeam rules.
403 - 20200	A form of delivery must be selected to complete purchase	This error may occur when Ticketmaster's system is unable to process a booking flow request in time before the subsequent request is made. If required information is not processed and attached promptly, the subsequent request may fail. This is typically due to processing delays on Ticketmaster's side.	Keep trying the request to see if it gets processed successfully. If the error occurs frequently, report the issue to Redeam for further assistance.
404	Order Not Found	Region-specific configurations or incorrect lookup method.	Contact Redeam for assistance, and we will coordinate with the Ticketmaster technical team to address the issue.
404	dc.availability.canceled	Event has been marked as canceled.	Inform the end user that the event has been canceled and the product is no longer bookable.
500	Unresponsive system	High traffic during major events or system maintenance. Ticketmaster has confirmed that this issue can sometimes occur due to high volumes of users purchasing tickets simultaneously, particularly during the sale of tickets for major artists' concerts or other high-demand events.	Allow some time for the Ticketmaster system to stabilize and retry the request later.
500 - 10000	Unknown error occurred	Generic error caused by system changes or updates.	Contact Redeam for assistance, and we will coordinate with the Ticketmaster technical team to address the issue.
500 - 20002	General uncoded system error	System outage.	Allow some time for the Ticketmaster system to stabilize and retry the request later.
500 - 20226	Command not processed	High system load on Ticketmaster’s side.	Allow some time for the Ticketmaster system to stabilize and retry the request later.
500 - 20257	ATLAS load error	System load prevents ticket visibility, although the booking is confirmed. This error indicates that the booking was successfully confirmed on Ticketmaster's side but failed to return their "Order Management" response. This prevents Redeam from receiving the tickets for the booking.	If you encounter this error, please report it to Redeam for further investigation and coordination with Ticketmaster to confirm bookings and monitor for potential duplicates.

Last updated on

Was this page helpful?