Skip to content
  • There are no suggestions because the search field is empty.

How to Access the Public Events API

Retrieve a list of live events for your event directory using an access token

The Public Events API lets you retrieve a list of live events on Sticky Tickets, using an access token. It's designed for event directories that want to pull publicly listed Sticky Tickets events into their own service.

Scope of this endpoint: This API returns list-level event details only. It does not return capacity, organiser/organisation name, contact phone or email, location instructions, or ticket/sub-ticket details — those aren't part of this endpoint's response.

"Live events" means events ending within the next two years. Events scheduled further out than that won't appear in results — worth accounting for if you're syncing events on an ongoing basis.

How to request access

Email support@stickytickets.com.au to request your public access token.

Endpoint

GET https://www.stickytickets.com.au/api/events/search

Authentication

Pass your token using either:

  • A request header named x-sticky-tickets, or
  • A query parameter named accessToken

Use only one method per request — if both are provided and one is stale or invalid, the entire request fails.

Response fields 

FIELD NOTES
id  
name HTML-encoded (see note below)
venue  
suburb  
description HTML-encoded
image Protocol-relative URL (see note below)
tags Event category names, e.g. "Music"
startDate No timezone included (see note below)
endDate No timezone included (see note below)
dateUpdateUtc  
buyText  
eventCode  
parentEventCode  
isHomePageVisible  
eventUrl Protocol unconfirmed — see note below

Sample response

{
  "events": [
    {
      "id": 239250,
      "name": "Jazz & Blues by the River",
      "venue": "Riverside Pavilion",
      "suburb": "Newcastle",
      "description": "Two days of live jazz and blues on the harbour.",
      "image": "//d1a2b3c4d5e6f7.cloudfront.net/events/239250/hero.jpg",
      "tags": ["Music", "Festivals"],
      "startDate": "2026-09-15T19:30:00.000",
      "endDate": "2026-09-16T23:00:00.000",
      "dateUpdatedUtc": "2026-08-20T04:12:07.000",
      "buyText": "Buy Tickets",
      "eventCode": "abc123",
      "isHomePageVisible": true,
      "eventUrl": "https://www.stickytickets.com.au/abc123"
    }
  ],
  "totalHitsFound": 128
}

Things to watch for

  • Dates have no timezone suffix. Confirm the expected timezone with your integration before parsing dates.
  • Image URLs are protocol-relative — they start with // rather than https://. Prepend a protocol yourself if your implementation requires a full URL.
  • Empty fields are omitted entirely, not returned as null. This means different events in the same response may have different sets of fields present — don't assume every field will always be there.
  • Text fields are HTML-encoded. For example, an ampersand in an event name is returned as &, as shown in the sample above.
  • eventUrl protocol is unconfirmed. Internal configuration suggests this may return as http:// rather than https:// — this article will be updated once confirmed against a live token.

Need help?

If you have any questions about the Public Events API, contact our support team.