Ticketing infrastructure for events.

Integrate via API or drop-in elements. We handle inventory, hosted checkout, refunds, and ticket lifecycle.

import { createClient } from '@session-services/sdk';

const client = createClient({
  environment: 'sandbox',
  tenantId: 'your-tenant-id'
});

const { event } = await client.event.get({ key: 'event-slug' });

curl https://api.session.services/events/event-slug \
  -H "x-tenant-id: your-tenant-id"

Trusted by event organisers

Built for teams shipping event products

Marketplaces & platforms

Embed event discovery and ticketing into your product while we run checkout and order lifecycle.

Custom storefronts

Bring your own listings UI, then use the Ticketing Element or API checkout flow to sell tickets.

Operational tooling (auth)

Use authenticated APIs for refunds, scanning, payouts, teams, and operational workflows.

Primitives you can build on

: Every request is scoped with x-tenant-id for strict isolation and routing.
: Create an order, redirect to checkoutUrl, and let us handle payment and confirmation.
: Orders reserve inventory for 10 minutes, then release automatically if abandoned.
: Return URLs include {orderId}?sig=… so customers can view confirmations and tickets without bearer auth.
: Refunds support idempotency keys to prevent duplicate processing.
: Tickets move between ACTIVE and REDEEMED with CHECK_IN and CHECK_OUT scans, and cancel on refunds.
: Web Component and React bindings with typed events like checkoutInit.

Who are we?

Session Services started with a simple observation: ticketing is infrastructure. It’s full of edge cases, operational workflows, and business complexity that most product teams shouldn’t have to rebuild. We’re building a developer-first events layer, designed to be called by your software and your agents.

Explore developer docs

Ready to integrate Session Services?

Book an integration call. We'll confirm fit, provision sandbox access on request, and help you ship an end-to-end flow fast.

Book an integration call