How does Quick Event's REST API work?

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.

What is the MCP server and how do I use it?

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.

Can I use Quick Event with ChatGPT?

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.

Are webhooks available?

Webhooks are on the roadmap. The planned features are: • Real-time notifications for registrations and cancellations • Signed payloads (HMAC-SHA256) for secure verification • HTTPS-only with retry logic (3× exponential backoff) • Configurable event filters per webhook URL The webhook integration will make it possible to connect Quick Event to any external system — CRM, Slack, your own backends. Submit a feature request on the roadmap page to be notified when it ships.

Do I need an API key or authentication?

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.

Which third-party services does Quick Event use?

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.

Can I embed an event creation form on my own website?

Quick Event does not offer a widget or iframe for embedding. 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.

How can I sync Quick Event registrations with my CRM?

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 — which will push registration and cancellation events to a URL of your choice — are also planned, making automatic CRM sync possible without polling.

What data will the planned read API expose?

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.

How do ticket payouts work — does Quick Event hold my money?

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, so there is no separate invoice. The modules themselves are bought once per event and are not affected by how much you sell.

Are the stock photos from Pexels free to use in my event page?

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.

How does Quick Event ensure my confirmation emails don't land in spam?

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.

Integrations & API – Quick Event

Quick Event connects to external tools and workflows through several interfaces, so your event data doesn't stay locked in one dashboard. A public event-creation endpoint lets you spin up events programmatically. An MCP server exposes Quick Event to AI assistants like Claude Desktop, so you can create and manage events conversationally from your own AI tools. An OpenAPI manifest lets you wire Quick Event into ChatGPT custom GPTs. Webhooks can notify your systems when key things happen — a new registration, a completed payment, a check-in — so you can sync to a CRM, spreadsheet, or automation platform in real time. A full REST API for reading event, attendee, and booking data is planned to round out programmatic access. Behind the scenes, Quick Event also relies on trusted third-party services — Stripe for payments, SendGrid for email delivery, and Hetzner for hosting and file storage in German data centres — each chosen for reliability and GDPR-aligned data handling.

Overview

Currently, two integration layers are available: the MCP Server , which provides Quick Event as a tool in the Model Context Protocol for AI assistants like Claude Desktop, and an OpenAPI specification for integration with ChatGPT and other OpenAPI-compatible platforms. Both interfaces allow users to create a complete event with a landing page , registration form , email templates , and ticket categories using text descriptions.

REST API Partial — read API on roadmap

A public event-creation endpoint is live today at POST /api/public/create-event: send a natural-language description (with optional date, location, and language) and Quick Event generates a full event — landing page, registration form, email templates, ticket categories — using AI. No authentication is required; the rate limit is 5 demo events per IP per 24 hours, and demo events expire after 30 days unless claimed by a free account. The same endpoint backs the MCP server and the ChatGPT integration .

A full read API for programmatic access to events, attendees, and bookings is on the roadmap. It will let you integrate Quick Event with existing CRM systems, marketing tools, or internal workflows without manual data exports. Authenticated mutations (cancel a booking, refund a ticket, edit attendee data) are planned alongside it. Details on endpoints, auth, and data formats will follow with the release.

MCP Server

The MCP (Model Context Protocol) server makes Quick Event available as a tool in AI assistants such as Claude Desktop, Cursor, Claude Code, and any other MCP-compatible client.

The server implements MCP protocol version 2025-11-25 over the Streamable HTTP transport at /api/public/mcp (JSON-RPC 2.0, no authentication, CORS enabled). It supports the methods initialize, tools/list, and tools/call. The only registered tool is create_event and it accepts the same parameters as the REST API.

In practice: you describe an event to your AI assistant, and it calls the MCP tool to create it. The generated links appear inline in the conversation.

Setup in Claude Desktop

MCP clients do not auto-discover servers from a URL — you add the endpoint to the client's config file. In Claude Desktop, edit claude_desktop_config.json (Settings → Developer → Edit config) and add a remote MCP server pointing at https://quick-event.com/api/public/mcp. Restart Claude Desktop and the create_event tool becomes available in new conversations. Cursor, Claude Code, and other clients use a similar config-file pattern. A machine-readable summary of the server (name, endpoint, tool schemas) is also published at /.well-known/mcp.json for documentation and tooling that wants to read it.

ChatGPT Integration

Quick Event publishes an OpenAPI 3.1 specification at /.well-known/openapi.yaml for use as a ChatGPT custom-GPT Action.

In the ChatGPT GPT Builder, create a new GPT, open Configure → Actions, and import the OpenAPI URL. The authentication field stays on "None". The custom GPT can then create events from a prompt and surface the returned links to the user. The OpenAPI spec documents the endpoint in full — request schema, response examples, and error codes.

The legacy ChatGPT Plugins platform (with its ai-plugin.json manifest) was deprecated by OpenAI in 2024 and is no longer supported — Custom GPTs with OpenAPI Actions are the current path.

Webhooks

Webhooks are available today as the CRM connection. Every registration, every later change and every check-in scan is posted as signed JSON to an HTTPS address you choose — your CRM directly, or an automation layer such as n8n, Make or Zapier.

Payloads are signed with HMAC-SHA256 over timestamp and body, delivery is HTTPS-only and at least once, and each destination keeps its own cursor so a broken endpoint never blocks a healthy one. Per destination you choose which record kinds it receives: participants, bookings, check-ins, or any combination.

The connection is one-way: data leaves Quick Event, nothing can be written in from outside. Full details — payload shape, signature verification and delivery guarantees — are on the CRM integration page .

Third-party services

Quick Event uses several specialized services in the background. As a user, you don't need to create a separate account with any of these providers — the integration is fully embedded in the platform.

SendGrid (Email)

All transactional emails—registration confirmations, reminders, campaign emails—are delivered via SendGrid. Quick Event automatically configures DKIM and SPF records for custom domains , ensuring emails are sent from your own sender address and achieve a high deliverability rate .

Stripe (Payments)

Paid tickets are processed via Stripe Connect — funds are routed directly to the organiser's bank account, never held by Quick Event. The studio onboards you to Stripe Connect on first paid event, surfaces chargesEnabled and payoutsEnabled status, and handles refunds and VAT-compliant invoices automatically. Card, Apple Pay, Google Pay, SEPA, and other local payment methods are supported out of the box. Quick Event's payment fee (3.25 % + €0.25 per booking (plus VAT on the fee), card processing included) is netted from each Stripe payout — see Paid tickets for the full flow.

Pexels (stock photos)

The page builder includes an integrated image search via the Pexels API. You can choose from millions of free, royalty-free photos directly when creating an event page and integrate them into your page—without any separate download or upload.

Hetzner (Infrastructure)

The platform runs in German data centres operated by Hetzner Online — application, database, and the object storage that holds your files (logos, PDFs, images). Backups are kept at a second German site. Custom domains automatically receive certificates from Let’s Encrypt as soon as they are verified.

Connect Quick Event to Your Tools & Workflows