Realtor.ca

Realtor.ca API endpoints

Realtor.ca logo

Available Realtor.ca Endpoints

Explore 11 endpoints for accessing Realtor.ca real estate data. Each endpoint is designed for a specific use case and returns structured JSON.

GET/details/byaddress

/details/byaddress

Get **full Realtor.ca property details** by a Canadian address. The address is resolved to a `propertyId` internally via Realtor.ca's autocomplete, then disambiguated by `city` / `province` / `postalCode` when multiple matches come back. Returns the same rich detail shape as [/details/byid](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=detailsbyid): address, price, building, agent, photos, history. ##### Note: - This endpoint costs `2 credits/call` and is slightly slower than `/details/byid`. - If you already know the `propertyId` (from any `/search/*` response or a Realtor.ca listing URL), use [/details/byid](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=detailsbyid) — it is `1 credit/call` and ~2× faster.

address
View endpoint
GET/details/byid

/details/byid

Get **full property details** by Realtor.ca `propertyId` (numeric) or `mlsNumber`. The `propertyId` is the `id` field returned in any `/search/*` response. The `mlsNumber` (e.g. `W13108430`) is resolved to a `propertyId` server-side via autocomplete first. Either `propertyId` or `mlsNumber` is required — pass one or the other.

View endpoint
GET/details/byurl

/details/byurl

Get **full property details** from a Realtor.ca listing URL. Both English (`/real-estate/<id>/<slug>`) and French (`/immobilier/<id>/<slug>`) URL forms are supported. The `propertyId` is parsed out of the URL path and forwarded to `/details/byid`.

url
View endpoint
GET/autocomplete

/autocomplete

