API & integrations

Event management software integrations.Connect your CRM, IT stack and AI assistants.

AirLST integrations connect your guest list with the rest of your company: contacts in from Salesforce or HubSpot, RSVPs and attendance back out, registrations from your own website, data for BI and finance. And through MCP, AI assistants talk directly to your event data.

Discuss your setup Integration Services

SalesforceConnectorContacts → guests · status ←
HubSpotConnectorContacts → guests · status ←
Your websiteREST APIRegistration → guests

Guest listBrand Summit 2026Live

1,240Guests
860RSVPs
6Connections

10:14 AMSalesforce 12 contacts updated
10:12 AMMCP registration form created
10:11 AMREST POST /guests · Laura Hayes

AI assistantMCPBuilds pages · user's rights
Your systemsREST APIRead guests and status
BI / financeExportAttendance, revenue · daily

CRM stays in chargeContacts come from Salesforce or HubSpot, event data goes back.

REST APICreate and update guests, read status: from any system that speaks HTTP.

MCPAI assistants build in Airstage, within the rights of the signed-in user.

Trusted by leading event teams and enterprises

Event data belongs in your systems. Not in a spreadsheet export.

01Contacts in

From your CRM, campaign or website straight into the guest list, with no Excel file in between.

02Results out

RSVP, attendance, no-shows and revenue back to the contact, your BI tool and finance.

03Standard connectors

Salesforce and HubSpot ready to go; SAP, Dynamics and marketing automation as a project.

04AI in the conversation

MCP: your assistant works in AirLST, within your rights, with your data hosted in Germany.

01CRM

Salesforce and HubSpot integration: contact in, result back.

Your CRM stays the system of record for contacts, AirLST for the event. The connector creates contacts, lists or campaign members as guests; invitation, RSVP, attendance and no-show go back to the contact as a status or activity. Sales and marketing keep working where they already are.

SalesforceContacts and campaign members as guests; event status on the contact; connector available. Salesforce event management
HubSpotContacts and lists as guests; RSVP and attendance as properties for workflows and sequences; trade show leads from lead retrieval (Exhibitor Edition) go to HubSpot as well. HubSpot event management
SAP, Microsoft Dynamics, marketing automationConnected through the REST API, delivered as an integration project: SAP integration, Dynamics 365 integration.
Fields and rulesWhich objects, which fields, which direction: defined with our Integration Services.

Connector · SalesforceBrand Summit 2026Field mappingSync

AirLST

Salesforce

First name

Contact.FirstName

Last name

Contact.LastName

Company

Account.Name

Guest group

CampaignMember.Status → VIP, Partner

Guest status

CampaignMember.Status ← Confirmed, Checked in

Campaign Summit 2026: 214 members created as guests, 12 updated, 0 conflicts.

Direction per field: the contact comes from the CRM, the status goes back

02REST API

The event management API: create guests, read status, from any system.

The REST API is the way in for everything that has no ready-made connector: registration on your own website, the intranet, the ticketing system, the BI tool. Create and update guests, read status and attendance, pull reporting data; all on the same record your team sees in the back office.

APIBrand Summit 2026 · key “Website”GuestsStatusReporting

// Registration from your own website
POST /events/{event}/guests
{
"first_name": "Laura",
"last_name": "Hayes",
"email": "laura.hayes@belventi.example",
"company": "Belventi Group",
"group": "Workshop A",
"status": "requested"
}
// Attendance after the event
GET /events/{event}/guests?status=checked_in

Response

201 Created · guest VLWR0O47 created, confirmation sent

code	VLWR0O47
status	Requested
group	Workshop A
registration_url	https://…/r/VLWR0O47

Field names and endpoints are illustrative; the documentation is binding:

One key per system with its own rights, like a user

The same guest record your team, the check-in app and reporting see

Three directions

Contacts in, registrations in, results out: RSVP, attendance, no-shows, revenue.

From Professional

API Access (REST) is included in the Suite and the event app from the Professional plan.

Developer details

SDKs, webhooks, OAuth scopes and documentation:

03MCP

Connect AI assistants: the AirLST MCP server.

Next to the REST API for systems, AirLST has an MCP server for AI assistants such as Claude, ChatGPT or Copilot. The assistant uses it to work in AirLST in the conversation, today in Airstage for landing pages and registration forms, with the signed-in user’s permissions and fully logged. Connection, tools and security are on the AirLST MCP server page.

API keysBrand Summit 2026New key

Key	Rights	Last call	Status
Website · registration	Create guests	30 s ago	Active
Intranet · employee events	Read guests Status	yesterday	Active
BI · finance	Reporting	6:00 AM	Active
Agency · test	Read guests	–	Inactive

Keys have rights like users: a key that only creates guests can’t read reporting data.

One key per system, revocable at any time

04Your own application

Build your own application on top of the API.

Building an employee portal, a dealer cockpit or an internal agent? The REST API delivers guests, status, attendance and reporting data; your application brings the interface. Rights per key, a log entry per call, data hosted in Germany.

REST APICreate and update guests, read status and attendance, pull reporting data; confirmed and in production use.
Keys with rightsOne key per system with the roles of the guest list; revocable and logged.
SDK, webhooks, OAuth
With supportDesign, field mapping, testing and go-live with our Integration Services.

An integration is a user. It has rights, and it has a log.

