Automate Parliament Statutory Instruments
HumDay reads Parliament Statutory Instruments’s own published API description and derives 10 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 Parliament Statutory Instruments is
An API exposing details of the various types of Statutory Instruments laid before Parliament.
What HumDay can read from Parliament Statutory Instruments
These are the operations a schedule or a trigger can watch.
- GETReturns a list of statutory instruments.
/api/v1/StatutoryInstrument - GETReturns a list of proposed negative statutory instruments.
/api/v1/ProposedNegativeStatutoryInstrument - GETReturns business item by ID.
/api/v1/BusinessItem/{id} - GETReturns all procedures.
/api/v1/Procedure - GETReturns all laying bodies.
/api/v1/LayingBody - GETReturns business items belonging to statutory instrument with ID.
/api/v1/StatutoryInstrument/{id}/BusinessItems - GETReturns procedure by ID.
/api/v1/Procedure/{id} - GETReturns business items belonging to a proposed negative statutory instrument.
/api/v1/ProposedNegativeStatutoryInstrument/{id}/BusinessItems - GETReturns a statutory instrument by ID.
/api/v1/StatutoryInstrument/{id} - GETReturns proposed negative statutory instrument by ID.
/api/v1/ProposedNegativeStatutoryInstrument/{id}
How automating Parliament Statutory Instruments 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 Parliament Statutory Instruments account.
- Grant access, then go live. You approve the specific Parliament Statutory Instruments operations it may use — and only those.
Automate Parliament Statutory Instruments with these
- Parliament Annunciator content2 operations
- Parliament Bills19 operations
- Parliament Commons Votes5 operations
- Parliament Erskine May11 operations
- Parliament House of Commons Oral and Written Questions4 operations
- Parliament Lords Votes5 operations
- Parliament Members43 operations
- Parliament Treaties6 operations
- Parliament Written Questions7 operations
- UK Parliament Search3 operations
- Monarchinitiative BioLink164 operations
- UniCourt Enterprise158 operations
Categories
Questions about Parliament Statutory Instruments automation
- Can HumDay connect to Parliament Statutory Instruments?
- Yes. HumDay reads Parliament Statutory Instruments's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 10 operations are documented.
- Do I need to write code to automate Parliament Statutory Instruments?
- 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 Parliament Statutory Instruments account.
- What can HumDay do in Parliament Statutory Instruments?
- 0 of the 10 documented operations change something in Parliament Statutory Instruments, and 10 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Parliament Statutory Instruments 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 Parliament Statutory Instruments is held behind that approval.
Where this came from
The operations above are read from a published API description for Parliament Statutory Instruments at statutoryinstruments-api.parliament.uk/swagger/v1/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-03.