Build your product. DocJacket runs the transactions underneath it.
Create your own real-estate app, brokerage portal, or agent assistant on the DocJacket API — 100+ documented endpoints, public reference, and webhooks.
You own the product, the brand, and the customer relationship. DocJacket provides the transaction system of record underneath it.
Public reference · No sales call to start · API access included with every paid plan
Your frontend. Your brand. Your vision.
The hard part of real-estate software is not the interface — it is the transaction underneath it. Build the first; start with the second already done.
You control
DocJacket provides
What is actually in the API
Not a roadmap. Every group below is in the published contract today — read it yourself before you talk to anyone.
Transactions
25 opsSearch, read, and update transactions; status, contingencies, notes, activity, portal links, and communication reports.
Messaging
17 opsConversations, threaded messages, scheduled sends, and the four transactional email flows — client updates, document requests, agent follow-ups, and direct agent email.
Documents
11 opsList, upload, classify, split, version, share, and generate view URLs for transaction documents.
Webhooks
9 opsSubscribe to transaction and document events. Signed payloads, a test endpoint, secret rotation, and a delivery log you can inspect.
Tasks
8 opsCreate, assign, complete, reschedule, comment on, and bulk-delete tasks, plus checklist state per transaction.
Disclosure packages
7 opsCreate packages, set their documents, activate them, invite and revoke recipients, and read recipient activity.
Organizations (partner)
7 opsProvision customer organizations, list them, invite and remove seats, and read each org’s plan, seats, and fair-use state.
Templates & forms
7 opsEmail templates, merge fields, template rendering, form definitions, form links, and submissions.
Contacts
6 opsSearch contacts, look them up by email, create them, attach them to transactions, and manage contact roles.
Proposals
5 opsThe approval workflow: read a pending AI proposal and its payload, then approve or reject it. Nothing acts without a decision.
Organization
5 opsAssignable team members, notifications and unread counts, device registration.
Extractions
3 opsKick off a contract extraction, poll the job, and fetch its source document.
Meta
4 opsHealth, per-key usage and error rate, transaction statuses, and a catalog endpoint that tells you exactly what your key may call.
Key dates
1 opsUpcoming key dates across the organization, plus per-transaction key-date reads and writes under Transactions.
Every endpoint, request shape, and response is in the public API reference →
What people build on it
Agent and brokerage applications
Build an action feed, mobile assistant, compliance dashboard, or brokerage portal without rebuilding transaction infrastructure.
Virtual TC platforms
Provision organizations, invite operational users, manage transactions, and deliver your own service experience end to end.
Existing real-estate software
Add contract-to-transaction capabilities to a CRM, forms product, coaching platform, or any other real-estate application.
Specialized transaction products
Create an experience for a particular state, brokerage model, transaction type, or customer segment.
Two ways to build
What you can do is decided by your key, not by a plan negotiation. Building for your own organization is included; building for other people’s organizations is the partner tier.
Build on your own organization
Build across your customers’ organizations
Includes 3 operator seats. Additional operator seats $25/month each — whether you create them in the dashboard or through the API.
Self-serve · Month-to-month · No approval queue
More people use the platform than you pay seats for
Operator seats are the people who run transactions. Agents can review their transactions through Agent Portals, and buyers, sellers, and other transaction parties can use Client Portals — without purchasing individual operator seats. You pay primarily for the users doing the operational work, not for everyone your product touches.
Start in three calls
Read the reference
The full API reference is public — no login, no sales call. Browse every endpoint, request shape, and response before you commit to anything.
Get a key
Mint an organization key in settings, or start a Platform Partner account if you need to provision organizations for your own customers.
Call the catalog
Hit /health, then /catalog — it returns exactly which operations your key is allowed to call, so you know your permissions before you write a line of integration code.
# 1. Confirm your key works
curl -H "Authorization: Bearer $DJ_API_KEY" \
https://api.docjacket.com/api/v1/health
# 2. See exactly what this key is allowed to call
curl -H "Authorization: Bearer $DJ_API_KEY" \
https://api.docjacket.com/api/v1/catalog
# 3. Read your transactions
curl -H "Authorization: Bearer $DJ_API_KEY" \
https://api.docjacket.com/api/v1/transactions# Partner keys only — provision a customer organization
curl -X POST -H "Authorization: Bearer $DJ_PARTNER_KEY" \
https://api.docjacket.com/api/v1/orgsThree ways to work with DocJacket
| If you want to | Choose |
|---|---|
| Use DocJacket directly | DocJacket → |
| Launch DocJacket under your brand | White-Label Program → |
| Build your own application | Platform API — you are here |
Not sure this is the piece you need?
You want an AI assistant working in your own transactions
That needs no code at all. The DocJacket MCP server connects Claude, ChatGPT, Codex, Cowork, and Gemini directly to your organization so they can search, draft, and update transactions for you.
You just want DocJacket to talk to the tools you already use
Most of that is already built. See the integrations before writing anything against the API.
You are evaluating whether you would be stuck here
Fair question to ask before you build on someone else's backend. Open by Design covers the API, exports, and pricing transparency in one place.
Frequently asked questions
Does DocJacket have an API?
Yes. The DocJacket API v1 is live and publicly documented at https://api.docjacket.com/reference, with 101 documented endpoints covering transactions, contacts, key dates, tasks, documents, contract extraction, messaging, disclosure packages, webhooks, and organization provisioning.
Is the API documentation public?
Yes — no login required. The interactive reference is at https://api.docjacket.com/reference, and the raw OpenAPI document is served at https://api.docjacket.com/reference/dj-api.json for tooling, code generation, and AI assistants.
How do I authenticate?
A bearer API key on every request. There are two kinds: an organization key, scoped to a single organization, and a partner key, scoped across the organizations you provision. A key that calls an operation outside its scope is rejected — you can check what any key is allowed to do by calling the catalog endpoint.
What does the API cost?
Organization-level API access is included with every paid DocJacket plan at no additional charge. Partner access — provisioning and managing customer organizations — is the Platform Partner subscription at $297/month, which includes 3 operator seats; additional operator seats are $25/month each.
Can I create users through the API?
Yes. Partner keys can invite a seat into any organization you provision and remove seats again, and you can read each organization’s current plan and seat state. Seats created through the API are billed exactly like seats invited from the dashboard — the same $25/month per additional operator seat. There is no separate API user fee and no second meter to reconcile.
Do all of my app’s users need to be paid seats?
No. Operator seats are for the people doing the operational work — the users who manage transactions. Agents can review their transactions through Agent Portals, and buyers, sellers, and other transaction parties can use Client Portals, without purchasing individual operator seats.
Can I provision customer organizations through the API?
Yes. A partner key can create a customer organization on demand, invite its users, read its plan and seat state, and act on its transactions — all from your own systems, without anyone signing in through the DocJacket interface.
Does the API support webhooks?
Yes. Subscribe to transaction and document events, and DocJacket delivers signed payloads to your endpoint with automatic retries. You can send a test delivery, rotate the signing secret, and inspect a delivery log to see exactly what was sent and what came back.
Can I build a mobile app on DocJacket?
Yes. The API exposes the transaction system of record, so you own the client entirely — native iOS, Android, web, or anything else. DocJacket runs the transaction infrastructure underneath, and your users never have to see DocJacket.
Is there rate limiting?
Yes. Requests are rate limited per API key, and a usage endpoint reports your call volume, daily breakdown, top operations, and error rate. If your integration needs a higher budget, get in touch and we will scope it.
Do you version the API?
Yes. The current version is v1 and it appears in the URL path. Within a major version we only add — new endpoints, new optional fields, new response fields, new enum values — so clients should ignore fields and values they do not recognize. Anything that would break an existing client ships as a new major version.
What is the difference between the Platform API and the White-Label Program?
The White-Label Program gives you DocJacket’s finished application under your own brand — your logo, domain, and email, with no development work. The Platform API is for building your own application on top of DocJacket’s backend. Use the White-Label Program if you want a product now; use the Platform API if you want to build the product yourself.
What is the difference between the API and the MCP server?
The MCP server is the no-code path: it connects an AI assistant like Claude or ChatGPT to your own DocJacket organization so it can search, draft, and update transactions for you. The Platform API is the developer path: you write software against it and ship a product to your own customers.
What happens to my data if I stop?
You can export it. DocJacket is built to be open — an API you can read everything through, no proprietary export barriers, and public pricing.
Stop rebuilding the transaction. Build the product.
Contracts, key dates, tasks, documents, messaging, permissions, and webhooks are already built, documented, and running. Read the reference and decide for yourself.
API access included with every paid plan · Platform Partner $297/month, 3 operator seats included