Order Notifications (Webhooks)
Description | Notifications System can be used to update you about new orders as well as changes to an order. |
---|
Webhooks are sent as an application/x-www-form-urlencoded
POST to a URL which you provide to TEvo. All webhooks will include an order_group_id
, recipient
, event_type
, and body
.
We have notifications that apply to both Sellers and Buyers and the recipient
parameter indicates whether you are the buyer or the seller for the given order.
If you wish to use webhooks in Sandbox or Production contact our support team to provide us the URL.
You will only receive Buyer Notifications if you are creating Buy Orders, which most groups should not be doing.
Seller Notifications
New Order/Fraud Response Received
As soon as a new order for your tickets is received we will send these notifications. This should reduce your reliance on checking Orders / Index for new orders, and once you have confirmed this notification is working for you we suggest that only check Orders / Index every 5 minutes or so as a fallback.
recipient | event_type | body |
---|---|---|
|
|
|
Airbill Uploaded
When a buyer has purchased Physical tickets to be shipped and used the delivery type ProvidedAirbill
to indicate they would upload an airbill we will send this notification when the airbill is uploaded and is ready for you to retrieve using Shipments / Get Airbill or manually via Core.
recipient | event_type | body |
---|---|---|
|
|
|
Delivery Updated
When the delivery has detail or attribute changes post-order (email address, name, etc…), we will send this notification.
recipient | event_types | body |
---|---|---|
|
|
|
Order Accepted
When you have Accepted an order we will send this notification.
recipient | event_type | body |
---|---|---|
|
|
|
Etickets Finalized
When you have uploaded and finalized Etickets for an order item we will send this notification.
recipient | event_type | body |
---|---|---|
|
|
|
In-Hand Updated
When the in hand
or in hand on
changes on an order, we will send this notification.
recipient | event_type | body |
---|---|---|
|
|
Order Rejected
When you have Rejected an order we will send this notification.
recipient | event_type | body |
---|---|---|
|
|
Buyer Notifications
Order Accepted
When a Seller accepts a Purchase Order you have sent you will receive this notification.
recipient | event_type | body |
---|---|---|
|
|
Order Rejected
When a Seller has Rejected a Purchase Order you have sent you will receive this notification.
recipient | event_type | body |
---|---|---|
|
|
ETicket Finalized
Once the Seller has uploaded the Etickets for an item within your Purchase Order you will receive this notification.
recipient | event_type | body |
---|---|---|
|
|
In-Hand Updated
When the in hand
or in hand on
changes on an order, we will send this notification.
recipient | event_type | body |
---|---|---|
|
|
Airbill Requested
When a Seller has requested an airbill because they are ready to ship Physical tickets we will send this notification. See below for notification example.
Airbill Generated
When a Seller has generated an airbill because they are ready to ship Physical tickets we will send this notification. See below for notification example.
Delivery Reclassified
When the delivery method has changed post-order (ex: from Fedex to Local Pickup, etc…), we will send this notification. See below for notification example.
Delivery Updated
When the delivery has detail or attribute changes post-order (email address, name, etc…), we will send this notification. See below for notification example.
Delivery Shipped
When FedEx shows that they have taken possession of a package we will send this notification. See below for notification example.
Delivery Complete
This notification is sent when:
Physical tickets are shown as delivered via FedEx
Etickets are uploaded into the system
Transferrable tickets (Flash and TM Mobile) have been transferred
When the information for Local Pickup, Will Call, or Guest List has been exchanged
recipient | event_types | body |
---|---|---|
|
|