GET Matrix Endpoint in GraphHopper Directions
A documented GraphHopper Directions 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
GET Matrix Endpoint
- GETReads data · Matrix API
graphhopper.com/matrix
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 GraphHopper Directions 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 GraphHopper Directions operations
- POST route optimization problemPOST · changes data
- Map-match a GPX filePOST · changes data
- POST Route EndpointPOST · changes data
- POST Matrix EndpointPOST · changes data
- POST Cluster EndpointPOST · changes data
- POST route optimization problem (batch mode)POST · changes data
- Batch Matrix EndpointPOST · changes data
- Batch Cluster EndpointPOST · changes data
Questions
- Can HumDay get matrix endpoint in GraphHopper Directions?
- Yes. This operation is published in GraphHopper Directions'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 GraphHopper Directions account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in GraphHopper Directions.
- 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 GraphHopper Directions account.
Where this came from
Read from a published API description for GraphHopper Directions at docs.graphhopper.com/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-07-19.