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 • Cloudflare: Hosting (Workers), file storage (R2), SSL certificates, custom domains and CDN These services are fully integrated — you don't need to create your own accounts to use Quick Event.

Integrations & API

Quick Event can be integrated into external workflows in several ways — a public event-creation endpoint, an MCP server for AI assistants like Claude Desktop, an OpenAPI manifest for ChatGPT custom GPTs, and a planned full REST API for reading event, attendee, and booking data. This article describes the available interfaces and the third-party services that operate in the background.

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 Planned

Webhooks are on the roadmap. They will make it possible to automatically send HTTP requests to a configurable URL in response to certain events — such as a new registration, a cancellation, or a status change.

The planned architecture features signed payloads (HMAC-SHA256), HTTPS-only delivery, and retry logic with three attempts and exponential backoff. Event filters will allow subscribing to only specific event types per webhook URL.

Once webhooks are available, they will enable workflows such as Slack notifications for new registrations, CRM synchronisation, or automatic follow-up emails via external systems. Want to be notified when this ships? Submit a request on the roadmap 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 per-ticket fee (€0.99 + 2.75 %) 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.

Cloudflare (Infrastructure)

The entire platform runs on Cloudflare Workers. Files (logos, PDFs, images) are stored in Cloudflare R2. Custom domains automatically receive SSL certificates via Cloudflare for SaaS. The global CDN ensures fast loading times regardless of the participants' location.