Catalog / Austin City Council Meetings

Austin City Council Meetings API

austintexas.gov

Live, read-only Austin City Council and related public meeting records from the City Clerk's Council Meeting Information Center. The service retrieves public HTML pages over HTTP on each request. Time and location remain null when the source does not publish them. The landing page publishes one next meeting and five recent meetings; an explicit date range outside that window can also use the linked year archive.

  • Other
  • Austin
  • city council
  • civic
  • meetings
2 endpointsDocs updated

Endpoint health

Loading verification…

Connect your agent

Connect through MCP so your agent can find this API, read its docs, and call its endpoints.

Setup guide

Add the server from your terminal.

Claude Code · terminal
claude mcp add --transport http agent-data https://agent-data.motie.dev/mcp

In Claude Code, run /mcp, select agent-data, then Authenticate. Sign in to your agent-data account in the browser.

Then ask your agent to use the Austin City Council Meetings API for your task.

Call it over HTTP

Get an API key

Sign up free, generate an API key, and set it as AGENT_DATA_API_KEY in your environment. Your first 100 calls each month are free.

Returns source-published next/recent meetings in ascending date order. Use ISO dates for inclusive from/to filtering, upcoming=true for meetings on or after today's date in America/Chicago, and type for a source-derived type such as regular, work_session, special, or ahfc. A cursor is the continuation token returned by a prior response; live source results can change between requests.

Optional parameters 6

Inclusive start date (ISO 8601).

Inclusive end date (ISO 8601).

When true, keep meetings dated today or later in America/Chicago.

Source-derived meeting type, for example regular, work_session, special, or ahfc.

Continuation token returned by a prior response.

Number of meetings to return.

View call pricing
cURL · Meetings
curl --request GET --get 'https://3kpkg0jfvk.execute-api.us-east-2.amazonaws.com/prod/ce749988-dec6-4f47-9a3d-168009036ec7/meetings' \
  --header "Authorization: Bearer $AGENT_DATA_API_KEY"

Endpoints

Inputs and response fields for every endpoint in this API.

GETMeetings/meetings

Returns source-published next/recent meetings in ascending date order. Use ISO dates for inclusive from/to filtering, upcoming=true for meetings on or after today's date in America/Chicago, and type for a source-derived type such as regular, work_session, special, or ahfc. A cursor is the continuation token returned by a prior response; live source results can change between requests.

Input

fromOptionalQuery · string (date) | null

Inclusive start date (ISO 8601).

Example: 2026-09-22

toOptionalQuery · string (date) | null

Inclusive end date (ISO 8601).

Example: 2026-10-08

upcomingOptionalQuery · boolean, default: false

When true, keep meetings dated today or later in America/Chicago.

Example: true

typeOptionalQuery · string | null

Source-derived meeting type, for example regular, work_session, special, or ahfc.

Example: regular

cursorOptionalQuery · string | null

Continuation token returned by a prior response.

limitOptionalQuery · integer, min: 1, default: 20

Number of meetings to return.

Example: 20

Response

sourcestring
meetingsobject[]
meetings[].bodystring
meetings[].note?string | null
meetings[].titlestring
meetings[].status?string | null
meetings[].location?string | null
meetings[].documents?object[]
meetings[].documents[].urlstring
meetings[].documents[].typestring
meetings[].documents[].titlestring
meetings[].documents[].size_text?string | null
meetings[].meeting_idstring
meetings[].source_urlstring
meetings[].agenda_urls?string[]
meetings[].observed_atstring (date-time)
meetings[].meeting_datestring (date)
meetings[].meeting_time?string (date-time) | null
meetings[].meeting_typestring
meetings[].source_updated_at?string (date-time) | null
next_cursor?string | null
observed_atstring (date-time)

Fields marked ? are optional.

For the next page, pass next_cursor from the response as cursor. Leave it empty on the first call.

GETMeetings by meeting id/meetings/{meeting_id}

Fetches the City Clerk detail page for the stable meeting slug returned by the list operation, including published agenda/minutes/document links and the page-updated timestamp.

Input

meeting_idRequiredPath · string

Stable City Clerk meeting slug, such as 20261022-reg.

Example: 20261022-reg

Response

bodystring
note?string | null
titlestring
status?string | null
location?string | null
documents?object[]
documents[].urlstring
documents[].typestring
documents[].titlestring
documents[].size_text?string | null
meeting_idstring
source_urlstring
agenda_urls?string[]
observed_atstring (date-time)
meeting_datestring (date)
meeting_time?string (date-time) | null
meeting_typestring
source_updated_at?string (date-time) | null

Fields marked ? are optional.

Don’t see the endpoint you need?

Ask agent-data to add an endpoint or return more fields. Extensions are free and keep existing endpoints working.