Automate Openstates Open States
HumDay reads Openstates Open States’s own published API description and derives 12 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Openstates Open States is
* [More documentation](https://docs.openstates.org/en/latest/api/v3/index.html) * [Register for an account](https://openstates.org/accounts/signup/) **We are currently working to restore experimental support for committees & events.** During this period please note that data is not yet available for all states and the exact format of the new endpoints may change slightly depending on user feedback
What HumDay can read from Openstates Open States
These are the operations a schedule or a trigger can watch.
- GETEvent List
/events - GETEvent Detail
/events/{event_id} - GETBills Search
/bills - GETPeople Search
/people - GETCommittee List
/committees - GETJurisdiction List
/jurisdictions - GETMetrics
/metrics - GETPeople Geo
/people.geo - GETCommittee Detail
/committees/{committee_id} - GETJurisdiction Detail
/jurisdictions/{jurisdiction_id} - GETBill Detail By Id
/bills/ocd-bill/{openstates_bill_id} - GETBill Detail
/bills/{jurisdiction}/{session}/{bill_id}
How automating Openstates Open States works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Openstates Open States account.
- Grant access, then go live. You approve the specific Openstates Open States operations it may use — and only those.
Automate Openstates Open States with these
- Monarchinitiative BioLink164 operations
- UniCourt Enterprise158 operations
- OSF APIv2 Documentation156 operations
- IllumiDesk143 operations
- Figshare136 operations
- MCW Rat Genome Database100 operations
- U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
- OpenFEC91 operations
- NBA Stats83 operations
- Thebluealliance The Blue Alliance65 operations
- eDRV57 operations
- Collegefootballdata College Football Data51 operations
Categories
Questions about Openstates Open States automation
- Can HumDay connect to Openstates Open States?
- Yes. HumDay reads Openstates Open States's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 12 operations are documented.
- Do I need to write code to automate Openstates Open States?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Openstates Open States account.
- What can HumDay do in Openstates Open States?
- 0 of the 12 documented operations change something in Openstates Open States, and 12 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Openstates Open States account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Openstates Open States is held behind that approval.
Where this came from
The operations above are read from a published API description for Openstates Open States at v3.openstates.org/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.