Legistar Meetings API
Read-only live JSON access to a configured Legistar Web API client. The source Help catalog names meetings Events and requires a client database code; this service uses LEGISTAR_CLIENT (default: seattle) and applies body/date filtering and opaque local pagination to the observed Events array. The source exposes agenda and minutes links but no separate packet field, so packet_url is null.
Endpoint health
Loading verification…
Connect your agent
Connect through MCP so your agent can find this API, read its docs, and call its endpoints.
Add the server from your terminal.
claude mcp add --transport http agent-data https://agent-data.motie.dev/mcpIn 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 Legistar Meetings API for your task.
Call it over HTTP
Get an API keySign 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.
curl --request GET --get 'https://3kpkg0jfvk.execute-api.us-east-2.amazonaws.com/prod/77570a35-dc2d-4cac-8cc1-39377fec1285/meetings' \
--header "Authorization: Bearer $AGENT_DATA_API_KEY"Endpoints
Inputs and response fields for every endpoint in this API.
GETMeetings/meetings
Fetches the configured client's live Events array, then filters by body and inclusive ISO dates. body accepts an observed body name or numeric body ID. cursor is an opaque continuation returned by this route; the upstream Events operation has no cursor parameter and is capped by the source response, so pagination is local over the fetched array.
Input
bodyOptionalQuery · string | nullObserved EventBodyName or EventBodyId.
Example: Civil Rights, Utilities, Economic Development, and Arts Committee
fromOptionalQuery · string (date) | nullInclusive ISO calendar date applied to EventDate.
Example: 2017-08-01
toOptionalQuery · string (date) | nullInclusive ISO calendar date applied to EventDate.
Example: 2017-08-31
cursorOptionalQuery · string | nullOpaque continuation returned as next_cursor.
Response
itemsobject[]items[].bodystring | nullitems[].titlestring | nullitems[].body_id?integer | nullitems[].comment?string | nullitems[].location?string | nullitems[].agenda_urlstring | nullitems[].meeting_idintegeritems[].packet_urlstring | nullitems[].source_urlstringitems[].status_rawstring | nullitems[].minutes_urlstring | nullitems[].observed_atstringitems[].meeting_datestring | nullitems[].meeting_time?string | nullitems[].source_as_ofstring | nullnext_cursorstring | nullobserved_atstringsource_countintegersource_clientstringFields 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}
Gets one source Event by its stable EventId and maps it to a meeting record.
Input
meeting_idRequiredPath · integerLegistar EventId returned by /meetings.
Example: 2910
Response
bodystring | nulltitlestring | nullbody_id?integer | nullcomment?string | nulllocation?string | nullagenda_urlstring | nullmeeting_idintegerpacket_urlstring | nullsource_urlstringstatus_rawstring | nullminutes_urlstring | nullobserved_atstringmeeting_datestring | nullmeeting_time?string | nullsource_as_ofstring | nullFields marked ? are optional.
GETMeetings by meeting id documents/meetings/{meeting_id}/documents
Gets source EventItems and returns structured event-level agenda/minutes links plus MatterAttachment records. Hyperlink attachments populate url; file/binary attachments populate file_name/content_base64 because the source does not provide a public file URL. An empty list is a valid source result.
Input
meeting_idRequiredPath · integerLegistar EventId returned by /meetings.
Example: 2910
Response
0object0.urlstring | null0.titlestring | null0.file_name?string | null0.meeting_idinteger0.source_urlstring0.document_idstring0.observed_atstring0.source_as_ofstring | null0.document_typestring0.content_base64?string | nullFields 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.
An account is required to submit an extension. Prepare your request, then sign in to build.