1. RunSignup
  2. API
  3. Methods
  4. Add Tickets

Add Tickets

Allows you to add tickets to a specific ticket event. This endpoint creates new tickets with the specified information for the purchaser and ticket holders.

Required columns:

  • contact_first_name - First name of the ticket purchaser
  • contact_last_name - Last name of the ticket purchaser
  • contact_email - Email address of the ticket purchaser
  • ticket_level_id - Ticketable level ID
  • ticket_quantity - Number of tickets to create
  • ticket_pricing - Price of the ticket in dollars (0 for free tickets)

Optional columns:

  • contact_dob
  • contact_age
  • contact_gender
  • contact_phone
  • contact_address1
  • contact_city
  • contact_state
  • contact_countrycode
  • contact_zipcode
  • ticket_first_name
  • ticket_last_name
  • ticket_email
  • ticket_dob
  • ticket_age
  • ticket_gender
  • ticket_phone
  • ticket_address1
  • ticket_city
  • ticket_state
  • ticket_countrycode
  • ticket_zipcode
  • ticket_purchase_date

Important: This API does not support timed entry events. If you need to import tickets for timed entry events, please use the manual entry feature available on the ticket dashboard.

Notes: The maximum number of ticket purchases in the tickets array per request must be fewer than 50. The order of values in each ticket array must match the order of columns defined in the "columns" array. Each value corresponds to the column at the same position. If you set the auto_check_in parameter to true, all imported tickets will be automatically checked in upon creation.

Request Format

{
	"columns": [
		"contact_first_name",
		"contact_last_name",
		"contact_email",
		"contact_phone",
		"contact_address1",
		"contact_city",
		"contact_state",
		"contact_countrycode",
		"contact_zipcode",
		"ticket_first_name",
		"ticket_last_name",
		"ticket_email",
		"ticket_level_id",
		"ticket_quantity",
		"ticket_pricing"
	],
	"tickets": [
		["John", "Smith", "john.smith@example.com", "555-123-4567", "123 Main St", "Philadelphia", "PA", "US", "19001", "John", "Smith", "john.smith@example.com", 7, 1, 0],
		["Jane", "Doe", "jane.doe@example.com", "555-234-5678", "456 Oak St", "Beverly Hills", "CA", "US", "90210", "Jane", "Doe", "jane.doe@example.com", 7, 1, 0],
		["Bob",  "Lee", "bob.lee@example.com",  "555-345-6789", "789 Pine St", "Houston",  "TX", "US", "77001", "Bob",  "Lee", "bob.lee@example.com", 7, 2, 0]
	]
}

Response Format

The ticket_ids array contains one entry for each ticket actually created. Since each row in your tickets array can specify a ticket_quantity greater than 1, you may get more IDs here than you have rows above. In the example below, three rows (quantities 1, 1, and 2) produce four ticket IDs.

{
	"ticket_ids": [2388, 2389, 2390, 2391],
	"num_tickets_added": 4
}

URL

https://www.trisignup.com/rest/v2/tickets/add-tickets.json

HTTP Method

POST

Parameters

Parameter HTTP Method Default Description Datatype
ticket_event_id
Required
GET ID of ticket event. uint
rsu_api_key GET API key. string
X-RSU-API-SECRET HTTP Header API secret. string
auto_check_in GET F Automatically check in the newly created tickets? bool
request POST Request in proper format. string

If you continue to use this site, you consent to use all cookies. We use cookies to offer you a better browsing experience. Read how we use cookies and how you can control them by visiting our Privacy Policy.

If you continue to use this site, you consent to use all cookies.