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.
Every event exposes an iCalendar file. Drop it into Google Calendar, Outlook or any scheduling tool and the event details come with it.
Signed .pkpass tickets, issued per booking. Buyers add them to Wallet and
scan straight off the lock screen.
Every ticket carries a QR code tied to its order. Our door scanner reads it, and it can only be redeemed once.
Promoters connect their own Stripe account. Charges settle to them directly, so they are the merchant of record for their own event.
Connect an Instagram account to publish event posts, and a Meta ad account to run campaigns against an event without leaving the dashboard.
A public JSON endpoint reporting live platform health, safe to poll from an uptime monitor on a one-minute interval.
These are public, unauthenticated and stable. No key, no signup.
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.
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.
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.