Integrations via API, MCP & Webhooks

Quick Event's public REST API enables event creation via HTTP request:

Endpoint: POST /api/public/create-event
Authentication: None required — the API is openly usable.
Rate limit: 5 demo events per IP address per 24 hours.

You send a description (prompt), optionally including date, location, and language. Quick Event uses AI to generate a complete event page with a landing page, registration form, email templates, and ticket categories. The response contains direct links to the event page and registration form.

Demo events expire after 30 days. With a free account, you can permanently take over the event.

The MCP Server (Model Context Protocol) makes Quick Event available as a tool in AI assistants like Claude Desktop, Cursor, and Claude Code:

Endpoint: https://quick-event.com/api/public/mcp
Transport: Streamable HTTP (JSON-RPC 2.0 over POST)
Protocol version: 2025-11-25
Auth: none

The `create_event` tool accepts the same parameters as the REST API. MCP clients are not auto-discovered from a URL — you add the endpoint to the client's MCP config (e.g. claude_desktop_config.json), and the tool becomes available in every new conversation.

Yes — via a custom GPT with an Action backed by our OpenAPI 3.1 specification:

• OpenAPI: https://quick-event.com/.well-known/openapi.yaml

In the ChatGPT GPT Builder, create a new GPT and add the OpenAPI URL under "Actions". Authentication is set to "None". The custom GPT can then create events via prompt and distribute the generated links to users. Note: the legacy ChatGPT Plugins platform was deprecated by OpenAI in 2024 — only Custom GPTs / Actions are supported today.

Webhooks are available today as the CRM connection:

• Every registration, every later change and every check-in scan is posted as signed JSON (HMAC-SHA256)
• HTTPS-only, delivered at least once
• Per destination you choose which records it receives: participants, bookings, check-ins

The connection is one-way — data leaves Quick Event, nothing can be written in. Point it at your CRM directly or at an automation layer such as n8n, Make or Zapier. Details are on the CRM integration page.

No. The public API does not require authentication. Anyone can create an event via a POST request.

The only limitation is the rate limit: a maximum of 5 demo events per IP address within 24 hours. Created events expire after 30 days unless they are made permanent by registering a free account.

All connections are via HTTPS with TLS 1.3.

Quick Event uses the following services in the background:

• SendGrid: Email delivery with custom domain support (DKIM, SPF)
• Stripe: Payment processing for paid tickets and subscriptions
• Pexels: Free stock photos available directly in the page builder
• Hetzner: Hosting, database, and file storage in German data centres

These services are fully integrated — you don’t need to create your own accounts to use Quick Event.

Quick Event does not offer a widget or iframe for creating events on your website. (Embedding the guest registration is different, and that is supported.) The cleanest approach is to call the public REST API (POST /api/public/create-event) from your own backend and redirect users to the generated event URL. No authentication is needed, and the API returns a direct link to the event page and registration form within seconds.

A full read API for events, attendees, and bookings is on the Quick Event roadmap. Until it ships, you can export participant data manually from the studio. Webhooks are available today as the CRM connection: every registration, change and check-in scan is pushed as signed JSON to a URL of your choice, so automatic CRM sync works without polling.

The upcoming read API will provide programmatic access to events, attendees, and booking records. Authenticated mutations such as cancelling a booking or editing attendee data are planned alongside it. Exact endpoint structure, authentication method, and data formats will be published with the release.

Payouts go directly to your bank account via Stripe Connect. Quick Event never holds funds: the studio walks you through Stripe Connect onboarding when you create your first paid event, and each payment is routed straight to your account. Quick Event’s payment fee for paid tickets — 3.25 % + €0.25 per booking (plus VAT on the fee), card processing included — is netted from each payout, and you receive an invoice for it with VAT for your accounting. The modules themselves are bought once per event and are not affected by how much you sell.

Yes. The Quick Event page builder integrates the Pexels API, giving you access to millions of royalty-free photos directly inside the editor. You do not need a Pexels account or a separate licence — the integration is fully embedded in the platform.

All transactional emails are sent via SendGrid. When you use a custom sender domain, Quick Event automatically configures DKIM and SPF records for that domain, which are the main technical factors that determine deliverability. You do not need a SendGrid account — the integration runs entirely within Quick Event.

Yes. Under Registration › Settings, copy the embed code and paste it where the registration should appear on your website. It works on any domain and resizes itself. The form, checkout and confirmation run inside the frame; guests pay by card, Apple Pay, Google Pay or Link, and a link opens the full checkout for other payment methods. If Google Tag Manager or Matomo is installed on that page, registration steps and purchases are passed on to it, without personal data. Only the registration can be embedded, not the event page, and a password-protected event cannot be embedded.