· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →DocuSeal LLC v2.0.0
Manage e-signatures
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Which vendor agreement templates are available?
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.
From the marketplace listing
DocuSeal lets you create document templates from PDFs, send them for e-signing, and track signing status - all through a simple conversation. Search your templates, send documents to multiple signers, and check who has signed without leaving the chat.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 3 observations
Screenshot urls updated; open the comparison for details. Declared skill added: “docuseal-code”. Declared skill added: “docuseal-cli”. Version changed from “1.0.0” to “2.0.0”.
View comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: docuseal-cli
description: >
Manage DocuSeal e-signature workflows from the terminal via the DocuSeal CLI -
create templates from PDF/DOCX/HTML, send documents for signing, track submissions,
and update submitters. Use when the user wants to run DocuSeal commands in the shell,
scripts, or CI/CD pipelines. Always load this skill before running `docuseal` commands.
license: MIT
metadata:
author: DocuSeal
version: "1.0.7"
homepage: https://www.docuseal.com
source: https://github.com/docusealco/docuseal-cli
openclaw:
emoji: "📝"
requires:
env:
- DOCUSEAL_API_KEY
- DOCUSEAL_SERVER
bins:
- docuseal
primaryEnv: DOCUSEAL_API_KEY
install:
- id: npm
kind: npm
package: docuseal
bins:
- docuseal
label: Install DocuSeal CLI (npm)
---
## Agent Protocol
**Rules for agents:**
- Supply ALL required flags — the CLI will not prompt for missing parameters.
- Output is always JSON.
- Use `-d key=value` (bracket notation) or `-d '{"..": ".."}'` (JSON) for body and array parameters.
## Authentication
Set environment variables:
- `DOCUSEAL_API_KEY` — API key (required). Get yours at https://console.docuseal.com/api
- `DOCUSEAL_SERVER` — `global` (default), `europe`, or full URL for self-hosted (e.g. `https://docuseal.yourdomain.com`)
## Available Commands
| Command Group | What it does |
|---|---|
| `templates` | list, retrieve, update, archive, create-pdf, create-docx, create-html, clone, merge, update-documents |
| `submissions` | list, retrieve, update, archive, create, send-emails, create-pdf, create-docx, create-html, documents |
| `submitters` | list, retrieve, update |
Read the matching reference file for detailed flags and examples.
## Common Mistakes
| # | Mistake | Fix |
|---|---|---|
| 1 | **Forgetting `-d template_id=<id>` on `submissions create`** | `--template-id` is a flag; submitters and other body params go via `-d` |
| 2 | **Passing a plain file path as a URL** | `--file` accepts a local path; for remote files use `-d "documents[0][file]=https://..."` |
| 3 | **Expecting array params as comma-separated** | Arrays use bracket notation: `-d "template_ids[]=1"` `-d "template_ids[]=2"` |
| 4 | **Using `templates create-pdf` without a Pro plan** | Commands marked _(Pro)_ require a DocuSeal Pro subscription |
| 5 | **Sending to multiple recipients with `submissions create`** | Use `submissions send-emails --emails a@b.com,c@d.com` for bulk; `submissions create` is per-submitter |
## Security
The CLI accepts user-provided file paths, remote URLs (`documents[0][file]=https://...`), and HTML content as template input. This is by design — all content originates from the authenticated user and is sent directly to the DocuSeal API over HTTPS. The CLI does not fetch, render, or execute remote content locally; it passes references to the server for processing. No user input is interpolated into shell commands.
## Common Patterns
**List templates:**
```bash
docuseal templates list --q "NDA" --limit 20
```
**Create a template from a PDF and send for signing:**
```bash
docuseal templates create-pdf --file contract.pdf --name "NDA"
docuseal submissions send-emails --template-id 1001 --emails signer@example.com
```
**Create a submission with pre-filled fields (bracket notation):**
```bash
docuseal submissions create --template-id 1001 \
-d "submitters[0][email]=john@acme.com" \
-d "submitters[0][values][Company Name]=Acme Corp"
```
**Create a submission with pre-filled fields (JSON):**
```bash
docuseal submissions create --template-id 1001 \
-d '{"submitters": [{"email": "john@acme.com", "values": {"Company Name": "Acme Corp"}}]}'
```
**Check signing status:**
```bash
docuseal submissions list --template-id 1001 --status pending
```
**Update a submitter:**
```bash
docuseal submitters update 201 --email new@acme.com --send-email
```
## When to Load References
- **Creating or managing templates** → [rePreview of the first 4,000 characters. Read full instructions →
Referenced files: 7 — file references are metadata, not package contents.
--- name: docuseal-code description: > DocuSeal development reference. Embed signing forms and template builder into web and mobile apps (JS/React/Vue/Angular, WebView, JWT, CSS theming). REST API with all endpoints, request/response schemas, code examples (cURL, CLI, Node.js, TypeScript, Python, Ruby, PHP, Go, C#, Java), and webhooks. Use when the user wants to integrate DocuSeal document signing or template management into their application. license: MIT metadata: author: DocuSeal version: "1.0.4" homepage: https://www.docuseal.com/docs source: https://github.com/docusealco/docuseal-agent-skills --- ## How References Are Organised Reference files live in two subdirectories under `references/`: - **`references/embed/`** — Embed UI components (signing forms, template builder). Each file is self-contained — load only the ones matching the user's stack. - **`references/api/`** — REST API endpoints and webhooks. One file per endpoint/webhook with parameters, schemas, code examples, and response samples. ## Embed UI Components | Component | Tag | Purpose | JWT | |---|---|---|---| | Signing Form | `<docuseal-form>` | Embed document signing UI into a page | optional | | Form Builder | `<docuseal-builder>` | Embed a full template/document builder | **required** | Each component ships in four frontend implementations: **JavaScript / React / Vue / Angular**. ### Signing Form (`<docuseal-form>`) - JavaScript / HTML → [references/embed/signing-form-js.md](references/embed/signing-form-js.md) - React → [references/embed/signing-form-react.md](references/embed/signing-form-react.md) - Vue → [references/embed/signing-form-vue.md](references/embed/signing-form-vue.md) - Angular → [references/embed/signing-form-angular.md](references/embed/signing-form-angular.md) - Mobile (Android/iOS/React Native/Flutter via WebView) → [references/embed/signing-form-mobile-integration.md](references/embed/signing-form-mobile-integration.md) ### Form Builder (`<docuseal-builder>`) - JavaScript / HTML → [references/embed/form-builder-js.md](references/embed/form-builder-js.md) - React → [references/embed/form-builder-react.md](references/embed/form-builder-react.md) - Vue → [references/embed/form-builder-vue.md](references/embed/form-builder-vue.md) - Angular → [references/embed/form-builder-angular.md](references/embed/form-builder-angular.md) After loading the main component reference, follow a link from its `## Guides` section for step-by-step walkthroughs. ### Cross-cutting - JWT token generation — Form Builder (Node/TypeScript/Ruby/Python/PHP/Java/C#/Go) → [references/embed/form-builder-jwt-token.md](references/embed/form-builder-jwt-token.md) - JWT token generation — Signing Form completed/preview mode → [references/embed/signing-form-completed-preview-jwt-token.md](references/embed/signing-form-completed-preview-jwt-token.md) - EU Cloud / self-hosted `host` configuration — Signing Form → [references/embed/signing-form-hosts.md](references/embed/signing-form-hosts.md) - EU Cloud / self-hosted `host` configuration — Form Builder → [references/embed/form-builder-hosts.md](references/embed/form-builder-hosts.md) - Custom CSS theming — Signing Form (dark theme reference) → [references/embed/signing-form-custom-css.md](references/embed/signing-form-custom-css.md) - Custom CSS theming — Form Builder (dark theme reference) → [references/embed/form-builder-custom-css.md](references/embed/form-builder-custom-css.md) - Signing Form security recommendations → [references/embed/signing-form-security-recommendations.md](references/embed/signing-form-security-recommendations.md) - Form Builder security recommendations → [references/embed/form-builder-security-recommendations.md](references/embed/form-builder-security-recommendations.md) ### Packages | Framework | Package | CDN | |---|---|---| | JavaScript | — | `https://cdn.docuseal.com/js/form.js`, `https://cdn.docuseal.com/js/builder.js` | | React | `@docuseal/react` | — | | Vue |
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 77 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugin_asdk_app_69aaf6dd80188191837a63290ed3a9b2
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.