Integrations
Not every integration needs to be written against the HTTP API. If you are wiring property data into a CRM, an AI agent, or a no-code app, one of these will get you there faster.
MCP server
RealEstateAPI publishes a Model Context Protocol server, which lets an AI agent explore the API reference and documentation directly rather than being told about it second-hand.
Streamable HTTP endpoint
{
"url": "https://developer.realestateapi.com/mcp",
"type": "streamable-http"
}
See MCP for RealEstateAPI for client setup.
Zapier
The Zapier integration exposes Property Detail and SkipTrace as Zap actions, which is enough to enrich records in most CRMs without any code. There are step-by-step guides for the common destinations:
| CRM | Property Detail | SkipTrace |
|---|---|---|
| HubSpot | Guide | Guide |
| Podio | Guide | Guide |
| Salesforce | Guide | — |
| Airtable | Guide | — |
| Zoho | Guide | — |
Both actions can run in one Zap if you need contact data attached to a property record — see the combined guide.
Salesforce Lightning
A native Salesforce integration brings tax, mortgage, phone, email, and demographic fields into your Salesforce objects, so lead records carry property context without a round trip through middleware. See the Salesforce integration guide.
Bubble
For no-code apps, the Bubble integration wires the API into Bubble's data layer.
These integrations still authenticate with your API key and still spend your credits. The rate limits apply exactly as they do to direct HTTP calls.
Building it yourself
If none of the above fits, the API is plain JSON over HTTPS with a single auth header — see Authentication and the Quickstart. There are no official client libraries to install; any HTTP client will do.