Client
ModelsExpand Collapse
Error { error } Standard API error envelope. Every error response wraps a single error object with a machine-readable code, a human-readable message, and optional structured details.
Standard API error envelope. Every error response wraps a single error object with a machine-readable code, a human-readable message, and optional structured details.
FeatureCollection { features, type } GeoJSON FeatureCollection (RFC 7946). For paginated endpoints, metadata is returned in HTTP response headers rather than the body:
Header
Description
X-LimitRequested result limit
X-Has-Moretrue if more results exist
X-Next-CursorOpaque cursor for next page (cursor pagination)
X-Next-OffsetNumeric offset for next page (offset pagination)
LinkRFC 8288 rel="next" link to the next page
Content-Type is application/geo+json.
GeoJSON FeatureCollection (RFC 7946). For paginated endpoints, metadata is returned in HTTP response headers rather than the body:
| Header | Description |
|---|---|
X-Limit |
Requested result limit |
X-Has-More |
true if more results exist |
X-Next-Cursor |
Opaque cursor for next page (cursor pagination) |
X-Next-Offset |
Numeric offset for next page (offset pagination) |
Link |
RFC 8288 rel="next" link to the next page |
Content-Type is application/geo+json.
Array of GeoJSON Feature objects
Array of GeoJSON Feature objects
GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.
GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.
GeoJsonFeature { geometry, properties, type, id } GeoJSON Feature representing an OSM element. Tags from the original OSM element are flattened directly into properties (not nested under a tags key). Metadata fields @type and @id identify the OSM element type and ID within properties.
GeoJSON Feature representing an OSM element. Tags from the original OSM element are flattened directly into properties (not nested under a tags key). Metadata fields @type and @id identify the OSM element type and ID within properties.
GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.
GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.
GeoJsonGeometry { coordinates, type } GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.
GeoJSON Geometry object per RFC 7946. Coordinates use [longitude, latitude] order. 3D coordinates [lng, lat, elevation] are used for elevation endpoints.