Get location figures for any point in Spain
For developers at proptech and site-selection vendors. Send lat and lon to POST /v1/claro/location for footfall, residents and nearby places at any point in Spain, within the live-location daily limit.
What is the problem?
Landlords, brokers and your own users bring addresses that are not on the market, and want the same footfall index, residents and nearby places that a premises found by a search gets.
How does it work, step by step?
- Hold the point's coordinates yourself; Claro takes
latandlonanywhere in Spain. - Call explain_location over MCP or
POST /v1/claro/location(REST) withlatandlon. For a premises a search returned, send itsidinstead. - Read the figures with
location_sources: each carries its unit, source and vintage (on 15 October 2026: footfall estimates 2024, sociodemographics 2024, places release 2026-09-23.1) and when it was computed. - Cache the answer per point: a point that is not a premises is a live call on the account's location data, about 31 location-data operations per point, and counts against
live_location_points_daily.
curl -X POST 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 footfall index within a 5-minute walk (an index of pedestrian activity that compares places with each other, not a head count), split into weekday and weekend averages, morning, lunch, afternoon and evening, and local, commuter and tourist shares; residents within a 10-minute walk and drive, by age band (0-14, 15-29, 30-44, 45-59, 60+), households, households per net income quintile and total spending power within a 10-minute walk; and nearby restaurants, fast food, cafes, shops, supermarkets, gyms and transit stops. A footfall or population figure with no data is null, never 0; a place count can be 0.
What are the limits?
The account needs location data access. The daily point limit is set on the organisation's Claro account behind the platform: when it is used up, a 429 with the code quota_reached names live_location_points_daily in its message and lasts until it resets, so stop rather than retry. A 429 rate_limited is the per-minute limit: wait and retry (429 handling). The platform's own limits answer first (limits). Label the footfall figure as an index, never people or visitors a day.