Version: 1.0.0
Doc E Sign API
The Doc E Sign REST API lets you send documents for signature, list and retrieve envelopes, resend signing invitations, and verify document integrity — all programmatically.
Authentication
The API accepts either of two methods on every endpoint below that requires authentication (endpoints are tried in this order):
- API key —
Authorization: Bearer <api_key>. Generate a key from the dashboard's API settings page. Recommended for server-side integrations.- Session cookie — suitable when you already control a Doc E Sign browser session. See the Sandbox page for a step-by-step guide.
Authentication
- HTTP: Bearer Auth
- API Key: sessionCookie
API key, generated from the dashboard's API settings page. Sent as
Authorization: Bearer <api_key>.
Security Scheme Type: | http |
|---|---|
HTTP Authorization Scheme: | bearer |
Supabase session access token. Obtain by signing in at doc-e-sign.com/sign-in and copying the cookie from your browser's DevTools (Application → Cookies). See the Sandbox page for a step-by-step guide.
Security Scheme Type: | apiKey |
|---|---|
Cookie parameter name: | sb-access-token |
Contact