Skip to content
Customer Portals Sign in
Submit a Ticket
  • There are no suggestions because the search field is empty.

How to Set Up Dexibit/Ticketure Data Feed

Looking to add Ticketure data into your Dexibit reporting suite. This article outlines the steps needed to define Ticketure automated tasks for this service.

Before you get started

Information and requirements relevant to completing this setup.

Skill Level Required Advanced
Ticketure Support Required A Ticketure team member is needed to configure the Automated tasks
Additional Requirements Dexibit will provide a security key and venue information.
 

Ticketure Webhook Definitions

The Dexibit feed requires 2 webhooks/automated tasks to be configured within Ticketure: `ticket_audit` and `session_changed`. The session_changed will send over the event times/details, whereas ticket_audit will send over all details of purchases/redemptions/etc.

Ticket Audit

ticket audit details

  1. Task - Required - Select `Webhook` as the Task
  2. Webhook Type - Required - Select `Ticket Audit 2` as the Webhook Type
  3. Display Name - Optional - Enter a Display Name for the Webhook - ex: Dexibit - Ticket Audit
  4. Sellers - Optional - Limit the events sent to Dexibit to selected seller(s) (default All/Empty)
  5. Audit Actions - Optional - Limit the actions that are sent to Dexibit (default All/Empty)
  6. Event Limits - Optional - Limit the events sent by Event Category or by Event Name (default All/Empty)
  7. Destination URL - Required - URL provided by Dexibit of where information is to be sent (varies by customer)
  8. Batch Size - Required - Select 200
  9. Send Event Data Starting from - typically this is when the customer started selling tickets in Ticketure.
  10. Request Headers - Required - 2 Request headers are provided by Dexibit:
    1. signature: YZzMbzqilYjufFnrQEXsJRtgI66y9ZQb
    2. venue_id:
* HMAC field can be left blank and will populate upon saving.

Session Changed

The session_changed webhook is needed to create a proper schedule of the events within Dexibit. 

  1. Task - Required - Select `Webhook` as the Task
  2. Webhook Type - Required - Select `Session Changed` as the Webhook Type
  3. Display Name - Optional - Enter a Display Name for the Webhook - ex: Dexibit - Session Changed
  4. Destination URL - Required - URL provided by Dexibit of where information is to be sent (varies by customer)
  5. Request Headers - Required - 2 Request headers are provided by Dexibit:
    1. signature: YZzMbzqilYjufFnrQEXsJRtgI66y9ZQb
    2. venue_id:
    * HMAC field can be left blank and will populate upon saving.

Session Changed payloads can not be replayed. To send event configuration to Dexibit, an update will need to be made to the event schedule or capacity in Ticketure