Page Comparison

...

hidden	true
id	api_docs_current_version

...

This page will show a few common examples of errors provided by the Ticket Evolution Orders Endpoint Error Messages

...

Long Description

These responses will help you understand order creation errors so you can properly message consumers on your website.

Generally speaking, HTTP status codes are used appropriately for each response.

...

Sometimes attempting to create an order will error. Here are some common reasons, the responses and suggested courses of action.

Problem	Code	Response Body	Suggested Action
Tickets No Longer Available	422	`["OrderIntegration::Error::NotFound", "OrderIntegration::Error::NotFound"]` or `["OrderGroup::Builder::NoTickets", "OrderGroup::Builder::NoTickets"]`	Redirect customer to the Event landing page with a message to select a new set of tickets.
Submitted Price Is Too Low (Usually because price was increased before checkout was completed.)	422	`["OrderGroup::TicketPriceError", "Ticket Group: Ticket Price:1677.0, Buy Price:1222.0"]`	Redirect customer to the Event landing page with a message to select a new set of tickets.
Order Timed Out	422	`["OrderIntegration::Error::ConnectionTimeout", "Connection Timeout"]`	This can happen when the inventory is on Order Integration and the seller’s API did not respond in time. Make a `GET /ticket_groups/1234567` to verify the inventory is still available, the quantity desired is still in the `splits` array and that the price has not increased. If all of those are true then re-submit the order. If not, redirect customer to the Event landing page with a message to select a new set of tickets.
Invalid Quantity Requested	422	`["OrderLink::InvalidTicketSplit", "Error performing ticket split, valid quantity values include`

...

X,Y, not Z"]

Either the order was submitted with a quantity that was not in the ticket_group’s splits array OR there are a different number of tickets available now vs when checkout started.

Redirect customer to the Event landing page with a message to select a new set of tickets.

Incorrect Delivery Specified

422

["OrderGroup::Builder::GeneralError", "Ticket group format is

...

XXXXXXX, but the specified delivery type is

...

`YYYYY."]`	Refer to the table on 08. Event Landing Pages to see which `shipment.type`s are allowed with each `ticket_group.format`
Not Enough EvoPay Available	422	`["EvopayTransaction::BalanceTooLow", "EvopayTransaction::BalanceTooLow"]`	Replenish your EvoPay balance.
Credit card Issues	422	`["BraintreeManager::BraintreeError", "CVV not verified Postal Code not verified Street Address not verified"]`	The customer’s credit card did not pass validation. Redirect customer to the checkout with a message to input correct credit card and billing information.
		`["OrderGroup::Manager::PaymentError", "(Status 402) (Request req_a9w6MIBQk369ei) Your card has insufficient funds."]`	Redirect customer to the checkout with a message to use a different credit or debit card.
		`["OrderGroup::Manager::PaymentError", "2014: Processor Declined - Fraud Suspected"]`
		`["OrderGroup::Manager::PaymentError", "2038: Processor Declined"]`	Redirect customer to the checkout with a message to use a different credit or debit card.
		`["OrderGroup::Manager::PaymentError", "2001: Insufficient Funds"]`	Redirect customer to the checkout with a message to use a different credit or debit card.
		`["OrderGroup::Manager::PaymentError", "2000: Do Not Honor"]`
Configuration problem	422	`["OrderGroup::Builder::InvalidSellerId OrderGroup::Builder::InvalidSellerId"]`	Contact us to make sure you are using the correct `seller_id`

Versions Compared

Old Version 1

New Version Current

Key

Long Description