OneMap Routing

OneMap uses a token, not a static API key. Register an account on OneMap, then POST your email and password:

curl -X POST 'https://www.onemap.gov.sg/api/auth/post/getToken' \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com","password":"YOUR_PASSWORD"}'

{"access_token":"***","expiry_timestamp":"1689388144"}

Each token is valid for 3 days. It does not auto renew. Call getToken again when it expires. Errors: 401 authentication failed, 404 user not registered.

Send the token in the Authorization header. Example from the official docs:

curl -H 'Authorization: YOUR_TOKEN' \
  'https://www.onemap.gov.sg/api/public/routingsvc/route?start=1.3081592%2C103.8551479&end=1.2739864%2C103.8012642&routeType=pt&date=11-10-2025&time=11%3A19%3A47&mode=TRANSIT&maxWalkDistance=1000&numItineraries=3'

• start, end: lat,lng. Required.
• routeType: walk, drive, cycle or pt. Required.
• For pt only: date (MM-DD-YYYY), time (HH:MM:SS, 24 hour), mode (transit, bus or rail). Optional: maxWalkDistance, numItineraries (1 to 3).

Walk, drive and cycle responses include status_message, an encoded route_geometry, route_instructions and route_summary with total_time (seconds) and total_distance (metres). Public transport responses return itineraries with legs such as WALK and SUBWAY.

We called the routing endpoint without a token on 2026-09-25 and got {"message":"Unauthorized"}. Documented errors:

• 401 Unauthorized: missing or expired token.
• 400: missing start or end, bad routeType, missing pt mode, bad date or time format, date more than 1 year past or 1 month ahead, coordinates outside Singapore, numItineraries outside 1 to 3.
• 404: no route found between the locations.

The Search API now also needs a token. Our untokened search call still returned results with an error field reading "Authentication token missing".