Realtor.ca **search-box autocomplete** (`/Autocomplete.svc/GetAutocompleteResults`). Autocomplete a free-text query (city, address, MLS#, postal code) against Realtor.ca's location/listing index. Returns up to 5 ranked suggestions with addresses, listing ids, and (where applicable) postal codes — ready to feed into a `/search/*` or `/details/*` call.

input
View endpoint
GET/search/bylocation

/search/bylocation

Search Realtor.ca listings by **free-text location** — city, neighborhood, region, or address. The location is resolved to a bounding box via `/Location.svc/SubAreaSearch`, and the listings inside that box are returned. Supports the **full filter set** below (status, price/beds/baths/sqft ranges, property type, ownership, sold-within-days, boolean amenity filters, keywords, sort, pagination). Returns paginated listings with `id`, address, photos, price, beds/baths/sqft, status, days on market, listing date, and the listing-advertiser block (use the `agentId` with [/agent/details](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=agentdetails)).

location
View endpoint
GET/search/byzip

/search/byzip

Search Realtor.ca listings near a **Canadian postal code**. Use the `zipCode` parameter for platform consistency — `postalCode` is also accepted as a silent alias. Six-character codes (`M5V 0J6`) and three-character forward sortation areas (`M5V`) both work. Supports the full filter set from [/search/bylocation](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=searchbylocation).

zipCode
View endpoint
GET/search/bycoordinates

/search/bycoordinates

Search Realtor.ca listings within a **circular radius** around a lat/lon point. The circle is approximated with an axis-aligned bounding box server-side. Accepts the same full filter set as [/search/bylocation](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=searchbylocation).

latitudelongitude
View endpoint
GET/search/bypolygon

/search/bypolygon

Search Realtor.ca listings inside an **arbitrary polygon**. Accepts a `"lon lat,lon lat,..."` string or a GeoJSON `Polygon` JSON. The polygon's bounding box is used as the search envelope. Supports the full filter set from [/search/bylocation](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=searchbylocation).

polygon
View endpoint
GET/search/byurl

/search/byurl

Replicate a **Realtor.ca search URL**. Supports the `/map#ZoomLevel=...&LatitudeMax=...` form, `?Place=...`, `?PolygonString=...`, and slug-based location URLs. Filter params on the URL are parsed and replicated server-side.

url
View endpoint
GET/agent/search

/agent/search

Search **REALTORS®** on Realtor.ca by name or location (`/Individual.svc/IndividualSearch`). Returns paginated agent results with names, organizations, phones, websites, and photo URLs. Use the returned `agentId` with [/agent/details](https://realtyapi.io/dashboard?tab=playground&api=realtorca&endpoint=agentdetails) for the full bio + active listings.

query
View endpoint
GET/agent/details

/agent/details

Get **full details for one REALTOR®** by `agentId` (`/Individual.svc/IndividualDetails`). Returns bio, specialties, languages, areas served, organization, phones, websites, and the agent's currently active listings.

agentId
View endpoint

Why Choose RealtyAPI for Realtor.ca Data

We built RealtyAPI so developers can focus on their products, not on data collection infrastructure.

Real-Time Data Access

Get the most current Realtor.ca data without dealing with rate limits, IP blocks, or anti-bot protections. Our infrastructure handles the heavy lifting.

Simple Integration

Clear documentation and a straightforward REST API make it easy to start pulling Realtor.ca data into your application within minutes.

High Reliability

Our infrastructure is built for uptime and performance. Rely on consistent, uninterrupted access to Realtor.ca data for your production applications.

Comprehensive Data

Access a wide range of Realtor.ca data points through carefully designed endpoints that cover properties, listings, agents, and market metrics.

Lightning Fast Responses

Optimized data pipelines deliver Realtor.ca results in milliseconds. Low latency means a better experience for your end users.

Structured JSON Output

Every Realtor.ca endpoint returns clean, well-structured JSON that is ready to parse and use directly in your application logic.

Realtor.ca API Use Cases

From property valuation to market analysis, the Realtor.ca powers a wide range of real estate applications.

Property Valuation

Analyze Realtor.ca property data to determine accurate market values, estimate appreciation, and identify undervalued investment opportunities.

Market Research

Track Realtor.ca listing trends, pricing shifts, and inventory changes to make informed, data-driven investment and development decisions.

Portfolio Management

Monitor your real estate portfolio with live Realtor.ca data. Track current values, rental comps, and market conditions in one place.

Lead Generation

Identify high-potential properties and neighborhoods using Realtor.ca data to power targeted outreach and marketing campaigns.

Competitive Analysis

Compare listings, pricing, and agent activity across Realtor.ca to understand market positioning and stay ahead of competition.

Custom Dashboards

Build real-time dashboards that aggregate Realtor.ca data for internal teams, clients, or investors with always-current information.

Frequently Asked Questions

Common questions about using the Realtor.ca through RealtyAPI.

Is the Realtor.ca API official?
No, RealtyAPI provides an unofficial Realtor.ca data API that lets you access real estate data through our platform. We handle the complexities of data collection so you can focus on building your application.
How current is the data?
We provide real-time Realtor.ca data. When you make a request, we fetch the latest information available so your application always works with up-to-date figures.
Can I use this API in production?
Absolutely. Many businesses rely on RealtyAPI for their production applications. Our infrastructure is designed for reliability, low latency, and high throughput.
What response format does the API use?
All endpoints return structured JSON responses. The data is clean, well-documented, and ready to use directly in your application without additional parsing.
Do I need a credit card to get started?
No. You can start with 250 free API calls to test any endpoint. No credit card is required. Upgrade to a paid plan when you are ready to scale.
What programming languages are supported?
RealtyAPI is a standard REST API, so it works with any language that can make HTTP requests: Python, JavaScript, Go, PHP, Ruby, Java, C#, and more.

Ready to Access Realtor.ca Data?

Get started with 250 free API calls. No credit card required.

Common Terms for Realtor.ca API Access

Realtor.ca API integrationRealtor.ca data APIAccess Realtor.ca data programmaticallyRealtor.ca API for developersRealtor.ca API endpointRealtor.ca API documentationHow to use Realtor.ca APIRealtor.ca real estate APIRealtor.ca property data APIRealtor.ca listing API