A real estate CRM API for your code and your AI.
Connect Claude, ChatGPT or any MCP client and do your Uplevel work from there, with your own permissions. Or build on the REST API, signed webhooks and Setup Packs.
Four ways in, each with its own limits.
An AI client acts as you, with your role. An API key acts for one workspace, within the scopes you give it. Neither reaches a workspace it wasn’t given.
Everything Uplevel does, from your own AI.
Add Uplevel to Claude, ChatGPT or Codex with one address. Your AI client opens Uplevel in the browser, you sign in and choose what it may do, and it’s connected. There’s no key to copy.
More than 890 tools come straight from the services the dashboard itself calls, so new features reach your AI client the day they ship. The few kept in the app are listed below.
# Claude: Settings → Connectors → Add custom connector
https://api.uplevelre.com/mcp
# Codex
codex mcp add uplevel --url https://api.uplevelre.com/mcp- Read only to start
- A connection can only read unless the AI client asks for more and you approve it. Either way, it acts with your own role and permissions.
- The workspaces you pick
- Choose all your workspaces or only some. A workspace you leave out answers as if it doesn’t exist.
- Approval for what matters
- Sending email, texts and broadcasts, placing calls, publishing, buying a domain or number, deleting contacts in bulk, billing changes and changes to who has access each wait for you.
- Safe retries
- A change sent twice with the same key runs once, so an AI client that retries after a timeout doesn’t make duplicates.
- Every call logged
- Uplevel records each call’s tool, workspace, outcome and time, and never the details you passed. Connections last 90 days, and you can revoke one at any time.
- Kept out of reach
- An AI client can’t create API keys or webhooks, connect outside accounts, sign in for you or approve its own requests. Those stay in the app.
Three jobs, call by call.
What happens when someone hands Uplevel a real job from outside the app: each call or step, what Uplevel does with it, and where you can see it afterward.
“Merge our duplicate contacts and delete the test ones.”
An agent asks Claude, which is connected to Uplevel with read and write. Claude reads and merges on its own, and the delete waits for her.
Open squares hold the job until someone answers.
Call list_workspaces
Claude finds the workspaces this connection is allowed to use.
The workspaces picked when connecting
Call contact_list_contacts
It reads the contacts she can see. Text from emails and forms comes back marked as data, not instructions.
Her own visibility and role
Call contact_merge_contacts
Each set of duplicates becomes one contact, and their history moves to the one kept.
Write access, approved when connecting
Call contact_delete_contacts (waits for an answer)
Deleting in bulk doesn’t run. Uplevel holds it and gives Claude an approval link to share.
Waiting for your approval, in Settings
Approve in Uplevel
She sees the action, the workspace and every detail of the request, then approves. It waits 15 minutes.
Integrations, Connected AI clients
Call contact_delete_contacts
Claude repeats the call with the approval, and exactly that call runs, once.
The connection’s call log
A REST API for the records you work every day.
Create an API key in Settings and call Uplevel from your own code, a spreadsheet script or a back-office system. Requests and responses are JSON, and the full OpenAPI document is published.
A key acts for the workspace within the scopes you give it, including contacts a teammate keeps private, and never sees another workspace.
curl https://api.uplevelre.com/v1/deals?limit=10 \
-H "Authorization: Bearer ul_live_…"- Contacts
- List, create, read, update and delete, add and remove tags, read activity, add notes.
- Deals
- List, create, read, update and delete.
- Tasks
- List, create, read, update and delete.
- Transactions
- List, create, read, update and delete, with the closing checklist, parties and commission.
- Listings
- Read all your listings, and create, update and delete the ones you added by hand.
- Webhooks
- Add, change, verify and delete endpoints, and read each one’s deliveries.
- Workspace
- Pipelines, contact stages, lead sources, tags, members, and the key itself.
- Scopes
- Give a key read or write for each resource, or full access. Write includes read. A key can expire on a date you set.
- Rate limit
- 120 requests a minute per workspace by default, across all its keys. Every response says how many are left.
- Usage
- Each key shows when it was last used and how many requests it has made. Revoke it and it stops at once.
Connect your AI client free during Early Access.
We’re working closely with a small group of agents, teams and brokerages before the wider launch. The MCP server, the API, webhooks and Setup Packs are part of the one plan.
Get early access- Price
- Free for as long as the program runs
- Card
- None, to apply or to use it
- Included
- 2 phone numbers, 1 domain, 1,000 texts and 500 call minutes a month
- Afterward
- 50% off your first paid year
Webhooks your server can check.
Tell Uplevel where to send events and it posts each one as it happens: a new contact, a deal changing stage, a task done, a sale closing. Each endpoint picks its own events, or all of them.
Every event carries the record as the API returns it, so a closed transaction arrives with its price and commission.
POST https://books.example.com/hooks/uplevel
X-Uplevel-Event: transaction.closed
X-Uplevel-Delivery-Id: …
X-Uplevel-Signature: t=1760889600,v1=5257a869e7…- HTTPS only
- Endpoints must use https://. Uplevel won’t deliver to a private address, and it doesn’t follow redirects.
- A secret per endpoint
- Uplevel generates each endpoint’s signing secret and shows it once. Rotate it in Settings whenever you need to.
- Verified before anything sends
- A new endpoint gets nothing until it answers a signed challenge. Change its address and it has to answer again.
- Signed deliveries
- Every delivery carries a timestamp and an HMAC-SHA256 signature of its body, so your server can tell it came from Uplevel.
- Retries and history
- Each delivery gets five attempts. Its status, response code and attempts show in the endpoint’s history, and 20 failures in a row pause the endpoint.
- Automation webhooks too
- The Send webhook step in an automation signs the same way, and only posts to addresses you’ve verified in the step.
Events you can subscribe to:
- contact.created
- contact.updated
- contact.deleted
- deal.created
- deal.updated
- deal.stage_changed
- deal.deleted
- task.created
- task.updated
- task.completed
- task.deleted
- transaction.created
- transaction.updated
- transaction.status_changed
- transaction.closed
- transaction.fell_through
- listing.created
- listing.updated
- listing.deleted
A workspace’s setup, in one file.
A Setup Pack is one JSON file with the automations, smart lists, message templates, pipelines and brand that make a workspace work, plus the tags, stages and fields they use. Export one from your workspace, or write one by hand.
Import it into another workspace and everything arrives together, with a version, so the next one upgrades it.
A Setup Pack can carry:
- Automations
- Smart lists
- Message templates
- Deal pipelines
- Brand
- Tags, stages and lead sources
- Custom fields
- Email templates
- Check before you install
- Check a pack shows what it would add, what clashes with what’s already there, and where in the file each problem is. Nothing changes.
- You decide each clash
- Use what the workspace already has, add a copy, or skip it. Automations always arrive turned off, so nothing sends until someone turns them on.
- Upgrades in place
- A newer version of the same pack updates what the last one installed. Items edited in the workspace are never replaced without a choice.
- A public format
- The JSON Schema is published at a stable address, so an editor checks a pack as you write it.
For coaches and consultants: a partner seat.
Build your playbook once as a Setup Pack, then support each client from a seat in their workspace.
- An unbilled seat
- A client invites you to a partner seat for setup work. It doesn’t add to their bill, and billing stays with them.
- Reach they choose
- Contacts, deals and automations, or also settings, email, integrations and branding. They can change it later.
- Every client on one page
- Partners lists every workspace you support, quietest first, beside your own. Push a new version of your pack to a client and the items they edited keep their version.
- A record they can read
- Every change made from a partner seat is recorded under Partner activity in Team.
Questions about the API and MCP.
Something we didn’t cover? Write to hello@uplevelre.com.
Which AI clients work with Uplevel?
Claude and ChatGPT, Codex, and any remote MCP client that signs in with OAuth. In Claude, add a custom connector with the address https://api.uplevelre.com/mcp and sign in when it opens Uplevel.
Can an AI client delete my data?
Only if you gave the connection write access, and only what your role allows. Deleting contacts in bulk, sending, publishing, spending and changing who has access each wait for you to approve the exact request in Uplevel.
Is there a Zapier integration?
Not today. Webhooks tell your systems when something changes, and the REST API reads and writes the records, so a developer can connect most tools directly.
What does an API key see?
A key acts for the whole workspace within its scopes, including contacts a teammate keeps private. It never sees another workspace. Give keys only to systems you trust with the workspace’s data.
Do the API and the MCP server cost extra?
No. They’re part of the one Uplevel plan, with no developer tier.
Where’s the full reference?
The API reference lists every endpoint and event with examples, the MCP guide covers connecting each client, and the Setup Pack guide documents the file format.
Your workspace, from wherever you work.
Apply for early access and connect your AI client today.
https://api.uplevelre.com/mcp