Ticketmaster provides access to the Partner API to a select number of partners, for specific use cases. If you have already been given access to the Partner API by the Distributed Commerce team, please see below for some commonly asked questions.
How can I integrate and test the Partner API? Why am I getting 4XX and 5XX errors? Can the API handle concurrent calls? What are “Channel Partners”?
Why am I not seeing my expected events at /events [GET]?
How frequently does polling occur?
Why is the “onsale” key not found for an event in the event details response?
Why does Event availability return 4XX errors? Why does Availability endpoint return 5XX errors?
Why am I receiving the error “No inventory found”? Why can I not reserve a cart even though inventory is available?
Why am I getting “TAP returned unknown error” when adding payment details? Can I send an un-encrypted credit card number and security code when adding payment? When adding billing info to a cart, can we specify the test credit card info in the docs without encrypting? Do Ticketmaster members have default payment methods defined? What are the valid characters to use for credit card salting?
What shipping options am I required to support?
Why am I getting “Invalid reserve request data structure “ error when attempting to commit a cart?
Why am I not receiving a barcode_id field in the Order details response?
You can use the Test Event ID 000051048D991EE7 in production for making a test purchase. Refer to Ticketmaster Partner API.
Please see Error Responses
The API does not support concurrent calls to any cart end point.
Ticketmaster works with various “channel partners” who contract directly with venues, clients, and promoters to source inventory, sometimes at discounted prices or available for sale exclusively through their own platforms. Ticketmaster provides additional APIs to service their needs and requires specific agreements on usage. Contact Ticketmaster for enabling the following APIs.
Verify with the client/promoter that the inventory is “Internet enabled” and all masks are set up correctly.
Polling can occur when traffic builds up for a particular event or venue. Clients can also be penalized and more frequently polled if their applications leave carts left unpurchased and not deleted if the user abandons the transaction.
Please ensure that you are following our best polling implementation practices as outlined in our developer documentation.
It is an event set up issue . You should follow up with the client to check if the event setup is done correctly.
It can happen due to Quota Policy violation (429 errors). Check if your requests are within the quota limit. The Quota limit variables can be found in the response header. If you are not violating the quota policy, check with our partner support team to investigate the error.
It can happen during niterun, a period when the service is unavailable. It can also be due to overflow of DB storage for atlas. If this is happening on a regular basis, please contact Partner support team.
The event, section, or price level may have sold out. Please use the Event Inventory service to verify availability before displaying event information.
There are a number of potential issues that can be checked and solved for. Example checks include:
Please check all required fields for your payment request. Clients are configured individually for required payment fields. Please contact support for your specific configuration.
NNo. Any credit card information sent to Ticketmaster payment services must be encrypted per our instructions here.
No. The credit card data must always be encrypted.
Members must specify the method of payment for each transaction. See View Member Payment Information to get a list of payment methods they can select from.
The following valid ASCII characters can be used for salting :
"a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,A,B,C,D,E,
F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z,1,2,3,4,5,6,7,8,9,0"
Shipping options vary per event. Make a request to Shipping endpoint [GET] to get valid shipping options for that event.
“Invalid reserve request data structure” error is returned if the request body is not valid or the method specified is not correct. Make sure your method type is PUT and the request body contains the correct cart id.
The event may not be set up correctly to emit barcodes.Please contact the client to verify Event settings.
