DocSend is a secure document sharing and analytics platform, now part of Dropbox, used by sales, marketing, and fundraising teams to share pitch decks, sales collateral, and confidential documents through trackable links. It provides page-by-page viewer analytics, granular access controls (email verification, passcodes, expiration, watermarking), virtual data rooms, and e-signature. DocSend was surfaced as a portfolio company of Cowboy Ventures, DCM Ventures, and Uncork Capital and enriched by the API Evangelist pipeline. DocSend publishes no public REST API and no OpenAPI; its only programmatic surface is a live, OAuth-secured hosted Model Context Protocol (MCP) server at https://docsend.com/mcp, backed by RFC 8414 authorization-server discovery, RFC 9728 protected-resource metadata, dynamic client registration (RFC 7591), and mandatory PKCE. In August 2026 DocSend replaced the server's two coarse mcp:read / mcp:write scopes with five resource-scoped ones — documents:read, spaces:read, spaces:write, analytics:read, contacts:read.
DocSend is listed with 1 API on the APIs.io network. Tagged areas include Company, Enterprise, Document Sharing, Sales Enablement, and Analytics.
The DocSend catalog on APIs.io includes 1 event-driven AsyncAPI specification.
DocSend’s developer surface includes authentication, pricing, signup flow, support, engineering blog, and 20 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/docsend/"><img src="https://apis.io/badge/docsend/card.svg" alt="DocSend on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics+8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
DocSend's hosted Model Context Protocol server — the only programmatic surface DocSend publishes. An MCP client POSTs Streamable-HTTP JSON-RPC to https://docsend.com/mcp (also r...
aid: docsend
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: self-serve
trial: true
try_now: false
public: false
label: Self-serve signup, paid plans from $30/user/month
confidence: high
source:
- https://www.docsend.com/pricing/
- https://www.docsend.com/signup
- authentication
generated: '2026-08-14'
method: searched
note: 'Upgraded from derived/unknown. The pricing page was read directly on 2026-08-14: three self-serve tiers (Standard
$30/user/month, Advanced $150/month, Advanced Data Rooms $180/month) each with a "Get Started Free" trial, plus Contact
Sales above that. The API/MCP surface itself is not sold or documented at any tier.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/docsend.png
name: DocSend
description: DocSend is a secure document sharing and analytics platform, now part of Dropbox, used by sales, marketing, and
fundraising teams to share pitch decks, sales collateral, and confidential documents through trackable links. It provides
page-by-page viewer analytics, granular access controls (email verification, passcodes, expiration, watermarking), virtual
data rooms, and e-signature. DocSend was surfaced as a portfolio company of Cowboy Ventures, DCM Ventures, and Uncork Capital
and enriched by the API Evangelist pipeline. DocSend publishes no public REST API and no OpenAPI; its only programmatic
surface is a live, OAuth-secured hosted Model Context Protocol (MCP) server at https://docsend.com/mcp, backed by RFC 8414
authorization-server discovery, RFC 9728 protected-resource metadata, dynamic client registration (RFC 7591), and mandatory
PKCE. In August 2026 DocSend replaced the server's two coarse mcp:read / mcp:write scopes with five resource-scoped ones
— documents:read, spaces:read, spaces:write, analytics:read, contacts:read.
url: https://raw.githubusercontent.com/api-evangelist/docsend/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- cowboy-ventures
- dcm-ventures
- uncork-capital
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-14'
tags:
- Company
- Enterprise
- Document Sharing
- Sales Enablement
- Analytics
- Virtual Data Room
- E-Signature
- MCP
- Dropbox
tags_raw:
- Company
- Enterprise
- Document Sharing
- Sales Enablement
- Analytics
- Data Room
- E-Signature
- MCP
- Dropbox
apis:
- name: DocSend MCP Server
description: 'DocSend''s hosted Model Context Protocol server — the only programmatic surface DocSend publishes. An MCP
client POSTs Streamable-HTTP JSON-RPC to https://docsend.com/mcp (also reachable at https://mcp.docsend.com/mcp) with
an OAuth 2.0 bearer token. The authorization surface is fully machine-discoverable: RFC 8414 authorization-server metadata,
RFC 9728 protected-resource metadata, RFC 7591 dynamic client registration and mandatory PKCE (S256). Five resource scopes
are advertised — documents:read, spaces:read, spaces:write, analytics:read, contacts:read — so the surface spans documents,
Spaces (virtual data rooms), viewer analytics and contacts, with Spaces the only writable domain. The tool list is behind
the bearer requirement and DocSend publishes no MCP documentation, so tools must be discovered after authorizing.'
humanURL: https://www.docsend.com/
baseURL: https://docsend.com/mcp
tags:
- MCP
- Agents
- Document Sharing
- Virtual Data Room
- Analytics
tags_raw:
- MCP
- Agents
- Document Sharing
- Data Room
- Analytics
properties:
- type: MCPServer
url: mcp/docsend-mcp.yml
- type: Authentication
url: authentication/docsend-authentication.yml
- type: OAuthScopes
url: scopes/docsend-scopes.yml
- type: RateLimits
url: rate-limits/docsend-rate-limits.yml
x-humanurl-note: DocSend publishes no documentation page for this API — no developer portal, no API reference, no MCP setup
guide on any readable host. humanURL points at the product the API serves, which is the closest human-readable page that
genuinely exists. No Documentation / DeveloperPortal / APIReference pointer is emitted for this repo, because none of
those pages exist.
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: MCPServer
url: mcp/docsend-mcp.yml
- type: WellKnown
url: well-known/docsend-well-known.yml
- type: Authentication
url: authentication/docsend-authentication.yml
- type: OAuthScopes
url: scopes/docsend-scopes.yml
- type: Conformance
url: conformance/docsend-conformance.yml
- type: Compliance
url: https://www.docsend.com/trust-center/compliance
- type: TrustCenter
url: security/docsend-trust-center.yml
- type: DomainSecurity
url: security/docsend-domain-security.yml
- type: LLMsTxt
url: llms/docsend-llms.txt
- type: Lifecycle
url: lifecycle/docsend-lifecycle.yml
- type: StatusPage
url: https://status.dropbox.com/
- type: Packages
url: packages/docsend-packages.yml
- type: Plans
url: plans/docsend-plans-pricing.yml
- type: RateLimits
url: rate-limits/docsend-rate-limits.yml
- type: VulnerabilityDisclosure
url: security/docsend-vulnerability-disclosure.yml
- type: Security
url: https://app.intigriti.com/programs/dropbox/dropbox-vdp
- type: Website
url: https://www.docsend.com
- type: Pricing
url: https://www.docsend.com/pricing/
- type: SignUp
url: https://www.docsend.com/signup
- type: Login
url: https://docsend.com/login
- type: TermsOfService
url: https://www.docsend.com/terms-of-service/
- type: PrivacyPolicy
url: https://www.docsend.com/privacy-policy
- type: Support
url: https://help.docsend.com/hc/en-us
- type: Blog
url: https://www.docsend.com/blog
- type: GitHubOrganization
url: https://github.com/docsend
x-enrichment:
date: '2026-08-14'
status: enriched
artifacts_added: 9
pass: local-v1
DocSend API — frequently asked questions
Does DocSend have an API?
Yes. APIs.io lists 1 API from DocSend, including DocSend MCP Server.
How do I authenticate with the DocSend API?
DocSend documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Docsend Authentication.
How much does the DocSend API cost?
DocSend publishes its prices; its Standard plan is $30/user/month as of 2026-10-28. APIs.io lists 4 pricing plans for DocSend, with each plan's price, limits and inclusions under Pricing on this page.
Does DocSend have an MCP server?
Yes. APIs.io lists 1 MCP server for DocSend: Remote MCP server at docsend.com over HTTP.
Is the DocSend API ready for AI agents?
DocSend has a Kin Score of 50.1 out of 100 (developing) and an Agent Readiness score of 47.1 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.