GET/v1/transit/stops

API key required, sent as Authorization: Bearer snk_… or ?api_key=snk_….

Call it

bash

curl -fsS -X GET "https://api.mapmap.ai/v1/transit/stops?lat=…&lon=…" \
  -H "Authorization: Bearer $MAPMAP_KEY"

Parameters

Name	In	Required	Description
lat	query	yes	Required. Latitude, WGS84 degrees
lon	query	yes	Required. Longitude, WGS84 degrees
radius_m	query	no	Search radius in metres, 1 to 2000 (default 500)
limit	query	no	Most stops to return, 1 to 50 (default 10), nearest first

Responses

200England bus and coach stops (NaPTAN) near the point, nearest first, each with its ATCO code, distance, bearing from the point and the lines the BODS timetable has calling there; coverage and the OGL v3.0 attribution on every answer. Bus only: rail, tram and ferry are not included

Field	Type	Required	Description
attribution	string	yes	NaPTAN and BODS attribution (both OGL v3.0), to be shown with the data.
coverage	string	yes	What this covers and what it does not.
stops	TransitStop[]	yes	Nearest first.

400lat or lon missing or out of range, or a malformed radius_m or limit. Not billed

401Missing or invalid API key

429Quota or rate limit exceeded

501Transit stops not enabled (SN_TRANSIT_DIR unset, or no departures index built yet). Not billed

Error bodies follow the shared problem model documented on API conventions.

Also under transit

GET /v1/transit/departures GET /v1/transit/vehicles

Generated from https://api.mapmap.ai/openapi.json on 2026-10-12 · operationId get_transit_stops