Connect your system to the promoter's CRM
Promoters with their stack already connected to Nevent
If your system produces event data, this is your landing point
Four typical integrator profiles and the data they send. Once connected, you become available to any promoter using Nevent.
Ticketing platforms
You send events (the ones the promoter publishes on your platform) and purchases (every sale with its buyer, prices, fees and issued tickets). The promoter sees in their CRM the same operation they see in your panel, unified with their campaigns and attribution. One integration opens the door to every promoter using Nevent.
Cashless systems
You send in-event consumption data per user: top-ups, which bars or stands they consumed at, refunds. This turns your transactional data into actionable behavior info: the promoter knows who consumes what and can segment campaigns based on those habits.
Ecommerce and merchandising
You send products, abandoned carts, online merch purchases and deliveries. The promoter can unify who bought a ticket with who bought a t-shirt and build cross-segments that previously lived in two separate platforms.
Custom systems and other providers
Custom apps from the promoter, access control systems, loyalty platforms, internal tools. Any system generating event data can send it to Nevent through the Connect API so it stops living isolated in silos.
A data model designed for live entertainment
The Connect API has specific endpoint groups for the data the sector produces. You don't have to adapt your model, it already covers the typical cases.
One integration, every promoter
For a technical provider, integrating promoter by promoter is a never-ending problem: each one with their data model, their authentication, their way of doing things. The Connect API solves the CRM side: a single integration with Nevent makes you available to any promoter using the platform. Your dev team does it once and it's done.
Frequently asked questions
Who should use the Connect API?
Technical providers that generate data from the promoter's events: ticketing platforms, cashless systems, merch ecommerce, access control, custom apps, or any tool producing purchase, attendance or in-event consumption data. The API is ingestion-only: your system sends data to Nevent, it doesn't consume Nevent data.
I'm a ticketing platform and I want to integrate with Nevent. What do I need to do?
Typically you send two types of data: events (the events the promoter publishes on your platform) and purchases (every ticket transaction with its buyer, prices, fees and issued tickets). With that, the promoter sees in their Nevent CRM the same operation they see in your panel, but unified with their campaigns, attribution and the rest of their audience. You integrate once and become available to every promoter using Nevent.
What if I'm a cashless or merch ecommerce solution?
Same concept: you send the relevant data from your vertical. Cashless sends consumption per user and per event. Merch ecommerce sends products, carts, purchases and deliveries. The Connect API has specific endpoint groups for cart, purchase, merch, zone and wallet, so the data model covers the typical verticals of live entertainment without you having to adapt your system.
What authentication does the API use?
Bearer token (JWT) in the Authorization header, with tokens issued at the provider level. Each token is tied to a provider (not to an individual promoter): you as a ticketing platform have your credentials, and from them you send data for the promoters you have connected with Nevent. Role-based permissions and token rotation are documented in the technical portal.
Does it have webhooks or is it just synchronous calls?
The Connect API receives data from your system via standard POST. You can send events one by one in real time (when the sale happens) or in batches if your system processes by batch. For the reverse flow (when Nevent needs to notify you of something, like a communication opt-out that affects your system), there's an outbound webhook mechanism your integration can consume.
Is there a validation or partnership process?
Yes. Before going to production, we validate the data model you'll send, run sandbox tests with real data and certify the integration. Once certified, we include you in the [Nevent integrations directory](/en/integrations/) and any promoter can connect your system in a couple of clicks. The interest is mutual: you reach more promoters and our clients have more options.
Connect your system with Nevent
Access the technical documentation or talk to our partnerships team to start the integration process.
View documentation