Skip to main content
This documentation is for white-label integrators who host their own branded event listing and ticket checkout while UnderPass handles inventory, orders, payments, tickets and settlement behind the scenes.

What you get

A small, stable HTTP API that covers the whole sales journey:
  • List events for your tenant account and render an event page with localities, ticket types, selling stages, prices, dates and organizer info
  • Reserve tickets the moment a buyer picks them, so nobody is sold a ticket that is gone
  • Sell seats on numbered localities, with a public seat map and best-available fallback
  • Put buyers in a waiting room for high-demand on-sales, without building a queue
  • Start a checkout that redirects the buyer to a hosted payment page, with installments, promo codes, sales links, referrals, group tickets, attendees and bar perks
  • Poll the order after payment to render a confirmation screen
You never handle payments, settlement, taxes, invoices or ticket delivery.

How it fits together

Your frontend, in any framework, calls https://api.underpass.com.co over HTTPS. After a buyer submits checkout you redirect them to the URL we return; they pay there (Bold or ePayco, whichever the organizer configured) and land back on a URL you provide. You poll us to render the confirmation page.

The endpoints

Core sales flow

Per-event features

Anything outside this list is not reachable from the public internet.

Identity & scoping

Requests are scoped to your tenant account UUID (account_id), provided during onboarding. There is no per-user authentication: buyers do not need accounts. Ticket type ids on checkout endpoints implicitly scope to your tenant, because tickets belong to events that belong to your account. Reservations and waiting-room passes belong to a session key you generate per browser. There is no API key on the public surface today. Per-tenant keys for higher-trust integrations (audit logging, dedicated budgets) are on the roadmap; nothing to send yet.

Guides

Quickstart

List → reserve → checkout → confirm, in plain fetch.

Reservations

Hold tickets at selection; take the hold over at checkout.

Multi-date events

A date selector before the tickets; performance_id on every item.

Numbered seating

Read the plan, draw it, pick seats or take the best available.

Waiting room

A fair line for on-sales, with a pass the hold must present.

Group tickets & attendees

Tables and 2-for-1s; one ticket per person or all to the buyer.

Bar perks

Cover with consumo, included or purchasable at checkout.

Ticket attributes

Entry cutoff, late fee and minimum consumption.

Fees & installments

The buyer-facing fee, computed per payment.

Marketing attribution

UTM, click ids and referrer on the order.

Analytics pixels

Required. The Meta and TikTok funnel, deduplicated with the server.

API reference

Every endpoint, payload, response and error code.
Need help? Email developers@underpass.com.co.