Automate Data Regulations.gov

What Data Regulations.gov is

Provides public users access to federal regulatory content.

API host: api.data.gov

What HumDay can read from Data Regulations.gov

These are the operations a schedule or a trigger can watch.

• GETReturns Document information/document.{response_format}
• GETSearch for Documents/documents.{response_format}
• GETReturns Docket information/docket.{response_format}

How automating Data Regulations.gov works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. 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.
3. See it proven. The program runs and shows you the result before it is allowed near your live Data Regulations.gov account.
4. Grant access, then go live. You approve the specific Data Regulations.gov operations it may use — and only those.

Questions about Data Regulations.gov automation

Can HumDay connect to Data Regulations.gov?

Yes. HumDay reads Data Regulations.gov's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 3 operations are documented.

Do I need to write code to automate Data Regulations.gov?

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 Data Regulations.gov account.

What can HumDay do in Data Regulations.gov?

0 of the 3 documented operations change something in Data Regulations.gov, and 3 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Data Regulations.gov 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 Data Regulations.gov is held behind that approval.

Where this came from

The operations above are read from a published API description for Data Regulations.gov at regulationsgov.github.io/developers/api-docs.json. Descriptions are the provider’s own words, not ours. Last published 2018-08-24.