Moshtix APIm.moshtix.com.au ↗
Retrieve structured event data from Moshtix — title, venue, address, start/end times, description, and image URL — for any Australian event listing.
What is the Moshtix API?
The Moshtix API exposes 8 structured fields per event through a single get_event endpoint, returning the event title, venue name, street address, start and end times, a plain-text description, and the event image URL for any Moshtix listing. Pass either a mobile (m.moshtix.com.au) or desktop (www.moshtix.com.au) event URL and receive a normalised response suitable for calendars, event aggregators, or venue-tracking tools.
curl -X GET 'https://api.parse.bot/scraper/a550282f-416e-4446-99bc-26a200ecf485/get_event?url=https%3A%2F%2Fwww.moshtix.com.au%2Fv2%2Fevent%2Fruby-jackson-this-love-thing-ep-launch%2F194638' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace m-moshtix-com-au-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Moshtix Event API — fetch event details by URL."""
from parse_apis.Moshtix_Event_API import Moshtix, EventNotFound
client = Moshtix()
# Fetch event details by providing the event page URL.
event = client.events.get(url="https://www.moshtix.com.au/v2/event/ruby-jackson-this-love-thing-ep-launch/194638")
print(event.title, "|", event.start_date, event.start_time)
print("Venue:", event.venue)
print("Location:", event.location)
print("Image:", event.image_url)
# Typed error handling: catch EventNotFound for invalid/removed event URLs.
try:
missing = client.events.get(url="https://www.moshtix.com.au/v2/event/nonexistent-event/999999")
print(missing.title)
except EventNotFound as exc:
print(f"Event not found: {exc.url}")
print("exercised: events.get / EventNotFound error handling")
Retrieve details for a single Moshtix event given its direct URL. Returns the event title, start date/time, end time, venue name, street address, a brief description, and the event image URL. Accepts both mobile (m.moshtix.com.au) and desktop (www.moshtix.com.au) URLs.
| Param | Type | Description |
|---|---|---|
| urlrequired | string | Direct URL to a Moshtix event page (e.g. https://www.moshtix.com.au/v2/event/ruby-jackson-this-love-thing-ep-launch/194638). Both mobile and desktop URLs are accepted. |
{
"type": "object",
"fields": {
"url": "string (canonical event URL)",
"title": "string",
"venue": "string (building/venue name)",
"end_time": "string (HH:MM:SS, 24-hour)",
"location": "string (street address with suburb, state, postcode)",
"image_url": "string (absolute URL to event image)",
"start_date": "string (ISO date YYYY-MM-DD)",
"start_time": "string (HH:MM:SS, 24-hour)",
"description": "string (plain text, 2-3 sentences)"
},
"sample": {
"data": {
"url": "https://www.moshtix.com.au/v2/event/ruby-jackson-this-love-thing-ep-launch/194638",
"title": "Ruby Jackson 'This Love Thing' EP Launch",
"venue": "The Lansdowne Hotel, Sydney",
"end_time": "22:30:00",
"location": "2-6 City Rd, Chippendale, NSW, 2008",
"image_url": "https://www.moshtix.com.au/uploads/e6417f69-cd02-41cd-8149-ed3ffd2b4b1cx600x600",
"start_date": "2026-06-20",
"start_time": "19:30:00",
"description": "Buy Ruby Jackson 'This Love Thing' EP Launch tickets for 2026 at Moshtix. Taking place at The Lansdowne Hotel, Sydney on June 20th, 2026, you can find more ticket and event information, lineup, artists, set times and extra show dates online."
},
"status": "success"
}
}About the Moshtix API
What the API Returns
The get_event endpoint accepts a single url parameter — a direct link to any Moshtix event page — and returns a flat JSON object with 8 fields. Core scheduling fields include start_date (ISO YYYY-MM-DD), start_time, and end_time (both HH:MM:SS in 24-hour format). Venue data is split between venue (the building or venue name) and location (the full street address including suburb, state, and postcode), giving you enough to geocode or display a map pin without additional lookups.
URL Handling and Coverage
The endpoint accepts both m.moshtix.com.au and www.moshtix.com.au URLs, normalising them to a canonical url in the response. This means you can pass whichever URL format you encounter — from a mobile share link or a desktop browser — without preprocessing. Coverage is limited to events listed on Moshtix, Australia's domestic ticketing platform, so events hosted on other ticketing services are out of scope.
Description and Media Fields
The description field returns a plain-text summary of 2–3 sentences drawn from the event page, suitable for display in cards or search snippets without HTML stripping. The image_url field is an absolute URL to the event's primary promotional image, ready to use in <img> tags or social preview cards.
The Moshtix API is a managed, monitored endpoint for m.moshtix.com.au — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when m.moshtix.com.au changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official m.moshtix.com.au API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate upcoming Australian live music gigs by pulling
title,venue, andstart_datefrom Moshtix event URLs - Build a venue-specific calendar by extracting
locationandstart_timefor all events at a given address - Populate event preview cards in a mobile app using
title,description, andimage_url - Geocode event locations by passing the
locationfield (suburb, state, postcode) to a mapping API - Monitor event scheduling changes by comparing
start_dateandstart_timeacross periodic fetches - Sync Moshtix event details into a CRM or newsletter platform using structured
venueandstart_datefields
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Moshtix have an official developer API?+
What does `get_event` return for the venue location?+
venue field contains the building or venue name (e.g. a bar or theatre), while location contains the full street address including suburb, state, and postcode. These are returned as separate strings so you can display or geocode them independently.Does the API return ticket pricing or availability?+
Can I retrieve a list of events for a venue or artist without individual URLs?+
How is `end_time` handled when an event page doesn't list a finish time?+
end_time field reflects whatever end time is published on the Moshtix event page. If a specific event does not display an end time, the field may be empty or absent in the response.