Put Zambian events on your site

What you can read

Published events: title, description, venue and city, start and end times, cover image, category, and the ticket tiers with their prices in kwacha. Enough to list an event and link people to buy.

No buyer data, ever. No names, e-mail addresses, phone numbers or ticket holders cross this boundary — not filtered out on request, simply not in the responses. Integrating carries no privacy weight for either of us.

Getting a key

E-mail support@octotickets.com and say who you are and where the events will appear. We issue keys by hand — there is no self-service signup — so expect a reply from a person rather than a dashboard.

Your key is shown once and stored only as a hash, so we cannot read it back to you. Keep it somewhere safe and out of your front-end code; ask and we will issue a replacement, which retires the old one immediately.

Calling it

Send the key as a bearer token. Everything else is an ordinary GET.

GET /v1/partner/events?limit=20
Host: api.octotickets.com
Authorization: Bearer octo_pat_…

One event from the response, trimmed:

{
  "events": [
    {
      "slug": "kwacha-sounds-festival",
      "title": "Kwacha Sounds Festival",
      "venue": "Agricultural Showgrounds",
      "city": "Lusaka",
      "category": "Festivals",
      "startAt": "2026-10-03T16:00:00.000Z",
      "endAt": "2026-10-03T22:00:00.000Z",
      "imageUrl": "https://…",
      "tiers": [{ "name": "General", "price": 150 }]
    }
  ],
  "nextCursor": null
}

Filter with q, category, city, dateFrom and dateTo; page with cursor and limit. Fetch one event directly at /v1/partner/events/{slug}.

Times are UTC instants; events happen on Zambian time, CAT (UTC+2). Prices are Zambian kwacha.

Things worth knowing before you build

• Only published events appear. An organizer taking an event off sale removes it from your results on the next call, so treat a disappearance as normal rather than an error.
• There is a per-key rate limit (60 requests a minute by default). Ask if you need more; tell us roughly what traffic you expect and we will set it rather than guess.
• Link to us to sell. There is no ticket-buying API — send people to the event page and the purchase happens on Octo, so you never handle money or personal details.
• Tell us before you go live at volume. Not a rule, a courtesy that means someone is watching when your traffic arrives.