# Moshtix Event Details API

> One Moshtix event page by its URL: its title, date and url.

- Page: https://cleanedweb.com/catalog/moshtix-event-details-api/
- Contract (JSON): https://cleanedweb.com/catalog/moshtix-event-details-api/contract.json
- Source: moshtix.com.au (https://www.moshtix.com.au/)
- Category: Businesses & places
- Updated: 2026-11-20

A run reads the one page you name and returns its record; `max_items`, `timeout_seconds` and your budget still bound it.

## Key fields

| Field | Type | Sample value |
| --- | --- | --- |
| `title` | string | `The Australian Pantera Show` |
| `date` | string | `2027-05-21T20:00:00` |
| `url` | string | `https://www.moshtix.com.au/v2/event/the-australian-pantera-show/194404` |
| `event_details` | string | `Event Details The Australian Pantera Show performs in Devonport Devonport, are …` |
| `other_events` | array of object | not in the saved sample |

Sample values come from one saved record, not a live run. Every field with its type, and the schemas, are in https://cleanedweb.com/catalog/moshtix-event-details-api/contract.json. Some fields the source returns are not published, so a record can carry fields the schema does not list.

## Inputs

- `url` (string, required): Paste the URL of a moshtix.com.au page of the same kind as the sample: its path looks like /{code}/event/{slug}/{int}. Any such page works, not only the one the API was built from.

## Request

`POST https://api.cleanedweb.com/v1/catalog/public/apis/generated_368a38fad7703c593a0f7a94/endpoints/generated_368a38fad7703c593a0f7a94_search/run`

```bash
curl -X POST https://api.cleanedweb.com/v1/catalog/public/apis/generated_368a38fad7703c593a0f7a94/endpoints/generated_368a38fad7703c593a0f7a94_search/run \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Idempotency-Key: UNIQUE_REQUEST_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "input": {
    "url": "https://www.moshtix.com.au/v2/event/the-australian-pantera-show/194404"
  },
  "version": 1,
  "max_items": 25
}'
```

Send an `Idempotency-Key` header with every run and save it before you send. Reuse it only to retry the same request. If the run does not end within `wait_seconds`, read the result with the same API key and key:

`GET https://api.cleanedweb.com/v1/catalog/public/apis/generated_368a38fad7703c593a0f7a94/endpoints/generated_368a38fad7703c593a0f7a94_search/result`

## Versions

Current: `1.0`. Pin a major with "version": N in the run body (an integer). Leave it out and the call runs on the latest major. A sunset major runs on the latest major and the response says rerouted. An unknown major answers 404 catalog_version_not_found and lists the available majors.

- v1: current, newest minor `1.0`

### Changelog

- `1.0` (major) 2026-11-18

The same changelog, as data, is in https://cleanedweb.com/catalog/moshtix-event-details-api/contract.json

## Use it from an AI agent

MCP server: https://api.cleanedweb.com/mcp?profile=catalog (Streamable HTTP). Sign in with a CleanedWeb account when the client asks (OAuth), or send an API key with the `read` and `run` scopes as `Authorization: Bearer`. Call `get_api` with `api_id` `generated_368a38fad7703c593a0f7a94`, then `run_api` with the `run_with` arguments it returns. See https://cleanedweb.com/docs/mcp/

## Run it

Reading the catalog needs no credential. Running needs a CleanedWeb account and an API key with the `run` scope; the first 5,000 records are free, then $1 per 1,000 records. See https://cleanedweb.com/docs/run-catalog-api/

CleanedWeb is not affiliated with Moshtix.
