HOWTO: Automate TEvo Order Processing
- J Cobb
Getting Notified of New Orders
There are multiple ways to know about new TEvo orders and they should all be used together.
Order Integration
Order Integration provides the best experience for buyers because it allows them to know immediately that the tickets they are purchasing have been secured.
With Order Integration at the time an order is being placed our servers will make an API request to your servers to verify the inventory is available and request a hold for a specified quantity of a ticket group. After receiving a successful hold response we will make an invoice request to tell you a TEvo order has been created and you should invoice those tickets to us. In rare cases of an issue on our side you may receive a hold release instead of an invoice request.
If we do not receive a successful hold response the purchaser will be alerted and no order will be created by TEvo.
Not all buyers buyers purchase via Order Integration so even if you support Order Integration you should support Webhooks as well.
Learn more at Processing Orders via Order Integration.
Webhooks
Webhooks are the fastest and least resource intensive way for you to know when a new order has been placed for your tickets. When a buyer submits an order to TEvo we will send a webhook to a URL you provide to alert you that a new order for your tickets has been created.
We also provide webhooks for many other operations including ones where you are the buyer.
Learn more at Processing Orders via Webhooks.
Polling
Polling our API for new orders is recommended only as a fail-safe to webhooks.
Learn more at Processing Orders via Polling.
Differentiating Order Types
Sales to TEvo
Sales where TEvo is the buyer are the most common type of sales you can expect to see. These sales can be identified by examining the order in the body for buyer.type=Office & buyer.id=6.
Sales to a Client
If a seller has a website powered by the TEvo API or they utilize Core to create sales to Clients then any sale where tickets are being sold their client can be identified by examining the order in the body for buyer.type=Client.
When invoicing these sales you should search the Point of Sale for a customer matching the Client. If no matching customer is found then one should be created using the buyer information before creating an invoice selling those tickets to the client.
Be aware of the fraud_check_status of sales to a Client
If a sale to a Client has fraud_check_status of null then that seller does not use Riskified.
If a sale to a Client has fraud_check_status of pending then we are awaiting an approval or detail from Riskified. Riskified will send TEvo periodic updates, each one of which will trigger a webhook with recipient=seller & event_type=fraud_response_received. The sale should not be accepted or invoiced until one is received where the fraud_check_status=approved.
Accepting an Order
When you accept an order you are committing to providing the requested tickets.
Before accepting an order you need to confirm in your system:
You should ensure the requested
quantityis availableThe
pricesupplied is acceptable to you
In the example below be sure to replace {order_id} in the URL with the id of the order (not the id of the item). Also, use the id of the User that was given to you as the reviewer_id.
curl -H 'X-Token: FsxRk6qxJgVn6qzsgPQznyvVNykPwd22' \
-H 'X-Signature: RFajHc97ooCUqQUAPPXVAmrapqVnunmcLFZP4a8ZVHJs' \
-H 'Accept: application/json' \
-d '{"reviewer_id":{reviewer_id}}' \
--url 'https://api.ticketevolution.com/v9/orders/{order_id}/accept'Fulfilling Orders
Mobile Tickets
Learn more at Automate Mobile Transfers.
Etickets (Print at Home or QR codes)
If you have confirmed—either manually or via the API—an order where one or more of the items has a value of true for eticket_delivery then you can deliver those tickets via the API.
With our API you can either deliver etickets either as one file per page or as one single file that includes all and only all of the requested tickets. > If you have a PDF file that has more tickets than you need to deliver you will need to split that file first or manually upload those tickets and choose the pages to deliver.
Delivering Separate Files for Each Page
Use the Items / Add Etickets endpoint to upload individual files for each ticket. You can send all the files in an array in a single POST or you may POST them one at a time, or a combination of the two.
In the example below the item_id is the property named id from the item within the order, not the order_item_id.
curl -H 'X-Token: FsxRk6qxJgVn6qzsgPQznyvVNykPwd22' \
-H 'X-Signature: Lyu2RxCtxYNZvJJXwDQbquoCcHB3gchHJWpaKkB6KBjk' \
-H 'Accept: application/json' \
--url 'https://api.ticketevolution.com/v9/orders/{order_id}/items/{item_id}/add_etickets'
-d '{"files":["<base64-encoded file>","<another base64-encoded file>"]}'Once you have added all of the files, simple let us know that you have completed it by POSTing to the Items / Finalize Etickets endpoint.
curl -H 'X-Token: FsxRk6qxJgVn6qzsgPQznyvVNykPwd22' \
-H 'X-Signature: nMNnzD2zauXFNgNoDwWBKwUg2TbJKZKLEwRcsmigdjkA' \
-H 'Accept: application/json' \
-url 'https://api.ticketevolution.com/v9/orders/{order_id}/items/{item_id}/finalize_etickets' \
-d '{"keep_pages":[1,2,3,4]}'If you need to, you can “reset” and wipe out all uploaded files using Items / Remove Etickets any time before you Finalize.
Delivering All Tickets in a Single File
Use the Orders / Deliver Etickets endpoint to upload a single base64 encoded PDF file that has all of the tickets.
In the example below the item_id value comes from the property named order_item_id from the item within the order, not the id.
Physical Tickets
FedEx
If the shipment type for an order is FedEx there is a two step process to getting the airbill.
Local Pickup
For orders where the shipment type is LocalPickup both the buyer and seller need to provide they information so that they can arrange to meet for the local pickup.