Getting started
Orkasa
Connect an assistant, a backend or your automations to the same real-estate file.
Orkasa is the CRM where a brokerage's business lives: the clients, the properties, the viewings, the offers and the documents that close a sale. All of it hangs off a single object — the operation — and everything documented here is three ways to read it and move it from outside the app.
Paste one URL into Claude or ChatGPT, authorize, and ask about your files in your own words. Two minutes, no code.
Quickstart→Pick a door and make your first call.
What you can build
"How is the Felipe deal going?" · "What do I have today?" · "Book the Thursday 4pm viewing." The agent talks to the assistant they already use, and the CRM answers with the whole file.
An email lands in the agency inbox and a qualified lead comes out. An
operation reaches won and billing fires. All in Zaps, over this API.
Publish your portfolio under your own brand. Properties come from Orkasa, and the contact form returns a lead with its operation already open.
Import an existing book, sync with accounting, or write your own dashboard. REST over HTTPS, with webhooks so you never have to poll.
Three ways to connect
All three talk to the same backend, see the same data, and share the same authentication, the same permissions and the same rate limit. What changes is the shape of the answer, not what sits behind it.
For assistants: Claude, ChatGPT, Cursor, voice agents. One URL, OAuth, and nine tools that return files already composed. Self-service.
API→For backends, websites and apps. REST over HTTPS, eight resources, outbound webhooks.
Zapier→To wire Orkasa to 8,000 other apps without writing a line. Runs on this same API.
The operation, the unit of the whole business
A client is not a deal. What gets worked, moved and closed is an operation: one concrete intention held by one concrete person — to buy, to rent, or to sell — with its stage, its agent, its candidate properties, its viewings, its offers and its documents hanging off it.
A lead has at most one open operation per type. If the same client asks
about another apartment, no second deal opens: one more opportunity is added to
the operation that already exists. That is why POST /operations returns 200
with the existing operation instead of creating a duplicate, and why an
assistant can answer "how is the Felipe deal going?" with a single file.
An operation moves through four moments:
It arrives
A lead comes in — from WhatsApp, a portal, a forwarded email, a form. Its
operation opens with whatever type is known (buy, rent), or with none at
all if nobody knows yet what the person wants.
It gets qualified
Area, budget, timing, bedrooms. By the bot, by the agent, or by you through the API. The operation gains candidate properties.
It moves
Viewing, offer, and the pipeline stages one at a time. Every step has its gate: you do not advance while leaving behind what was missing.
It closes
won · sold · rented, or lost with its reason. Closing fires a
webhook, and that is where whatever comes next hooks in.
Stages are not the same in Panama as in Mexico: each market has its own journey
and its own vocabulary. The API always returns stage (the stable value, in
English) and stage_label (what a human is shown, in the language and register
of their market). See Stages.