Appearance
Build on JustDocs
JustDocs is where a team writes documents, sends them for signature and collects the details that fill them in. The developer platform lets your software and AI agents do the same work through the same rules:
- The REST API at
https://tryjustdocs.com/api/v1, for your own software. - The MCP server at
https://tryjustdocs.com/mcp, for AI agents. It has the same commands, as tools. - Webhooks, so your systems hear when something is sent, viewed, signed, completed, answered or approved.
Agents work on every plan, Free included, in personal workspaces and teams, through the MCP server or the REST API with an agent key. API keys for your own software, and webhooks, come with the Teams & Platform plan, in a team workspace.
The records
| Record | What it is |
|---|---|
| Template | A reusable document with fill-ins (named blanks such as client_name) and, often, an intake form whose questions answer them. Written in the editor, made from a PDF, saved from the library, or created through the API with create_template. |
| Document | A document started from a template, with its fill-ins completed. It has a draft_revision that goes up when it changes. |
| Signing request | One or more documents sent to one or more recipients. Each recipient signs as a role (such as client), in order or all at once. |
| Intake link | A form emailed to one person. Their answers fill the documents, then either you review them or they go straight on to sign. |
| Approval | A send that waits for an owner or admin, because an agent key, or a key set to need approval, asked for it. |
A signing request moves from draft to sent, then ends completed, declined, voided or expired. Each recipient goes from pending to notified, viewed and signed, or declined.
Keys, permissions and approvals
Keys are made on the workspace's API & agents page: in your personal workspace by you, and in a team by its owners and admins. A key works only in the workspace it was made in, and get_workspace says which. A key acts for the person who made it. It sends invitations in their name and stops working if they stop being an owner or admin.
- API keys are for your team's own software, on Teams & Platform. Their sends go out at once, unless you set them to need approval.
- Agent keys are for AI agents, on every plan, and are the only keys the MCP server takes. Everything an agent key asks to send waits for a person's approval. Below Teams & Platform, a workspace can have 3.
- Connected apps are AI clients that sign in with OAuth instead of being given a key, such as Claude, ChatGPT or Muse. Connecting one makes an agent key for it, in the name of the person who connected it.
Each key has permissions, and can be limited to recipient domains and a number of sends a day. Each key also expires. See Keys and permissions.
What no key can do
- Sign, accept or decline on anyone's behalf.
- Read a recipient's signing link. Recipients get it by email only.
- Reach another workspace's records.
- Act as a person who is no longer an owner or admin.
Next
- Quick start A key, a client and a first approved send.
- Plans and limits What each plan includes, and every limit in one table.