Resolve specific Idealista location IDs instantly.
Submit a region or district ID to get structured geographic metadata. No more manual coordinate mapping or regional hierarchy maintenance.
How it works
One request, one response.
- 1
Send location ID
Provide a specific identifier and the target country code in a POST request.
- 2
Resolve geographic data
The API fetches current regional metadata and hierarchy information for that specific identifier.
- 3
Parse JSON response
Receive structured details about the location for use in search filters or database mapping.
Capabilities
What you get.
Everything this endpoint does, without running the infrastructure yourself.
Multi-country support
Access location data for Spain, Italy, and Portugal using standardized country codes.
Property type filtering
Target specific real estate categories like homes, offices, or land within a location context.
Operation specific routing
Retrieve metadata tailored for either the rental or sale market segments.
Stable identifiers
Resolve internal IDs into human-readable geographic hierarchies for frontend display.
Cost of ownership
Build it yourself, or call this.
Both are real options. Here is what each one actually costs you.
Run it yourself
- Reverse-engineer internal ID systems
- Maintain local geographic mapping tables
- Handle frequent changes in regional hierarchies
- High developer maintenance cost
Call the API
- Instant resolution via locationId
- No database of European regions required
- Pay only for successful metadata lookups
- Integrated with search endpoints
Integrate
Built for the language you use.
One HTTP endpoint. Copy the call in your language and go.
curl -X POST https://automatio.ai/api/v1/query \
-H "Authorization: Bearer $AUTOMATIO_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "tool": "idealista_locations", "params": { "locationId": "example", "location": "example" } }'In production
What people build with it.
Pre-search Validation
Validate a user's location selection before triggering a wider search query. By resolving the locationId first, you ensure the coordinates and regional bounds are correct, reducing empty search results and improving user experience.
Market Analysis Dashboards
Map proprietary location IDs to a geographic hierarchy for regional price reporting. This allows you to aggregate data by province or municipality without building your own mapping engine or geographic information system.
Dynamic Filter Building
Use resolved location data to populate frontend filters in real estate applications. When a user selects a region, this endpoint provides the necessary context to show relevant property types and operations available in that specific zone.
Choosing parameters
Which options matter.
The table below lists what exists. These are the calls worth making deliberately.
- location
- locationId
- propertyType
Alternatives
When to use something else.
A page that pretends it has no alternatives reads as an advert. These are the other real options.
Official API
Requires a formal partnership and often involves usage restrictions or high entry costs for smaller developers.
Manual Geo-mapping
Building a local database of postal codes and regions is free but requires constant manual updates to remain accurate.
Before you integrate
What it does not do.
The boundaries are as useful as the features. These are the ones worth knowing up front.
No Coordinate Search
This endpoint requires a specific locationId and cannot resolve data from raw latitude and longitude inputs.
Limited to Three Countries
Data is only available for Spain, Italy, and Portugal; other European or global markets are not supported by this tool.
No Listing Counts
The response provides geographic metadata but does not return the number of active properties currently available in that location.
Reference
135 credits per call- Endpoint
- POST https://automatio.ai/api/v1/query
- Tool ID
- idealista_locations
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| locationId | string | Parent locationId (divisible=true from suggestions) | |
| location | "es" | "pt" | "it" | Country code: Spain (es), Portugal (pt), Italy (it) | |
| propertyType | "homes" | "offices" | "premises" | "garages" | "bedrooms" | "newDevelopments" | "land" | — | Property type context (default: homes) |
| operation | "sale" | "rent" | — | Property operation type |
The same endpoints are available over MCP, and the full machine-readable catalogue lives in the API documentation.
Frequently Asked Questions
Find answers to common questions about Property Locations API
Same data source
Every Real estate endpoint.
One key, one endpoint shape. These all bill per successful call the same way.
Agency Listings API
Extract property listings for real estate agencies on Idealista. Get structured data for sales or rentals in Spain, Italy, and Portugal via JSON.
135 creditsReal Estate Agency API
Extract structured real estate agency data from Idealista using the microsite ID. Access contact details, portfolio size, and metadata for Spain, Italy, and...
135 creditsIdealista Property Search API
Search real estate listings across Spain, Italy, and Portugal. Filter by location, price, and features like pools or terraces to get structured property data.
135 creditsProperty Details API
Get structured Idealista property data for Spain, Italy, and Portugal. Access prices, features, and localized descriptions via a single POST request.
135 creditsLocation Autocomplete API
Access real-time location suggestions from Idealista for Spain, Italy, and Portugal. Convert partial text strings into valid geographic identifiers for search.
135 creditsOther endpoints
Browse all APIs →Supercharge your workflow with AI Automation
Automatio combines the power of AI agents, web automation, and smart integrations to help you accomplish more in less time.