Dropbox Sign (HelloSign)
Dropbox Sign (formerly HelloSign) is an eSignature platform whose v3 REST API lets developers send documents for legally binding electronic signature, build reusable templates, embed signing directly in their own apps, run bulk send jobs, and manage accounts, teams, and API apps. The API exposes 73 operations across 12 product areas (Signature Request, Template, Bulk Send, Embedded, Account, Team, Report, Fax, Fax Line, Unclaimed Draft, API App, OAuth), with API-key and OAuth 2.0 authentication, 23 webhook event types, official SDKs in six languages, and a published hosted documentation MCP server. HelloSign was a Y Combinator company (S11), acquired by Dropbox in 2019 and rebranded to Dropbox Sign in 2022; the API base host remains api.hellosign.com.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Dropbox Sign (HelloSign) the way a machine reads it — 20 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Dropbox Sign (HelloSign) scores 62.8/100 (strong), with a separate agent-readiness read of 71/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Dropbox Sign (HelloSign)
Each block below is one kind of artifact we hold for Dropbox Sign (HelloSign). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Dropbox Sign (HelloSign) Account API
{'$ref': './markdown/en/tags/account-tag-description.md'}
Dropbox Sign (HelloSign) Api App API
{'$ref': './markdown/en/tags/api-app-tag-description.md'}
Dropbox Sign (HelloSign) Bulk Send Job API
{'$ref': './markdown/en/tags/bulk-send-job-tag-description.md'}
Dropbox Sign (HelloSign) Embedded API
{'$ref': './markdown/en/tags/embedded-tag-description.md'}
Dropbox Sign (HelloSign) Fax API
The Fax API from Dropbox Sign (HelloSign) — 4 operation(s) for fax.
Dropbox Sign (HelloSign) Fax Line API
{'$ref': './markdown/en/tags/fax-lines-tag-description.md'}
Dropbox Sign (HelloSign) OAuth API
{'$ref': './markdown/en/tags/oauth-tag-description.md'}
Dropbox Sign (HelloSign) Report API
{'$ref': './markdown/en/tags/report-tag-description.md'}
Dropbox Sign (HelloSign) Signature Request API
{'$ref': './markdown/en/tags/signature-request-tag-description.md'}
Dropbox Sign (HelloSign) Team API
{'$ref': './markdown/en/tags/team-tag-description.md'}
Dropbox Sign (HelloSign) Template API
{'$ref': './markdown/en/tags/template-tag-description.md'}
Dropbox Sign (HelloSign) Unclaimed Draft API
{'$ref': './markdown/en/tags/unclaimed-draft-tag-description.md'}
Scroll within the panel for all 12 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
hellosign-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Hellosign Events Webhooks
ASYNCAPISecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Hellosign Trust Center
HIPAA, ISO 9001, SOC (CPA/AICPA attestation), Skyhigh Enterprise-Ready
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Dropbox Sign (HelloSign) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/hellosign · machine-readable index on apis.io