Store your places, tag them with your own typed attributes and let Lanewise add a street address to every one. Then find what is within any radius of a point, filtered exactly the way your app needs.
The Free plan includes 50 requests per hour, 1,000 POIs and every API feature.
curl -G https://api.lanewise.app/v1/pois \
-H "X-API-KEY: $LANEWISE_KEY" \
-d latitude=41.3851 \
-d longitude=2.1734 \
-d distance=500 \
-d "attributes[open]=true"HTTP/1.1 200 OK
Content-Type: application/json
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 997
X-RateLimit-Reset: 1790600400Every response carries your hourly quota, so clients can back off before they hit a 429.
{
"data": [
{
"id": "01K5YQ3H8V2N6T4R9M7C1X0B5D",
"name": "Mercat de la Boqueria",
"latitude": 41.3817,
"longitude": 2.1716,
"distance": 406.8,
"category": {
"id": "01K5YQ1A7C2D3E4F5G6H7J8K9M",
"name": "Markets",
"created_at": "2026-09-18T08:02:11.000000Z",
"updated_at": "2026-09-18T08:02:11.000000Z"
},
"attributes": {
"open": true,
"rating": 4.6,
"owner_id": "client_1042"
},
"address": {
"display_name": "Mercat de la Boqueria, 91, La Rambla, el Gòtic, Ciutat Vella, Barcelona, Barcelonès, Barcelona, Catalunya, 08001, España",
"street": "La Rambla",
"city": {
"id": "9b2f6c1e-4a7d-4f0b-8c3e-2d5a6f7b8c9d",
"name": "Barcelona"
},
"country": {
"id": "3e8a1d2c-5b6f-4c7d-9e0f-1a2b3c4d5e6f",
"name": "España"
},
"zipcode": {
"id": "7c4d2e1f-8a9b-4c0d-a1e2-f3a4b5c6d7e8",
"code": "08001"
},
"geocoded_at": "2026-09-21T10:15:34.000000Z"
},
"created_at": "2026-09-21T10:15:32.000000Z",
"updated_at": "2026-09-24T17:40:05.000000Z"
},
{
"id": "01K5YQ4B2W8X1Z3P5N7Q9S0T2V",
"name": "Mercat de Santa Caterina",
"latitude": 41.3859,
"longitude": 2.1786,
"distance": 442.85,
"category": {
"id": "01K5YQ1A7C2D3E4F5G6H7J8K9M",
"name": "Markets",
"created_at": "2026-09-18T08:02:11.000000Z",
"updated_at": "2026-09-18T08:02:11.000000Z"
},
"attributes": {
"open": true,
"rating": 4.4,
"owner_id": "client_1042"
},
"address": {
"display_name": "Mercat de Santa Caterina, Avinguda de Francesc Cambó, Sant Pere, Santa Caterina i la Ribera, Ciutat Vella, Barcelona, Barcelonès, Barcelona, Catalunya, 08003, España",
"street": "Avinguda de Francesc Cambó",
"city": {
"id": "9b2f6c1e-4a7d-4f0b-8c3e-2d5a6f7b8c9d",
"name": "Barcelona"
},
"country": {
"id": "3e8a1d2c-5b6f-4c7d-9e0f-1a2b3c4d5e6f",
"name": "España"
},
"zipcode": {
"id": "2a6b8c0d-1e3f-4a5b-9c7d-8e9f0a1b2c3d",
"code": "08003"
},
"geocoded_at": "2026-09-21T10:16:02.000000Z"
},
"created_at": "2026-09-21T10:15:58.000000Z",
"updated_at": "2026-09-21T10:16:02.000000Z"
}
],
"next": "01K5YQ5C9D1F3G5H7J9K1M3N5P"
}Features
One API for storing locations, describing them with your own data and finding the right ones fast. No GIS stack to run, no geocoder to wire up.
Ask for everything within N meters of a point. Lanewise runs a haversine search over your POIs and tells you how far away each result is.
Send coordinates, get an address. Every POI is reverse-geocoded in the background with OpenStreetMap Nominatim, and again whenever its coordinates change.
{
"name": "Mercat de la Boqueria",
"latitude": 41.3817,
"longitude": 2.1716
}{
"address": {
"display_name": "Mercat de la Boqueria, 91, La Rambla, el Gòtic, Ciutat Vella, Barcelona, …, 08001, España",
"street": "La Rambla",
"city": {
"id": "9b2f6c1e-4a7d-4f0b-8c3e-2d5a6f7b8c9d",
"name": "Barcelona"
},
"country": {
"id": "3e8a1d2c-5b6f-4c7d-9e0f-1a2b3c4d5e6f",
"name": "España"
},
"zipcode": {
"id": "7c4d2e1f-8a9b-4c0d-a1e2-f3a4b5c6d7e8",
"code": "08001"
},
"geocoded_at": "2026-09-21T10:15:34.000000Z"
}
}How it works
Three steps, all over HTTPS. Use any language or HTTP client you already have.
Sign up, create a team and generate a key in the dashboard. Choose exactly which resources it can touch and when it expires.
export LANEWISE_KEY="your-api-key"Define the attributes you care about once, then send your places. Categories and attribute values ride along in the same request.
curl https://api.lanewise.app/v1/attributes \
-H "X-API-KEY: $LANEWISE_KEY" \
-H "Content-Type: application/json" \
-d '{ "name": "open", "type": "boolean" }'
curl https://api.lanewise.app/v1/pois \
-H "X-API-KEY: $LANEWISE_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Mercat de la Boqueria",
"latitude": 41.3817,
"longitude": 2.1716,
"category_id": "01K5YQ1A7C2D3E4F5G6H7J8K9M",
"attributes": { "open": true }
}'Search around a point, by category, by attribute or by location, and page through the results with a cursor.
curl -G https://api.lanewise.app/v1/pois \
-H "X-API-KEY: $LANEWISE_KEY" \
-d latitude=41.3851 -d longitude=2.1734 \
-d distance=500 \
-d category_name=MarketsBuilt for teams
Lanewise is multi-tenant from the ground up. Your team's POIs, attributes and categories are isolated from everyone else's, and the dashboard gives you control over who and what can reach them.
API keys
IllustrationProduction backend
ActiveExpires in 11 months
Driver app (read only)
ActiveNo expiry
Old import script
InactiveDeactivated
Use cases
If your product answers “what is near here?”, Lanewise can hold the answer. A few of the ways teams put it to work:
Keep depots, hubs, lockers and drop-off points in one place and find the closest ones to a driver or an order. Cluster the stops and optimize each vehicle’s deliveries.
GET /v1/pois?category_name=Depots&distance=5000
Warn drivers about the hazards or restricted zones you store, or plan routes that keep away from road works and closed streets.
GET /v1/pois?category_name=Hazards&distance=2000
Power a "near me" page with stores, venues or partners, showing only the ones that are open right now.
GET /v1/pois?attributes[open]=true
Track job sites, assets and inspection points by city or zipcode, and let the whole team work from the same data.
GET /v1/pois?city_id=…&attributes[status]=pending
Store locations for many clients in one team and keep them apart with an owner or client attribute.
GET /v1/pois?attributes[owner_id]=client_1042
Roadmap
Bulk CSV import and routing are live. The rest is in the works and not available yet. Want one of them first? Tell us at [email protected].
Load up to 50,000 POIs per file, attributes included, in one upload.
Put your POIs to work between A and B.
Ready-made datasets you can switch on next to your own POIs.
Typed clients so you can skip the HTTP plumbing.
Pricing
Choose how many requests per hour and how many POIs your team needs. Each is priced on its own, and the first 50 requests per hour and 1,000 POIs are free.
Requests are counted per team and reset at the top of every hour (UTC), with at most a thirtieth of them in any minute (never fewer than 20). Routing calls that avoid POIs or optimize deliveries also use a daily allowance that resets at midnight UTC. The POI limit is the most your team can store at once.
Pro plan
€44/ month excl. VAT for 1,000 requests/hour, 50,000 POIs
Create your account, then confirm this plan and pay securely through Link, powered by Stripe. Prices exclude VAT, added at checkout where it applies. Billed monthly, cancel anytime.
Quotas and limits apply to your whole team, and you can change plan from the dashboard at any time. Requests over the hourly quota or the per-minute burst cap get a 429, and imports stop once the POI limit is reached. Each requests tier includes a daily allowance of routing calls. Teams have up to 2 members on Free and 10 on any paid plan, pending invitations included. Each account can have one team on Free. Paid plans also get conditional requests: data that hasn't changed comes back as an empty 304 that costs a tenth of a request. POI tiers above 250,000 are set up by agreement.
429 because a limit is reached do not count.429 JSON error and a Retry-After header until the quota resets at the top of the next hour (UTC). Each team can also send at most a thirtieth of its hourly quota in any minute, never fewer than 20; over that, the 429 tells you how many seconds to wait. The X-RateLimit-* headers on every response let you see it coming.name, latitude, longitude, an optional category and one column per attribute, from the dashboard or with POST /v1/imports. It is processed in the background, and every new POI is geocoded.POST /v1/routes plans a route that keeps away from the POIs you select, /v1/routes/clusters groups stops into compact areas, and /v1/routes/optimize assigns stops to vehicles around time windows and capacities. The API key needs the plan-routes permission. Avoiding POIs and optimizing deliveries use a daily allowance of routing calls set by your requests tier, from 20 on Free to 1,000 on the largest tier; clustering is free. See the routing guides.geocoded_at tells you when it last ran.attributes[name]=value, using either the attribute name or its ID.latitude, longitude and a distance in meters; if you leave the distance out it defaults to 1,000 m. Each result includes its distance from the point.limit (15 by default) and pass the next value from the response as cursor to get the following page.Create a free account, generate a key and run your first nearby search today.