| name | documenso-security-basics |
| description | Implement security best practices for Documenso document signing integrations.
Use when securing API keys, configuring webhooks securely,
or implementing document security measures.
Trigger with phrases like "documenso security", "secure documenso",
"documenso API key security", "documenso webhook security".
|
| allowed-tools | Read, Write, Edit |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","documenso","api","security","webhooks"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Documenso Security Basics
Overview
Essential security practices for Documenso integrations: API key management, webhook verification, document access control, and self-hosted signing certificate configuration.
Prerequisites
- Documenso account with API access
- Understanding of environment variables and secret management
- Completed
documenso-install-auth setup
Instructions
Step 1: API Key Security
const BAD = new Documenso({ apiKey: "api_abc123..." });
const GOOD = new Documenso({ apiKey: process.env.DOCUMENSO_API_KEY! });
Key management rules:
- Store in
.env (never committed) or a secrets manager (Vault, AWS Secrets Manager)
- Use team-scoped keys for team resources, personal keys for personal documents
- Rotate keys on employee offboarding -- revoke in dashboard immediately
- CI/CD: use masked/encrypted secrets (GitHub Secrets, GitLab CI variables)
.env
.env.*
!.env.example
Step 2: Key Rotation with Zero Downtime
function getApiKey(): string {
return process.env.DOCUMENSO_API_KEY_PRIMARY
?? process..
?? ( { (); })();
}