Quadruper API docs
Route, geocode and measure travel time in the Philippines with one JSON API.
Build with the API
From no account to a route on your screen.
- Request a key
- Store it outside your code
- Send your first route
- Read the response
Building with an AI agent?
Paste this line into your coding agent.
Read https://quadruper.com/llms.txt before using the Quadruper API.
Find the right endpoint
| You want to | Call | Key required |
|---|---|---|
| Get a route, distance and ETA between 2 to 10 points | POST /v2/route |
Key or our website |
| Compare travel times across many places at once | POST /v2/matrix |
Yes |
| Turn a place name or address into coordinates | GET /v2/geocode |
Key or our website |
| Turn coordinates into the nearest place | GET /v2/reverse |
Key or our website |
| Snap a point to the nearest road | GET /v2/nearest |
Key or our website |
| Map the area reachable within a travel time | GET /v2/isochrone |
Yes |
| Check coverage, profiles and data date | GET /v2/info |
Key or our website |
Programs and scripts always send a key. "Our website" means the pages on quadruper.com itself, such as the test map.
Rules that apply to every call
- Base URL:
https://quadruper.com - Coordinates: always
[lng, lat], in query strings, request bodies and responses. - Units: metres and seconds. Field names say so:
distance_m,duration_s. - Authentication: send your key in the
X-API-Keyheader. - Errors: branch on
code, never onmessage. See Errors. - Attribution: show the
attributionlist wherever you show routes, places or maps to people.
API rules has the full list, with limits.