Ratifyly API and MCP
Build on the same tools Ezra uses.
The Ratifyly API gives you and the software you choose the same tools Ezra uses: your deals, dates, documents and timeline, the actions Ezra can take, and a webhook when a deal is built, a document is filed or a milestone moves. Through Ratifyly's MCP server, the AI assistant you already use can connect and work with your deals too. Every request follows the same rules as Ezra: you see only what your seat can see, and anything that counts waits for your approval in Ratifyly.
Integrations
Keys for the Ratifyly API; Zapier connects with one. A key reaches this workspace and no other. Treat a key like a password: it's shown once at creation, and you can revoke it here any time.
- Zapier
rat_7Qx2…Last used 3 minutes ago - Team dashboard
rat_k9Pe…Last used 1 day ago
The category
Why build on Ratifyly
Most real estate software keeps its data behind its own screens, so connecting it means exports, retyping and a spreadsheet someone rebuilds every Monday.
Ratifyly is built the other way: every action a person can take has a tool behind it, which is how Ezra does the work for you, and the API opens those same tools to the software you choose. See every connector on the integrations page, or meet Ezra.
The API
Your deals, in the software you choose
Create a key in Settings. It is shown once, it reaches your workspace and no other, and you can revoke it any time. Pull deals and their key dates into your own reports and dashboards, create a deal from the system you already run, and do anything Ezra can do, under the same approvals. Connect Ratifyly to thousands of apps through Zapier with the same key.
- Deals, parties, status and key dates, searchable
- Create deals from the systems you run
- The same actions Ezra takes, under the same approvals
- Zapier with one key
- Revoke a key in one click
Request
GET /api/v1/transactions?status=under_contract Authorization: Bearer rat_7Qx2…
Response
200 OK
{
"data": [
{
"id": "txn_8f3k2m",
"propertyAddress": { "street": "26 Birch Hollow Lane" },
"status": "under_contract",
"keyDates": { "closingDate": "2026-10-16" }
},
{
"id": "txn_2p7d9q",
"propertyAddress": { "street": "9 Kestrel Court" },
"status": "under_contract",
"keyDates": { "closingDate": "2026-10-30" }
}
]
}Webhooks
Know the moment a deal moves
Subscribe a webhook and your system hears the moment a deal is created, changes or closes, a document is filed or a milestone moves. Webhooks pause when a workspace's access is paused, so nothing keeps firing into a system that should not hear it.
- Created, changed and closed, as they happen
- Documents and milestones as they land
- Paused with the workspace, never left firing
Webhook, the moment the deal moved
POST https://your-system.example/hooks/ratifyly
{
"id": "evt_…",
"event": "transaction.updated",
"createdAt": "2026-09-08T18:42:07.000Z",
"data": {
"id": "txn_8f3k2m",
"propertyAddress": { "street": "26 Birch Hollow Lane" },
"status": "under_contract",
"keyDates": {
"contractDate": "2026-09-08",
"inspectionDate": "2026-09-18",
"appraisalDate": "2026-09-29",
"financingDate": "2026-10-06",
"closingDate": "2026-10-16"
}
}
}MCP
Bring the AI assistant you already use.
Ratifyly runs an MCP server. MCP is the open standard AI assistants and AI agents use to connect to software. Connect yours and it works with your deals through the same tools Ezra uses: it sees only what your seat can see, anything that counts still waits for your yes in Ratifyly, and it works whenever your workspace's API access is on.
The same rules
Every request follows the rules Ezra does
- Your seat's view, nothing wider.
- A key or an assistant sees what your seat sees.
- Approvals.
- Anything that counts waits for a person in Ratifyly.
- The audit trail.
- Every call is recorded beside Ezra's own work.
Build on Ratifyly
Tell us what you want to connect, and we'll set up your access and walk you through the first call.