DocuSign REST API

{
  "service_type": "platform",
  "base_url": "https://developers.docusign.com",
  "auth_method": "oauth2",
  "auth_config": {
    "grant_types": ["authorization_code", "jwt_bearer", "implicit"],
    "token_endpoint": "https://account-d.docusign.com/oauth/token",
    "production_token_endpoint": "https://account.docusign.com/oauth/token",
    "scopes": [
      "signature",
      "extended",
      "impersonation",
      "openid",
      "aow"
    ],
    "notes": "OAuth 2.0 with JWT Grant or Authorization Code Grant. Legacy X-DocuSign-Authentication header is deprecated."
  },
  "endpoints": [
    {
      "name": "Envelopes",
      "path": "/restapi/v2.1/accounts/{accountId}/envelopes",
      "method": "GET/POST",
      "description": "Create, list, and manage signature envelopes."
    },
    {
      "name": "Envelope Recipients",
      "path": "/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/recipients",
      "method": "GET/POST/DELETE",
      "description": "Manage recipients on an envelope."
    },
    {
      "name": "Templates",
      "path": "/restapi/v2.1/accounts/{accountId}/templates",
      "method": "GET/POST",
      "description": "List and create templates."
    },
    {
      "name": "Documents",
      "path": "/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents",
      "method": "GET/POST/PUT",
      "description": "Manage documents within an envelope."
    },
    {
      "name": "Folders",
      "path": "/restapi/v2.1/accounts/{accountId}/folders",
      "method": "GET",
      "description": "List folders and their contents."
    },
    {
      "name": "Users",
      "path": "/restapi/v2.1/accounts/{accountId}/users",
      "method": "GET/POST",
      "description": "Manage account users."
    },
    {
      "name": "Brands",
      "path": "/restapi/v2.1/accounts/{accountId}/brands",
      "method": "GET/POST",
      "description": "Manage branding configurations."
    },
    {
      "name": "Bulk Operations",
      "path": "/restapi/v2.1/accounts/{accountId}/bulk_envelopes",
      "method": "GET/POST",
      "description": "Bulk send envelopes."
    },
    {
      "name": "Connect (Webhooks)",
      "path": "/restapi/v2.1/accounts/{accountId}/connect",
      "method": "GET/POST",
      "description": "Configure webhook subscriptions for envelope events."
    }
  ],
  "pricing_model": {
    "type": "subscription",
    "details": {
      "notes": "DocuSign is a commercial e-signature platform. API access is typically bundled with paid plans (Standard, Business Pro, Enterprise). Envelope volumes and API call limits vary by plan. Free developer sandbox available at developers.docusign.com."
    }
  },
  "rate_limits": {
    "notes": "DocuSign applies per-account API rate limits that vary by plan and are documented in the API guidelines. Typical limits are in the range of requests per hour per account; exact numbers are account-specific.",
    "headers": ["X-RateLimit-Limit", "X-RateLimit-Remaining", "X-RateLimit-Reset"]
  },
  "capabilities": [
    "Electronic signature workflows",
    "Envelope creation and management",
    "Template-based document generation",
    "Recipient routing and authentication",
    "Document upload and retrieval",
    "Webhook/Connect event notifications",
    "Bulk sending (Bulk Operations)",
    "Branding customization",
    "User and account administration",
    "Audit trails and certificate of completion",
    "Embedded signing and sending",
    "Integration with Salesforce, Microsoft, Google, and other platforms"
  ],
  "raw_analysis": "DocuSign REST API is a mature, enterprise-grade API for the DocuSign e-signature platform, one of the dominant players in the electronic signature and agreement management space. It serves businesses of all sizes — from SMBs using standard plans to large enterprises with complex agreement workflows — and is commonly integrated into CRM (Salesforce), productivity (Microsoft 365, Google Workspace), and custom internal systems.\n\nThe API is well-documented at developers.docusign.com and follows RESTful conventions with JSON payloads. Authentication is OAuth 2.0 (Authorization Code Grant for user-context, JWT Grant for server-to-server automation), which replaces the older X-DocuSign-Authentication header approach. The API exposes resources under /restapi/v2.1/accounts/{accountId}/ including envelopes, recipients, templates, documents, folders, users, brands, bulk operations, and Connect webhooks.\n\nMaturity is high: DocuSign has offered its API for over a decade, supports multiple SDKs (Java, C#, Python, Node, PHP, Ruby), provides a sandbox environment, and maintains a robust partner/integration ecosystem. Pricing is subscription-based with API access tied to paid plans; envelope allowances and rate limits depend on the plan tier. Developers should consult DocuSign's API guidelines for exact rate limits, which are per-account and can be tuned by agreement.\n\nOverall, this is a production-ready, widely adop

2/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 9.0,
    "first_try_success": 7.0,
    "response_parseability": 9.0,
    "error_clarity": 8.0,
    "doc_quality": 9.0,
    "auth_simplicity": 5.0,
    "latency": 10.0,
    "consistency": 8.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "notes": "Commercial e-signature platform; API access bundled with paid tiers (Standard/Business Pro/Enterprise). Envelope volumes and API call limits vary by plan. Free developer sandbox available — good for evaluation but production requires paid plan.",
    "free_tier": "developer sandbox only",
    "agent_friendly": "moderate — paid plans needed for production use"
  },
  "issues": [
    "No llms.txt (404) — reduces machine-readable discoverability for agents",
    "Auth is OAuth 2.0 / JWT grant — more complex than magic-link or simple API key flows",
    "Pricing is opaque; API limits tied to plan tier and not publicly unified",
    "robots.txt disallows some doc paths (v2 eSign REST, SOAP, clickwrap test) which may hinder agent crawling of canonical references"
  ],
  "recommendations": [
    "Publish an llms.txt summarizing core e-signature workflows, endpoints, and auth steps for AI agent consumption",
    "Provide clear public documentation of API rate limits per plan tier",
    "Offer a frictionless sandbox onboarding (e.g., instant API key or OAuth with verified identity) to improve agent-assisted setup",
    "Expose a concise OpenAPI/JSON schema summary in llms.txt so agents can plan envelope operations without deep doc traversal"
  ]
}