Build real estate search autocomplete.
Convert partial text strings into valid Idealista location IDs. Support Spain, Italy, and Portugal with property type and operation filters.
How it works
One request, one response.
- 1
Submit search prefix
Send a JSON payload containing your partial string and the target country code to the query endpoint.
- 2
Identify geographic matches
The system queries the platform to find matching towns, neighborhoods, and districts.
- 3
Receive location IDs
Get back a structured list of names and internal identifiers ready for use in search filters.
Capabilities
What you get.
Everything this endpoint does, without running the infrastructure yourself.
Cross-country support
Query locations across Spain, Italy, and Portugal using a single interface.
Contextual filtering
Refine suggestions by property type to ensure matches have relevant inventory.
Operation awareness
Filter results based on whether the search intent is for buying or renting.
Structured identifiers
Returns unique internal keys that map directly to the requirements of search endpoints.
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 platform suggestion logic
- Handle complex session header rotations
- Manually map identifiers to changing geographic schemas
- High infrastructure maintenance
Call the API
- Single POST endpoint for all three countries
- Consistent JSON structure for every response
- Zero proxy management required
- Billed only for successful calls
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_suggestions", "params": { "prefix": "example", "location": "example" } }'In production
What people build with it.
Property Search Portals
Input a prefix like 'Barc' and receive 'Barcelona' with its specific internal ID. This allows users to select exact locations from a dropdown before triggering a high-volume search query.
CRM Data Normalization
Take partial address strings from inbound leads and normalize them against official platform locations. This ensures that internal lead records match the data structure used for automated market alerts.
Investment Analysis Tools
Allow users to quickly navigate between specific neighborhoods in Lisbon or Milan. The API returns the precise district IDs needed to fetch historical pricing data or inventory counts.
Choosing parameters
Which options matter.
The table below lists what exists. These are the calls worth making deliberately.
- prefix
- location
- 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.
Google Places API
Excellent for raw address strings but the resulting Place IDs will not map to Idealista's internal search filters.
Manual Location Mapping
Cost-effective for static lists of major cities but fails to account for new developments or neighborhood boundary changes.
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 data
The API returns location names and internal identifiers but does not include latitude, longitude, or polygon data.
Strict country boundaries
You cannot search across all three countries in a single request; the location parameter is required and strictly exclusive.
Suggestion depth
Very specific street addresses may not return results if they do not match the platform's primary geographic hierarchy for that region.
Reference
135 credits per call- Endpoint
- POST https://automatio.ai/api/v1/query
- Tool ID
- idealista_suggestions
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| prefix | string | Location name to search (e.g. "madrid", "barcelona", "lisbon") | |
| 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" | — | Operation context (default: sale) |
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 Location Autocomplete API
Same data source
Every Real estate endpoint.
One key, one endpoint shape. These all bill per successful call the same way.
Property Locations API
Retrieve structured geographic metadata for Idealista location IDs across Spain, Italy, and Portugal. Get accurate regional data for real estate integrations.
135 creditsAgency 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 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.