JustDocs Developers

Appearance

Changelog ​

We add to the API without breaking it. New fields, events and tools can appear at any time, so ignore what you don't recognise. A change that would break existing code gets a new version and notice here first.

November 2026 ​

  • Agents create templates (November 10, 2026). create_template (POST /templates) saves a template from text with fill-ins and signing fields, or as a copy of a library entry such as mutual-nda or w9-request. The documents permission now allows it, so keys and connected apps that have documents can create templates as well as start documents from them. It emails no one and needs no approval; sending a document started from it through an agent key waits for approval as before. See Create a template. In the app, the library's free documents and forms can be saved straight as templates with Save as template.
  • Which workspace a key works in (November 10, 2026). get_workspace (GET /workspace) names the key's workspace ("Personal" for a personal one), its plan and saved templates, and what the key may do, including whether its sends wait for approval. list_templates adds workspace, get_template and create_template return the template's roles, and a template or document the key can't reach gets a 404 that names the key's workspace. The MCP server now has 14 tools. Each key's row on the API & agents page is labelled Agent key or API key, and Sends wait for approval or Sends go out at once. See Which workspace a key works in.
  • Agents on every plan (November 5, 2026). Agent keys, the MCP server, apps that sign in with OAuth, and the REST API with an agent key now work on every plan, Free included, in personal workspaces and teams. Everything an agent asks to send still waits for a person's approval. Below Teams & Platform, a workspace can have 3 active agent keys, and a connected app counts as one. API keys, whose sends can go out without approval, and webhooks stay with Teams & Platform. A workspace that leaves Teams & Platform keeps its agent keys and connected apps. See Plans and limits.
  • Sign in with OAuth (November 3, 2026). MCP clients such as Claude, ChatGPT, Muse and Claude Code can connect to the MCP server by signing in, without a key. An owner or admin approves the app on a JustDocs page and chooses its workspace, permissions and limits. The app then acts as an agent key in their name, so its sends still wait for approval. The server supports OAuth 2.1 with PKCE, rotating refresh tokens, Client ID Metadata Documents and Dynamic Client Registration. Agent keys work as before. See Sign in with OAuth.
  • Developer docs launched at tryjustdocs.com/docs. They include a reference generated from the code for every MCP tool, REST operation and webhook event, plus guides and Markdown copies of every page for assistants.
  • MCP Registry. The server is listed in the official MCP Registry as com.tryjustdocs/justdocs.

October 2026 ​

  • API v1, the MCP server and webhooks came to Teams & Platform:
    • REST operations for templates, documents, signing requests, intake links and approvals, described by OpenAPI 3.1.
    • Twelve MCP tools over Streamable HTTP, for agent keys.
    • Approvals: what an agent asks to send waits for an owner or admin.
    • Signed webhooks for ten events, retried, with pausing and a delivery log.
    • API and agent keys with permissions, recipient domains, daily send limits and expiry.