Build any site. Konecto is the backend.
Public API, SDK, drop-in ticket components and webhooks. Checkout stays on Konecto, so you never touch card data.
Free for free events. No card needed.
<!-- Any site, any host -->
<script src="https://cdn.konec.to/components.js" defer></script>
<konecto-tickets event="founders-london" key="pk_live_…"></konecto-tickets>
// Or with the SDK
import { Konecto } from '@konecto/sdk';
const k = new Konecto({ publishableKey: 'pk_live_…' });
const event = await k.events.get('founders-london');
const { url } = await k.checkout.create({ ticketType: 'standard', quantity: 2 });
location.href = url; // Konecto checkoutIn short
Konecto is a headless events backend. Developers build fully custom event sites anywhere and use the Konecto Public API, TypeScript SDK and drop-in components for event data, ticket availability and checkout, with signed webhooks for orders and check-ins.
“Our client wanted a custom site.”
- Building ticketing, payments and check-in yourself takes months.
- Embedded widgets rarely match a bespoke design.
- Handling card data brings compliance work nobody wants.
Read events, agenda, speakers and availability from the Public API with a publishable key limited to your domains. Send buyers to Konecto checkout. Listen for webhooks. Attendees still get their tickets in the Konecto attendee app.
Do it in the Konecto organiser app, or ask your AI to do it for you.
Three steps.
Get keys
A publishable key for the browser, a secret key for your server.
Build
Use the SDK or drop in <konecto-tickets>.
Listen
Webhooks for orders, refunds and check-ins.
FAQ
Is the API free?
Yes. The API is part of the free core; paid tickets carry the usual ticket fee.
Do I handle payments?
No. Checkout always runs on Konecto through Stripe.
Can I replace the attendee app?
No. Attendees always get their tickets and network in the Konecto attendee app.
Is there an OpenAPI spec?
Yes, plus an SDK and LLM-friendly docs.
Your next event, connected.
Free for free events. No card needed.