austintexas APIaustintexas.org ↗
Search Austin, TX community events by date range and keyword. Returns titles, dates, locations, descriptions, admission info, and categories from Visit Austin.
What is the austintexas API?
The austintexas.org API exposes 1 endpoint — search_events — that returns up to 11 fields per event from Visit Austin's official event listings, including title, date range, location, admission, and categories. Developers can query concerts, festivals, exhibits, and family activities by date range and optional keyword, with automatic pagination across all matching results.
curl -X GET 'https://api.parse.bot/scraper/0b6c9434-7775-42f2-8880-7e2837379f25/search_events?page=1&limit=20&keyword=music&end_date=2026-07-21&start_date=2026-07-14' \ -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 austintexas-org-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: austintexas_org_api SDK — bounded, re-runnable; every call capped."""
from parse_apis.austintexas_org_api import AustinEvents, InvalidDateFormat
client = AustinEvents()
# Search upcoming events in Austin with a keyword filter
for event in client.events.search(keyword="music", limit=3):
print(event.title, event.date, event.location)
# Get the first event from a broader search and inspect its details
event = client.events.search(start_date="2026-07-14", end_date="2026-07-21", limit=1).first()
if event:
print(event.title, event.description[:100], event.url)
# Handle invalid date format gracefully
try:
client.events.search(start_date="bad-date", limit=1).first()
except InvalidDateFormat as e:
print("invalid date:", e)
print("exercised: events.search")
Search community events in Austin, TX by date range and optional keyword. Returns paginated results with event name, date, description, URL, location, and categories. Results are auto-iterated; the SDK advances pages automatically.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
| limit | integer | Maximum number of events per page. |
| keyword | string | Free-text search term to filter events by title or description. |
| end_date | string | End of date range in YYYY-MM-DD format. Defaults to 7 days after start_date. |
| start_date | string | Start of date range in YYYY-MM-DD format. Defaults to today (UTC). |
{
"type": "object",
"fields": {
"page": "current page number",
"total": "total number of matching events",
"events": "array of event objects with recid, title, date, start_date, end_date, description, url, location, city, admission, recurrence, and categories",
"total_pages": "total number of pages"
},
"sample": {
"data": {
"page": 1,
"total": 171,
"events": [
{
"url": "https://www.austintexas.org/event/american-modernism-from-the-charles-butt-collection/393230/",
"city": "Austin",
"date": "2026-07-14T04:59:59.000Z",
"recid": "393230",
"title": "American Modernism from the Charles Butt Collection",
"end_date": "2026-08-03T04:59:59.000Z",
"location": "Blanton Museum of Art",
"admission": "$15",
"categories": [
"Museums & Exhibits",
"Visual Arts"
],
"recurrence": "Recurring daily",
"start_date": "2026-03-08T06:00:00.000Z",
"description": "Discover the first exhibition dedicated to the remarkable collection of businessman, philanthropist, and Texas native Charles Butt."
}
],
"total_pages": 57
},
"status": "success"
}
}About the austintexas API
What the API covers
The search_events endpoint queries the Visit Austin event calendar at austintexas.org. Each event object in the response includes a recid (unique record identifier), title, date, start_date, end_date, description, url, location, city, admission, recurrence, and categories. This covers the full range of publicly listed Austin events — live music, cultural festivals, outdoor markets, gallery openings, and community gatherings.
Filtering and pagination
Requests accept a start_date and end_date in YYYY-MM-DD format to scope results to a specific window; start_date defaults to today (UTC) and end_date defaults to 7 days out if omitted. A keyword parameter filters results by title or description text. The page and limit parameters control pagination; the SDK auto-iterates pages, so you can consume all matching results without manually incrementing the page counter. Each response includes total, total_pages, and page fields to support your own pagination logic if needed.
Response fields in detail
Beyond basic metadata, the admission field indicates whether an event is free or ticketed. The recurrence field flags recurring events. The categories array lets you bucket events by type — useful for filtering results client-side after retrieval. The url field links directly to the canonical Visit Austin event detail page, where additional details like ticketing links may appear.
The austintexas API is a managed, monitored endpoint for austintexas.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when austintexas.org 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 austintexas.org 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?+
- Build a local event calendar app filtered by date range using
start_dateandend_date - Surface Austin weekend activities in a travel itinerary tool by querying a 2-day window
- Send a weekly email digest of free Austin events by filtering on the
admissionfield - Aggregate recurring community events using the
recurrenceflag for a local newsletter - Populate a map of Austin event venues using the
locationandcityfields - Build a keyword-driven event recommendation engine using the
keywordparameter against user interests - Track upcoming festivals and exhibits by parsing the
categoriesarray for content-type filtering
| 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 austintexas.org provide an official developer API?+
What does the `search_events` endpoint actually return for each event?+
recid, title, date, start_date, end_date, description, url, location, city, admission, recurrence, and categories. The total and total_pages fields in each response let you determine how many events matched and how many pages exist.Does the API cover events outside Austin or statewide Texas events?+
Can I retrieve detailed ticketing or vendor information for an event?+
admission field (free vs. ticketed) and a url linking to the full event detail page, but does not return ticketing platform links, ticket prices, or vendor data. You can fork this API on Parse and revise it to add an endpoint that fetches the individual event URL and extracts those details.How current is the event data, and are past events accessible?+
start_date to a past date may return past events if they are still listed on the source calendar, but Visit Austin typically removes or archives events after they conclude. There is no guarantee of historical completeness for events that have already been removed from the source listing.