Crexi API · unofficial, by Cotlet
Create your own Crexi API
Crexi's Listing API is a one-way listings feed for qualifying partners under an agreement (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Crexi account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Crexi session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Crexi. Crexi is a trademark of its owner. If Crexi's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/new-leads" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"days": 7}' const url = "https://cotlet.dev/api/v1/custom/new-leads";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ days: 7 }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/new-leads",
headers={"Authorization": f"Bearer {key}"},
json={"days": 7},
)
data = res.json()["data"] {
"data": [
{
"lead": "Dana R.",
"company": "Northwind Capital",
"listing": "120 Main St",
"action": "Downloaded OM",
"date": "2026-11-17"
},
{
"lead": "Tom H.",
"company": "broker",
"listing": "120 Main St",
"action": "Viewed listing",
"date": "2026-11-18"
}
]
} 01 Build
How do you build a Crexi endpoint with Cotlet?
-
Sign in to Crexi in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "List the new leads on my listings from the last 7 days, with the listing, company and what they did."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a number of days or a listing, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Crexi session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Crexi
Cotlet ships no fixed list of Crexi endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/new-leads New leads
Leads on your listings in the days you name, with what they did
-
POST
/api/v1/custom/leads-by-listing Leads by listing
Lead count per listing for a period
-
POST
/api/v1/custom/my-listings My listings
Your listings with status and asking price
-
POST
/api/v1/custom/saved-search-matches Saved search matches
New properties that match a saved search
-
POST
/api/v1/custom/writesmessage-lead Message a lead
A message sent to the lead you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/new-leads" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"days": 7}' The answer is JSON, with your fields under data:
{
"data": [
{
"lead": "Dana R.",
"company": "Northwind Capital",
"listing": "120 Main St",
"action": "Downloaded OM",
"date": "2026-11-17"
},
{
"lead": "Tom H.",
"company": "broker",
"listing": "120 Main St",
"action": "Viewed listing",
"date": "2026-11-18"
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Crexi endpoints for?
- Schedule Cotlet endpoint Your CRM
Leads into your CRM.
New Crexi leads added to the CRM or sheet you already use.
- Schedule endpoint Google Sheets
A seller report.
Leads per listing pulled into Google Sheets for the weekly owner update.
- Schedule endpoint Slack
Deal alerts in your team chat.
New matches for a saved search posted to Slack each morning.
- Chat agent endpoint lead activity
Your own AI assistant.
A chat agent that reads a lead's activity before it drafts a follow-up.
04 Access
What can an endpoint see and change?
An endpoint works in your own Crexi session, so it can read and change only what your Crexi login can. An owner login sees the whole business. A team login sees what its permissions allow. You choose what each endpoint does when you build it.
An endpoint that changes something, such as messaging a lead, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Crexi have an official API?
Crexi has a Listing API, a one-way feed that pushes listings onto Crexi for MLS groups, large brokerages and data providers after a review and an agreement; it does not read a broker's leads (checked 20 Nov 2026). The full picture with sources: Does Crexi have an API or MCP server?
Want ChatGPT or Claude to work in Crexi instead of code? See the Crexi MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Crexi API with Cotlet: questions
Is this an official Crexi API?
No. Cotlet is independent and not affiliated with Crexi. The endpoints you build run in your own signed-in Crexi account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Crexi changes its screens?
An endpoint works while Crexi works the way it did when you built it. If Crexi changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Crexi endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.