XML - Bus Incidents

What this operation does

XML - Bus Incidents

• GETReads dataapi.wmata.com/BusIncidents

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Wmata Incidents operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Wmata Incidents operations

• XML - Rail IncidentsGET · reads data
• XML - Elevator/Escalator OutagesGET · reads data
• JSON - Rail IncidentsGET · reads data
• JSON - Bus IncidentsGET · reads data
• JSON - Elevator/Escalator OutagesGET · reads data

All 6 Wmata Incidents operations

Questions

Can HumDay xml - bus incidents in Wmata Incidents?

Yes. This operation is published in Wmata Incidents's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my Wmata Incidents account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Wmata Incidents.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Wmata Incidents account.

Where this came from

Read from a published API description for Wmata Incidents at developer.wmata.com/docs/services/54763641281d83086473f232/export?DocumentFormat=Swagger. The description above is the provider’s own wording, not ours. Last published 2021-06-21.