Ways to take data out

CapitolMath's data doesn't have to stay in CapitolMath. The Integration menu at the top of every page gathers each way to take it somewhere else — onto your website, into a Slack channel, into your own code or a data warehouse. Integration lists them on one page, with who in an organization can use each.

Which one fits depends on where the data is going and who will read it there.

On your website: widgets#

A widget puts live bills, meetings, elected officials, a dashboard chart, session dates or a legislator scorecard on your own site. Your page holds a short snippet; what the widget shows comes from CapitolMath and from your saved views, so it stays current without anyone editing the website.

Widgets are free to publish and free to view, and their traffic never counts against your API quota. An organization's Owners and Admins build and publish them. See About widgets.

When something changes: webhooks#

A webhook watches a saved view — or everything your plan covers — and tells you when something in it changes: a bill moves, a hearing is scheduled, moved or canceled. It can deliver to your own HTTPS endpoint, a Slack or Microsoft Teams channel, or a set of email addresses.

Members with a Full license build webhooks; Owners and Admins can see, pause and delete any of them. See About webhooks.

Into your own code: the REST API and MCP#

The REST API searches and reads bills, roll-call votes, legislators, committees and the calendar, with CapitolMath's derived measures. Every endpoint is documented, and can be tried live, in the API reference. The same API is described as an OpenAPI 3.1 spec, which you can import into Postman or use to generate a client.

The MCP server offers the same data as tools for AI assistants such as Claude, over the Model Context Protocol, using the same API key.

Both need an API key, which a member with a Full license creates on their profile. See Creating an API key and the API quickstart.

Whole jurisdictions as files: bulk datasets#

Bulk datasets are everything in CapitolMath as files, rebuilt every night: one per state (or all states together) and, where the data has years, one per year, in CSV and Parquet. Their columns match the API's, so downloads and API responses join on the same keys. Where effective dates are live, the Effective dates dataset has each enacted law's dates with how each was worked out, a row per date, joining to Bills by jurisdiction, session and bill number.

Downloading them needs a plan that includes bulk datasets and a Full license. Everyone in an organization can see what's there.

One list at a time: Export CSV#

The Legislation, Elected Officials, Committees and Calendar pages each have an Export CSV button beside the search box. It exports what the page is showing, with your filters applied.

If you can read your organization's tracked items, the Legislation export ends with your tracking: whether you track each bill, and its position, priority, status, owner and tags. It holds only what the Ours line on each bill shows you. Tracked items, Tasks and Reports have their own Export CSV.

Exporting needs a Full license. On a plan that covers one state, you can export that state only. When the button can't be used, it stays on the page, dimmed, and hovering over it says why.