Got Tickets Online
Developers

Build on
GotTickets.

Feeds, passes and integrations that are live in production today — plus a straight answer about the REST API, which is available on request rather than open to the public. We would rather tell you that than hand you a URL nobody supports.

Available now

What you can integrate with today

Live

Calendar feeds

Every event exposes an iCalendar file. Drop it into Google Calendar, Outlook or any scheduling tool and the event details come with it.

Live

Apple Wallet passes

Signed .pkpass tickets, issued per booking. Buyers add them to Wallet and scan straight off the lock screen.

Live

QR check-in

Every ticket carries a QR code tied to its order. Our door scanner reads it, and it can only be redeemed once.

Live

Stripe Connect

Promoters connect their own Stripe account. Charges settle to them directly, so they are the merchant of record for their own event.

Live

Meta & Instagram

Connect an Instagram account to publish event posts, and a Meta ad account to run campaigns against an event without leaving the dashboard.

Live

Status feed

A public JSON endpoint reporting live platform health, safe to poll from an uptime monitor on a one-minute interval.

Reference

Endpoints you can use without asking us

These are public, unauthenticated and stable. No key, no signup.

GET https://gottickets.online/events/{event}/calendar.ics iCalendar feed for a single event. {event} is the event id. GET https://gottickets.online/status.json Live platform status. Cached 60s. Returns an overall status plus one object per check. Browsers are redirected to the human status page; add ?format=json to read the raw feed in one.

Wallet passes and ticket downloads are deliberately not in that list: they are tied to a specific booking and are served only to the person who holds it, or against a signed link. That is a privacy boundary, not an oversight.

The REST API

Access on request

We will give you an honest answer, not a sandbox key

There is a programmatic interface behind the platform, and we do open it up — for integrators with a concrete use case, on a per-partner basis, with support attached. What we do not do is publish a self-serve public API and quietly let it rot.

Tell us what you are building — a box-office sync, a venue calendar, a promoter's own site pulling their events — and we will tell you whether it is something we can support today, and what it would take if not.

Working with us

What to expect

🔐
Least access, always. An integration gets scoped to the events and the data it actually needs. Nobody gets buyer email addresses because it would be convenient.
📉
We tell you before we break you. Anything we open to a partner gets a deprecation notice and a migration window, not a surprise 404.
🚨
Incidents are public. If something we run is failing, it shows on the status page whether or not anyone has noticed yet.
Security

Reporting a vulnerability

If you have found a security problem, email Info@Gottickets.online with enough detail to reproduce it. We will acknowledge it, keep you updated while we fix it, and credit you if you want the credit.

Please do not run automated scans against production, and please do not access, alter or download anyone else's data to prove a point — a description is enough.