Dropbox Sign (HelloSign) Signature Request API is one of 13 APIs that Dropbox Sign (HelloSign) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Signature Request. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes
20 operations
across 20 paths,
and defines 42 schemas.
It is described by OpenAPI 3.2.0, at version 3.0.0.
Requests are made against a single base URL, https://api.hellosign.com/v3.
20 operations20 paths42 schemas5 GET11 POST4 PUT
Metadata
The identity and technical contract details declared by the specification.
Dropbox Sign (HelloSign) Signature Request API declares
2 security schemes
for authenticating requests.
It accepts HTTP basic authentication (api_key).
It accepts HTTP bearer tokens (JWT) (oauth2).
By default, every request must be authenticated.
api_key — Your API key can be used to make calls to the Dropbox Sign API. See [Authentication](/api/reference/authentication) for more information. ✅ Supported by Try it…
oauth2 — You can use an Access Token issued through an OAuth flow to send calls to the Dropbox Sign API from your app. The access scopes required by this endpoint are l…
Paths & Operations 20
Across 20 paths, the API surfaces 20 operations — 5 GET, 11 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.
The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are SignatureRequestEditRequest (25 properties), SignatureRequestResponse (25 properties), SignatureRequestSendRequest (25 properties), SignatureRequestEditEmbeddedRequest (24 properties). Each schema is shown below with its type and property counts.
ErrorResponseError
object
Contains information about an error that occurred.
This allows the requester to specify the types allowed for creating a signature and specify another signing options. NOTE: If signingoptions are not defined in…
6 properties1 required
SubFormFieldRule
object
4 properties4 required
WarningResponse
object
A list of warnings.
2 properties2 required
SubAttachment
object
4 properties2 required
SubFormFieldsPerDocumentBase
object
The fields that should appear on the document, expressed as an array of objects. (For more details you can read about it here: [Using Form Fields per Document]…
11 properties9 required
SignatureRequestResponseAttachment
object
Signer attachments.
6 properties4 required
SignatureRequestEditEmbeddedRequest
object
24 properties1 required
SubSignatureRequestTemplateSigner
object
6 properties3 required
SignatureRequestSendWithTemplateRequest
object
16 properties2 required
SignatureRequestGetResponse
object
2 properties1 required
SignatureRequestUpdateRequest
object
4 properties1 required
SignatureRequestEditWithTemplateRequest
object
16 properties2 required
ErrorResponse
object
1 property1 required
SignatureRequestCreateEmbeddedWithTemplateRequest
object
15 properties3 required
SignatureRequestEditRequest
object
25 properties
SubSignatureRequestGroupedSigners
object
3 properties2 required
FileResponseDataUri
object
1 property1 required
SignatureRequestSendRequest
object
25 properties
SignatureRequestRemindRequest
object
2 properties1 required
SubCC
object
2 properties2 required
ListInfoResponse
object
Contains pagination information about the data returned.
4 properties
SignatureRequestResponseDataBase
object
An array of form field objects containing the name, value, and type of each textbox or checkmark field filled in by the signers.
5 properties
SignatureRequestResponse
object
Contains information about a signature request.
25 properties
SignatureRequestListResponse
object
3 properties2 required
SubSignatureRequestSigner
object
6 properties2 required
BulkSendJobResponse
object
Contains information about the BulkSendJob such as when it was created and how many signature requests are queued.
4 properties
SignatureRequestCreateEmbeddedRequest
object
24 properties1 required
SignatureRequestEditEmbeddedWithTemplateRequest
object
15 properties3 required
BulkSendJobSendResponse
object
2 properties1 required
SubCustomField
object
When used together with merge fields, customfields allows users to add pre-filled data to their signature requests. Pre-filled data can be used with "send-once…
4 properties1 required
SubFormFieldRuleAction
object
4 properties2 required
SignatureRequestResponseCustomFieldBase
object
An array of Custom Field objects containing the name and type of each custom field. Text Field uses SignatureRequestResponseCustomFieldText Checkbox Field uses…
5 properties2 required
SignatureRequestResponseSignatures
object
An array of signature objects, 1 for each signer.
19 properties
FileResponse
object
2 properties2 required
SubFormFieldGroup
object
3 properties3 required
SubFieldOptions
object
This allows the requester to specify field options for a signature request.
1 property1 required
SubBulkSignerListCustomField
object
2 properties2 required
SignatureRequestBulkSendWithTemplateRequest
object
13 properties1 required
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Dropbox Sign (HelloSign) Signature Request API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.
