# Airlst

> Airlst is an all-in-one event management software for professional guest management (SaaS), RSVP workflows, on-site check-in, ticketing and seating — built for event agencies and corporate event teams.

> Airlst solves the operational complexity of managing event attendees at scale: it replaces fragmented spreadsheets, manual invitation tracking, and ad-hoc check-in lists with a single, GDPR-compliant platform that increases efficiency, raises the professional standard of guest communication, and ensures data security throughout the entire event lifecycle.

## Core Features

- **RSVP Management**: Customizable invitation pages, multi-step registration forms, plus-one and session-level RSVPs, automated reminders, and real-time response tracking.
- **Guest Management**: Centralized guest database, segmentation, custom fields, bulk import/export, status tracking, and approval workflows.
- **Check-in App**: Native mobile check-in app for on-site entry control with QR-code scanning, offline mode, multi-device sync, and live attendance dashboards.
- **Seating Planner**: Visual drag-and-drop seating tool with table assignments, group/VIP logic, capacity rules, and printable place cards.
- **Email Automation**: Triggered transactional emails (invitation, confirmation, reminder, thank-you), branded templates, custom domains, and personalized merge fields.
- **Event Workflows**: Multi-event management, role-based team access, agenda/session handling, and automated lifecycle triggers.
- **Reporting & Analytics**: Live event KPIs, response rates, check-in statistics, and exportable attendee reports.

## For Developers / Integration

Airlst provides a REST API for programmatic access to events, guest lists, RSVP data, and check-in status. Outbound webhooks deliver real-time notifications for guest registrations, status changes, and check-ins. No-code integrations are available via Zapier and Make (Integromat) for connecting Airlst to CRM systems (HubSpot, Salesforce, Pipedrive), marketing tools, and Google Sheets. Single Sign-On (SSO) is supported for enterprise deployments.

## Key Resources

- [Homepage](https://www.airlst.com)
- [Features](https://www.airlst.com/features)
- [Preise](https://www.airlst.com/pricing)
- [Help Center](https://help.airlst.com)
- [Login](https://app.airlst.com)

## llms-full

### Guest List Architecture
Guest lists in Airlst are structured as event-scoped collections of guest records. Each record supports core identity fields (salutation, first/last name, email, phone), arbitrary custom fields per event, status flags (invited, confirmed, declined, checked-in, no-show), plus-one relations, group/company affiliation, and per-session participation. Guest records carry an immutable invitation token used for secure, password-less access to personalized RSVP pages and digital tickets/QR codes.

### Check-in & On-Site Operations
Check-in runs through a dedicated mobile app (iOS/Android) with QR-code scanning. The system supports offline-first operation — scans queue locally and sync when connectivity returns. Multiple devices can scan the same event simultaneously with conflict resolution and live cross-device state. Manual check-in, search-by-name fallback, and accreditation badge printing are supported.

### Security & Compliance
Airlst is built and operated under GDPR (EU 2016/679) requirements. Data is hosted in EU data centers (Germany). Standard security measures include encryption in transit (TLS 1.2+), encryption at rest, role-based access control, audit logging, and data processing agreements (DPA / AVV) for B2B customers. The platform supports configurable retention policies and guest-data deletion workflows to meet right-to-erasure obligations.

### Certifications & Standards
Airlst aligns its information security practices with industry standards relevant to enterprise and automotive event clients. For up-to-date certification details (including any TISAX or SOC-equivalent statuses), refer to the official trust/security documentation on airlst.com or request the current compliance package via sales.

### API & Webhook Surface
The REST API exposes events, guests, RSVPs, sessions, and check-in actions. Authentication is via API tokens scoped to an organization. Webhooks fire on guest creation, RSVP status change, check-in, and email-event delivery. Rate limits and pagination follow standard REST conventions. SDK/code examples and full endpoint references are available via the official Airlst documentation.

### Technical Reference for Integrators

**Checkout API.** Airlst publishes a dedicated Checkout API used by event landing pages to drive the ticket and add-on purchase flow. It covers order creation, billing-address updates, ticket and add-on selection per guest, companion guest management, ticket-guest self-registration, promo codes, and retrieval of the payment redirect URL. The Checkout API is documented with an OpenAPI 3.0 specification, which is the source of truth for request and response shapes. The machine-readable spec is published at https://airlst.app/openapi.yml.

**Landing-page API.** A separate API powers the public event websites built with the Airlst website editor: form submissions, guest lookup via invitation token, and dynamic content rendering for personalized landing pages.

**Authentication.** Public guest-facing APIs are scoped to a specific order or guest via the order ID and the guest's invitation code, so guests can act only within the booking they were invited to. Programmatic and partner integrations authenticate using API tokens scoped to an organization.

**Conventions.** All APIs are JSON over HTTPS. Responses follow a `{ "data": ... }` envelope, primary identifiers are UUIDs, and per-route rate limits protect sensitive actions (e.g. promo-code redemption). Validation errors return HTTP 422 with a structured `{ message, errors }` body.

**Domain model worth knowing for API consumers.**

- An *event* belongs to a tenant organization and owns its own guest list, landing page, and checkout configuration.
- A *booking* is a group of one or more guests invited or registered together. Each guest carries an immutable invitation code that acts as a password-less identifier in URLs and APIs.
- A booking may have one or more *orders*. Each order line item is a reservation pointing to either a ticket product or an add-on product (workshops, accommodation, transport, etc.). Products are organized into product categories such as tickets, hotel, or workshop.
- *Custom fields* can be defined per event and attached to events, bookings, or guests. Their values are returned in API payloads under a custom-fields map keyed by field slug.

**Webhooks & workflows.** Outbound webhooks are configured per event through the workflow module: triggers fire on guest status changes, registrations, check-ins, and payment events, and can dispatch HTTP requests or transactional emails. Webhook payloads follow the same JSON resource shape as the API.

### Target Audience
Event agencies, corporate communications and marketing teams, automotive and luxury-brand event operations, conference organizers, and internal event managers handling recurring high-stakes guest experiences.