Tixstock Sandbox API

Number of APIs: 16

TixStock will implement a local Event's database which will be frequently synced to StubHubs Event Listing. As part of the Event mapping there will additional logic in place which groups commonly used naming convention for Events. i.e. a market place could refer to Manchester United Football club in multiple ways "Manchester United, Man Utd, Man U, MUCFC" etc.

Event categorisation will also be handled by TixStock. By default it is expected the reseller will be using StubHub as their default event data. If this is not the case, the reseller will be required to provide their event information in advance so the necessary rule sets can be implemented.

Event mapping is performed for each ticket related Endpoint. By doing so, this will associate the Reseller Event to an Event on TixStock. When an reseller event cannot be matched the Event in question will still appear on TixStock. However the Event will be restricted to that Resellers website. As a result a Broker cannot cross sell the ticket(s) on other Market Places.

API Endpoints:

Webhooks:

Resellers:

Ticket Resellers will upload their event listings via the TixStock Add Tickets API endpoint. Event mapping will be performed to match the Event in accordance to the above.

Brokers:

Brokers are teams and individuals, whom use TixStock directly to manage their inventory.

System Flow Questions and Answers:

Q) How do we populate our event's on TixStock?

A) This depends on how you are categorising your events. If you are following StubHub data mapping you can upload each event using the Add Ticket(s) endpoint. If this is not the case, you will need to provide your event data upfront. This will allow TixStock to update their Event Mapping rules based upon your systems naming convention and identifiers.

Q) What happens when a Broker uploads a ticket to a reseller from TixStock

A) When a broker pushed their inventory to selected Market Places (resellers) the Add Listing Webhook event is executed containing a payload of Event identifier, seat information and Broker identifier. This will allow the reseller to update the event listings and broker inventory on their site.

Q) What measures are taken to reduce the risk of double selling a ticket.

A) The TixStock API has an on Hold Ticket endpoint which the reseller should send a request at the point the customer adds the ticket to their basket. The request should include the event, ticket and broker identifier information to mark the ticket as "On Hold". Once the request has been verified a On Hold Webhook event will be sent to the other reseller informing them the ticket is currently being purchased.

If a customer removes the ticket from their basket the reseller website should send a request to Release Ticket endpoint. This will allow TixStock to immediately send out a Webhook event informing the other reseller the ticket in question can be purchased again.

When a ticket is purchased on a reseller website, the website must instantly send an API request to the Sold endpoint. This will allow Brokers Sales information to be update within TixStock, and more importantly send out a Sold Ticket Webhook event to the other resellers allowing the reseller to update their inventory accordingly. If the tickets are being listed on StubHub, TixStock will send out an API request to update/remove the listing.

Q) How does TixStock authenticate my customer login details?

A) The customer will be required to enter their credentials on TixStock for each Market Place. A Webhook event will be sent to reseller endpoint continuing either a hash/encrypted password (based upon a pre-agreed format ). The response from the reseller should contain the status of the authentication, coupled with the customers identifier. This will allow TixStock to associate the user on both systems.

Q) What happenes if my customer changes their password?

A) To ensure the customer is always authenticated TixStock allows a reseller to update their customer credentials. The reseller should execute TixStock's Broker Account Details Changed endpoint, at the point the customer updates their details.

Q) What happens if my customer closed their account?

A) Under such circumstances the Reseller should notify TixStock by sending a request to the Close Account endpoint. This will allow TixStock to unlink the customer to your market place within TixStock.

If a TixStock broker has their account closed TixStock will send out Account Closed Webhook event containing the Broker identifier.

1. Broker - Close Broker POST {{API_URL}}/{{API_VERSION}}/broker/close/{{BROKER_ID}}

2. Venues - Get Venues GET {{API_URL}}/{{API_VERSION}}/venues/get?id=&name=&address_line_one&city&country_code&postcode&mapped=&start_date=&end_date=&order_by=&sort_order=&per_page=&page=

3. Orders - Get Orders GET {{API_URL}}/{{API_VERSION}}/order/get?order_id&event_id=&broker_id=&ticket_type=&from=&to=&status&order_by=&sort_order=&per_page=&page=

4. Events - Get Events GET {{API_URL}}/{{API_VERSION}}/events/get?event_id=&event_name&venue_name=&performer_name=&mapped_status=&start_date=&end_date=&order_by=&sort_order=&per_page=&page=

5. Events - Add Event POST {{API_URL}}/{{API_VERSION}}/events/add/{{EVENT_ID}}

6. Events - Bulk Add/Update Events POST {{API_URL}}/{{API_VERSION}}/events/bulk.

7. Performers - Get Performers GET {{API_URL}}/{{API_VERSION}}/performers/get?id=db9188f3-39ec-41b1-b350-d67f7dccdb12&name=Manchester United FC&mapped_status=true&start_date=&end_date=&order_by=&sort_order=&per_page=&page=

8. Tickets - Get Tickets GET {{API_URL}}/{{API_VERSION}}/tickets/get?listing_id=&event_id&broker_id&ticket_type&order_by=&sort_order=&per_page=&page=

9. Tickets - Add Ticket POST {{API_URL}}/{{API_VERSION}}/tickets/add/{{LISTING_ID}}

10. Tickets - Update Ticket POST {{API_URL}}/{{API_VERSION}}/tickets/update/{{LISTING_ID}}