In2event integrates with external ticket providers such as Paylogic and Weeztix to automatically create tickets for accredited guests, crew, and artists. This means you don't have to manually create tickets in your ticket provider — In2Event handles it when someone is approved.
How it works
You connect your ticket provider to your In2Event event via the API settings
You link accreditation items to specific ticket products in your provider
When a person is approved and has an accreditation item assigned, In2Event automatically requests a ticket from the provider
The ticket (usually a PDF) is attached to the person's briefing
What gets synced
Ticket availability — In2Event may sync the available quantity from your ticket provider to the accreditation item limit. This keeps totals aligned but can be surprising if you're not expecting it.
Ticket status — successful or failed ticket creation is logged in the person's logbook
PDF tickets — generated tickets are stored and included in briefings
Important: accreditation item limits
When linked to a ticket provider, the limit on an accreditation item may update automatically based on the available quantity in your provider. If you notice the limit changing on its own, this is the sync at work. To set a custom limit, you may need to adjust availability in your ticket provider first.
Paid guest lists
For paid accreditation items, the flow works slightly differently. When a person is approved, In2Event reserves a ticket with the provider before payment is completed. This ensures the ticket is available when the payment goes through, preventing overselling. The ticket is only fully confirmed after payment is received.
Setting up a new integration
To connect your ticket provider, go to your event settings and look for the API or integration section. You'll need API credentials from your ticket provider. If you need help setting this up, contact In2Event support.
Troubleshooting
If tickets fail to create, check the person's logbook for the error message. Common issues include expired products, reached limits, or connection problems. Read more in our troubleshooting article.
]]>