Location figures for any point in Spain
For proptech and site-selection vendors with sites found outside the search. Send any lat and lon in Spain to explain_location and get the footfall index, residents by age, households, spending power and nearby places with vintages.
What is the problem?
Landlords, brokers and your own users bring sites found elsewhere, not in a Claro search, and want the same location figures a premises from the search carries.
How does it work?
- Call
explain_location(tool) orPOST /v1/claro/location(operation) withlatandlonfor any point in Spain. For a premises from a search, send itsidinstead. - Read the footfall index within a 5-minute walk (an index of pedestrian activity that compares places with each other, not a head count: weekday and weekend averages, morning, lunch, afternoon and evening, local, commuter and tourist shares), residents within a 10-minute walk and drive, residents by age band (0-14, 15-29, 30-44, 45-59, 60+), households, households per net income quintile, total spending power within a 10-minute walk, and nearby restaurants, fast food, cafes, shops, supermarkets, gyms and transit stops.
- Keep
location_sourceswith each figure: unit, source, vintage and when it was computed. On 15 October 2026: Footfall estimates 2024 and MB Research sociodemographics 2024 from Targomo; places release 2026-09-23.1 from OpenStreetMap and Overture Maps places. - Cache the answer per point on your side: a point that is not a premises is a live call on the account's location data.
curl https://platform.casafari.com/v1/claro/location \
-H "Authorization: Bearer $CASAFARI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"lat": 40.4155, "lon": -3.7074}'What do you get?
The same figures a premises carries, each with its unit, source and vintage. A figure that is unknown is null, never 0; a count of places can be 0.
What are the limits?
Location data access on the account is required. A point that is not a premises counts against live_location_points_daily (about 31 location-data operations per point); when it is used up the answer is 429 with code quota_reached and a message naming live_location_points_daily, which lasts until the reset (429 codes). Points must be in Spain.