· 3 min read
Show your events on your own website with a TixFix API key
Create an API key in Settings, list your published upcoming events on your own site, and revoke the key if it ever leaks. Who can make one and how to use it.

Your website is where regulars look first. If your events page is a hand-edited list, it is out of date the day someone changes a start time or sells out. A better setup is a page that reads your upcoming events straight from TixFix, so the site and the ticket page always agree. That is what an API key is for. This post covers who can create one, where it lives, and the habits that keep it safe.
What an API key does
An API key lets your own website ask TixFix for your list of published upcoming events. Draft events are not part of that list, and neither are events that already happened, so a visitor only sees what they can actually buy a ticket to.
The point is that you stop copying details by hand. Update the date or venue in TixFix, and the list your site reads reflects it. Whoever builds or maintains your website, whether that is you, a volunteer or a freelancer, uses the key to fetch the list and show it in your own design.
Where to find it
Keys are made in the organizer web app at Settings, then API Keys. Only owners and admins of the organization can create them, so other team roles cannot create them. If you cannot find it, check your team role first.
Three facts worth knowing before you click:
- You can have two keys at a time.
- A key can be revoked whenever you choose.
- A key is for listing your published upcoming events on your own site, which is the job it was built for.
The step-by-step page is in the docs at API keys.
Why two keys
Two slots are useful because keys sometimes need replacing. Say your current key is used on the live website. A new developer takes over and you want a fresh one. Create the second key, switch the site to it, confirm the events page still loads, then revoke the first. There is no gap where your page is broken, and the old key stops working for good.
Use the same approach on a schedule if you like. A key that has been in an old developer's notes for a year is a key worth replacing.
Keeping a key safe
Treat it like a password. A few simple rules:
- Keep it out of public places: a shared document, a screenshot in a group chat, a public code repository.
- Give it only to the person who needs it, and tell them what it is for.
- If anyone who had it leaves the team, or you are not sure where it ended up, revoke it and create another.
- Name where each key is used in your own notes, so you know which one to revoke without guessing.
Because revoking is always available, a leak is an annoyance, not a disaster. You revoke, create a new key and update your site.
What to put on your events page
Once the list is coming through, design the page for a visitor who has thirty seconds:
- Show the next event first, with date, venue and price.
- Link each event to its TixFix ticket page so buying takes one click.
- Keep an empty state ready: "No events right now, follow us for the next one" beats a blank gap.
- Test the page on a phone. Most of your audience will see it there.
Your site stays the home for your story and photos, and the ticket page does the selling.
When you do not need a key
If all you want is a place to send people, the public event page already exists for every published event, and short links such as app.tixfix.ai/xxxxxxxx work well on posters and bios. A key is for the case where you want your own site to display the list itself.
TixFix organizers who run their own site can create API keys under Settings to list published upcoming events there. See how it works for organizers or browse events by city.