The Claude Code plugin
Install seven skills that teach Claude Code this API, then describe the integration you want instead of reading a reference.
All documentation
If you use Claude Code, you can skip most of this documentation. The plugin installs seven skills that describe how this API actually behaves, so you describe the outcome you want and Claude writes the integration against the real contract instead of guessing at one.
Install it
claude plugins marketplace add AngularMinds/documentesign-api-plugin
claude plugins install documentesign@documentesignRestart your session and the skills load. There is nothing to configure, because the plugin ships documentation rather than anything that runs.
Then ask for what you want
You do not need to name a skill. Claude picks whichever fits the request.
- "Add Document eSign to our supplier onboarding so the agreement is signed before the account activates."
- "Verify the webhook signature before we trust the payload."
- "Let people sign inside our app instead of emailing them a link."
The seven skills
| Field | Type | Notes |
|---|---|---|
documentesign-best-practices | skill | Where to start, key handling, how usage is billed. |
documentesign-quickstart | skill | Auth, the sandbox split, scopes, your first call. |
send-from-template | skill | Roles, prefilled fields, the shortest path to a signature. |
send-from-file | skill | Uploading a PDF and placing fields by coordinate. |
embedded-signing | skill | The iframe flow, origin allowlist, browser messages. |
webhooks | skill | The seven events and exact signature verification. |
errors-and-limits | skill | Error shapes, status codes, rate limits, backoff. |
What it will not do
It writes code. It does not touch your account. There is no MCP server inside it and no tools it can call, so installing it gives Claude no path to your documents. Your API key sits in your own environment and is read by the integration running on your machine.
Why it does not drift
The skills live in the same repository as the API routes they describe, so an endpoint change and its documentation land in one review. A conformance check then runs every skill against the live OpenAPI document, which the server generates from its own route schemas. A skill that references a removed endpoint fails the check and the plugin does not ship.
Working without the plugin
Any assistant or client generator can read the same spec:
https://api.documentesign.com/v1/openapi.jsonThe source is public at github.com/AngularMinds/documentesign-api-plugin, and there is a longer walkthrough on the blog: Add eSignatures to Your App.