DocJacket Platform API

Documentation

• Interactive API reference Browse and try every operation in the browser.
• OpenAPI 3.1 (JSON) The canonical machine-readable contract.
• OpenAPI 3.1 (YAML) The same contract, YAML serialization.
• Markdown API reference Every operation as plain text — no JavaScript.
• Integration guide Recommended call sequences, start to finish.
• llms.txt Concise index for AI tools and agents.
• llms-full.txt Expanded overview of the API model.
• Guides & tutorials Authentication, requests, webhooks, partner tier.

What you can build

• Transactions — create, search, and update deals; manage checklists, contingencies, notes, statuses, and reminders.
• Key dates & tasks — read and write the negotiated deadlines that drive the transaction, and the work items hanging off them.
• Documents & extraction — upload a contract and have DocJacket read it, returning structured fields with confidence and citations back to the source.
• Messaging — send client updates and document requests, draft and schedule messages, and read the unified per-deal communication log.
• Contacts & disclosures — people and companies with roles; assemble seller disclosure packages and track recipient access.
• Webhooks — subscribe to events and be pushed changes instead of polling.
• Partner provisioning — white-label partners provision and administer organizations across their book of business.

Authentication

Every operation takes a bearer token. There are three credential types, and each is rejected on the other's routes.

How to choose: mcp_at_ is one organization whose key you hold yourself. rsk_ is provisioning across your tenants, and it never reaches deal data. OAuth is an application acting on behalf of many users — the only one of the three shaped to scale past a handful of hand-issued keys.

OAuth clients register dynamically (RFC 7591) at /oauth/register and should read the flow's endpoints from /.well-known/oauth-authorization-server rather than hardcoding them — authorization code + PKCE, no client secret.

A resource belonging to another organization returns 404, never 403 — existence is never disclosed across tenants.

Integration path

1. Obtain an API key in DocJacket under Settings → Advanced → API & AI Access.
2. Verify it with the health endpoint — it echoes your organization and scopes.
3. Inspect the catalog — every operation, flagged callable against your key.
4. Create or retrieve transactions, then attach key dates, tasks, and documents.
5. Subscribe to webhooks so changes are pushed to you instead of polled.

# 1. Does my key work? Echoes your organization and granted scopes.
curl https://api.docjacket.com/api/v1/health \
  -H "Authorization: Bearer $DOCJACKET_API_KEY"

# 2. What can this key call? Every operation, with a callable flag.
curl https://api.docjacket.com/api/v1/catalog \
  -H "Authorization: Bearer $DOCJACKET_API_KEY"

# 3. The book of business.
curl https://api.docjacket.com/api/v1/transactions \
  -H "Authorization: Bearer $DOCJACKET_API_KEY"

Conventions