Whether it’s a connector, an API key or an MCP connection, every access runs through the roles and rights of the guest list and is recorded in the change log. The data stays with AirLST in Germany; what a connected system or a language model processes on its own side is governed by your contract with that provider.

Hosted in GermanyGuest and event data on servers in Germany, including when it’s exchanged through integrations.
GDPR compliantData processing terms and the deletion policy are in the Trust Center; technical details on API security:
TISAX assessedAirLST is assessed under TISAX, the information security assessment standard of the automotive industry.

PermissionSalesforceWebsiteAI assistant

Create guests–

Read and filter guests–

Write status back––

Draft email––

Export–––

Example. You assign rights per connection; the AI assistant inherits the role of the user who connected it.

Part of AirLST

The integration is the guest record, seen from the outside.

Your CRM, website, BI tool and AI assistant read and write the same guest as your team, the check-in app and reporting. That’s why there’s no export going stale and no import creating duplicates.

Hosting, encryption and data processing are described in the Trust Center; our Integration Services handle the design and implementation of integrations. How many events run on one standard, connected to your IT, is covered on the event management software page.

What is an event API?

An event API is an interface that lets other systems read and write event data: create CRM contacts as guests, hand over registrations from your own website, and push RSVPs, attendance and no-shows back to your CRM, marketing automation or BI tool. In AirLST that is a REST API, complemented by ready-made connectors for Salesforce and HubSpot; integrations with SAP, Microsoft Dynamics and marketing automation platforms are delivered as a project.

The point of event management software integrations isn’t moving data around; it’s ending the export. As long as guest lists travel as Excel files between CRM, agency and the front door, there are several versions, duplicate contacts and results that never make it back to the CRM. With the API, your CRM stays in charge of contacts, AirLST stays in charge of the event, and both know the same guest. On top of that comes MCP: through the Model Context Protocol, AI assistants talk to AirLST, for questions and prepared actions within the user’s rights.

The integration isn’t a data export. It’s the guest record, seen from the outside.

RESTAPI for guests, status, attendance, reporting; from Professional

2Ready-made connectors: Salesforce, HubSpot; SAP and Dynamics as a project

MCPModel Context Protocol for Claude, ChatGPT, Copilot and your own agents

How does an integration with AirLST work?

Define the goal. Which direction, which data, which system of record: contacts in, registrations in, results out.
Choose the route. A connector for Salesforce or HubSpot; the REST API for your website, intranet, BI, SAP, Dynamics and marketing automation; MCP for AI assistants.
Create a key. One key per system with the roles of the guest list; only the rights the purpose needs.
Map the fields. Which field goes where, which group gets which status; handle conflicts and duplicates, with our Integration Services.
Test and go live. Test event, check the sync, read the log, then production; every change stays traceable.
Run it. Connectors run automatically; API calls and MCP access are logged; keys can be revoked at any time.

How is MCP different from the API?

The REST API connects AirLST with other systems and is programmed by developers: one call, one response, one defined field. MCP connects AirLST with AI assistants and is used by people in conversation: the AirLST MCP server describes tools such as “add a page” or “build the form from the guest fields”, and the assistant picks them based on the request. Both access the same data, with the same rights.

The API is for systems, MCP is for conversations. Both see the same guest, and both can only do what the user can.

For an event team, that means a landing page with a registration form takes shape in a conversation, while you watch live and approve. Airstage is connected today, other modules follow; the tools and the OAuth sign-in are described on the AirLST MCP server page.

What does the integration work with?

With the event CRM as the contact base across events, the guest list as the record behind every endpoint, event registration for sign-ups from outside, event reporting for BI, workflow automation for if-then rules, and special configurations with integrations.

Integration Services: design, field mapping, testing, go-live
Trust Center: hosting, encryption, data processing
Event management software: many events, one standard, connected to your IT
Automotive events: TISAX-assessed data handling for integrations in the automotive industry

FAQ

Integrations, API and MCP: frequently asked questions

Does AirLST have an event management API?

Yes. AirLST offers a REST API that exchanges event data with your other systems: contacts from your CRM go into the guest list, registrations from your own website go into AirLST, and RSVPs, attendance and reporting data flow back to your CRM or BI tool. API Access is included from the Professional plan; connectors and integration projects are offered as Integration Services. See pricing.

How does the Salesforce event integration work?

Through the Salesforce connector: contacts or campaign members are created as guests in AirLST, and invitation, RSVP and attendance go back to the contact as a status. Which objects and fields are synced is defined together with our Integration Services. Salesforce stays the system of record for contacts, AirLST for the event.

Can HubSpot be used for event management?

Yes, together with AirLST. The AirLST HubSpot connector takes contacts and lists from HubSpot as guests, and event data such as RSVP, attendance and no-show lands on the HubSpot contact as properties or activities, ready for workflows and sequences.

Can AirLST connect to SAP, Microsoft Dynamics or marketing automation?

Yes, through the REST API. Integrations with SAP, Microsoft Dynamics and marketing automation platforms are possible and are delivered as an integration project. Our Integration Services team supports you from interface design to go-live.

Is there API documentation, an SDK or webhooks?

The REST API is confirmed and in production use. We describe documentation, SDKs and webhooks here only once they are confirmed: . MCP access terms: . Until then, request access and we will get back to you with the details.