JSON - Lines in Wmata Rail Station Information
A documented Wmata Rail Station Information operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
JSON - Lines
- GETReads data
api.wmata.com/json/jLines
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Wmata Rail Station Information operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Wmata Rail Station Information operations
- XML - Station ListGET · reads data
- JSON - Station ListGET · reads data
- XML - Path Between StationsGET · reads data
- XML - Station InformationGET · reads data
- XML - Station TimingsGET · reads data
- XML - Parking InformationGET · reads data
- XML - Station EntrancesGET · reads data
- XML - Station to Station InformationGET · reads data
Questions
- Can HumDay json - lines in Wmata Rail Station Information?
- Yes. This operation is published in Wmata Rail Station Information'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 Rail Station Information 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 Rail Station Information.
- 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 Rail Station Information account.
Where this came from
Read from a published API description for Wmata Rail Station Information at developer.wmata.com/docs/services/5476364f031f590f38092507/export?DocumentFormat=Swagger. The description above is the provider’s own wording, not ours. Last published 2021-06-21.