Automate DriveBC's Open511
HumDay reads DriveBC's Open511’s own published API description and derives 4 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 DriveBC's Open511 is
This API is DriveBC's implementation of the Open511 specification. It provides information about known road events (traffic accidents, construction, etc.) in British Columbia, Canada. Please note that you may experience issues when submitting requests to the delivery or test environment if using this [OpenAPI specification](https://github.com/bcgov/api-specs) in other API console viewers.
API host: api.open511.gov.bc.ca
What HumDay can read from DriveBC's Open511
These are the operations a schedule or a trigger can watch.
- GETLists road events
/events - GETLists the geographical areas (e.g.
/areas - GETLists the jurisdictions publishing data through this Open511 API implementation
/jurisdiction - GETProvides the geographical boundaries for all the jurisdictions.
/jurisdictiongeography
How automating DriveBC's Open511 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 DriveBC's Open511 account.
- Grant access, then go live. You approve the specific DriveBC's Open511 operations it may use — and only those.
Automate DriveBC's Open511 with these
- BC Data Catalogue22 operations
- BC Geocoder16 operations
- BC Geographical Names14 operations
- BC GeoMark7 operations
- BC Gov News 1.027 operations
- BC Groundwater Wells, Aquifers and Registry24 operations
- BC Route Planner24 operations
- WorkBC Job Posting5 operations
- Monarchinitiative BioLink164 operations
- UniCourt Enterprise158 operations
- OSF APIv2 Documentation156 operations
- IllumiDesk143 operations
Categories
Questions about DriveBC's Open511 automation
- Can HumDay connect to DriveBC's Open511?
- Yes. HumDay reads DriveBC's Open511's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 4 operations are documented.
- Do I need to write code to automate DriveBC's Open511?
- 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 DriveBC's Open511 account.
- What can HumDay do in DriveBC's Open511?
- 0 of the 4 documented operations change something in DriveBC's Open511, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my DriveBC's Open511 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 DriveBC's Open511 is held behind that approval.
Where this came from
The operations above are read from a published API description for DriveBC's Open511 at raw.githubusercontent.com/bcgov/api-specs/master/open511/open511_OAS3.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.