This API can be used to fetch all the tickets that belong to an organizer or an event, along with useful data for each ticket.
It can also be used repeatedly with a parameter to only fetch the new & updated tickets after a given date & time.
GET https://api.shotgun.live/tickets
If you are a partner, add your key in the URL query string
If you are an organizer, add your token either as a header (Authorization: Bearer [token]) or in the query string as token
| key | required | description |
|---|---|---|
organizer_id |
yes | • if you are a partner, this organizer must have granted you access |
| • if you are the organizer, it must match your token’s payload | ||
event_id |
no | if you only want the tickets for a given event |
include_cohosted_events |
no | set to 1 or true to include events of which you are a cohost |
after |
no | ISO date to only return tickets updated after it |
(can also be a tuple of [date]_[ticket id] to specify from which ticket to start when multiple tickets have the exact same update date) |
Tickets are ordered by update date/time ascending, then ID ascending, which means you get the oldest ones first, and the newest ones in the last page.
Pages contain at most 100 tickets, and if the page is full, the result contains a link to the next page for your convenience (in pagination.next).
You don’t get the total count in the response, because by the time you reach the last page, it can evolve.
https://api.shotgun.live/tickets?**token**=xxx.xxx.xxx&**organizer_id**=173027&**event_id**=410006&**include_cohosted_events**=1
The response uses JSON and is an object containing your params, the pagination infos, and a list of tickets in data, so it looks like this:
Each ticket object has these fields: