How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Dropbox Sign (HelloSign) Unclaimed Draft API

{'$ref': './markdown/en/tags/unclaimed-draft-tag-description.md'}

Dropbox Sign (HelloSign) Unclaimed Draft 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 Unclaimed Draft. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 22 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.

4 operations 4 paths 22 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Base URL
https://api.hellosign.com/v3
Authentication
HTTP Basic, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Dropbox Sign (HelloSign) Unclaimed Draft 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 4

Across 4 paths, the API surfaces 4 operations — 4 POST. Each is listed below with its method, path, parameters, and response codes.

Unclaimed Draft 4

{'$ref': './markdown/en/tags/unclaimed-draft-tag-description.md'}

POST
/unclaimed_draft/create
Create Unclaimed Draft
unclaimedDraftCreate body → 2004XX
POST
/unclaimed_draft/create_embedded
Create Embedded Unclaimed Draft
unclaimedDraftCreateEmbedded body → 2004XX
POST
/unclaimed_draft/create_embedded_with_template
Create Embedded Unclaimed Draft with Template
unclaimedDraftCreateEmbeddedWithTemplate body → 2004XX
POST
/unclaimed_draft/edit_and_resend/{signature_request_id}
Edit and Resend Unclaimed Draft
unclaimedDraftEditAndResend 1 param body → 2004XX

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are UnclaimedDraftCreateEmbeddedRequest (36 properties), UnclaimedDraftCreateEmbeddedWithTemplateRequest (30 properties), UnclaimedDraftCreateRequest (24 properties), SubFormFieldsPerDocumentBase (11 properties). Each schema is shown below with its type and property counts.

ErrorResponseError
object
Contains information about an error that occurred.
3 properties 2 required
UnclaimedDraftCreateRequest
object
24 properties 1 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 properties 9 required
SubFormFieldRuleTrigger
object
4 properties 2 required
UnclaimedDraftCreateEmbeddedRequest
object
36 properties 2 required
UnclaimedDraftEditAndResendRequest
object
8 properties 1 required
UnclaimedDraftCreateEmbeddedWithTemplateRequest
object
30 properties 3 required
UnclaimedDraftCreateResponse
object
2 properties 1 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 properties 1 required
SubUnclaimedDraftSigner
object
3 properties 2 required
SubFormFieldRuleAction
object
4 properties 2 required
SubCC
object
2 properties 2 required
SubSigningOptions
object
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 properties 1 required
SubFormFieldRule
object
4 properties 4 required
SubUnclaimedDraftTemplateSigner
object
3 properties 3 required
SubFormFieldGroup
object
3 properties 3 required
SubFieldOptions
object
This allows the requester to specify field options for a signature request.
1 property 1 required
WarningResponse
object
A list of warnings.
2 properties 2 required
SubAttachment
object
4 properties 2 required
UnclaimedDraftResponse
object
A group of documents that a user can take ownership of via the claim URL.
6 properties
SubEditorOptions
object
This allows the requester to specify editor options when a preparing a document
2 properties
ErrorResponse
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hellosign-unclaimed-draft-api-openapi.yml Raw ↑

Other APIs Dropbox Sign (HelloSign) publishes across the network.

Dropbox Sign (HelloSign) Account API
Dropbox Sign (HelloSign) Api App API
Dropbox Sign (HelloSign) Bulk Send Job API
Dropbox Sign (HelloSign) Embedded API
Dropbox Sign (HelloSign) Fax API
Dropbox Sign (HelloSign) Fax Line API
Dropbox Sign (HelloSign) OAuth API
Dropbox Sign (HelloSign) Report API
Dropbox Sign (HelloSign) Signature Request API
Dropbox Sign (HelloSign) Team API
Dropbox Sign (HelloSign) Template API
Dropbox Sign (HelloSign) Callbacks and Events API
Where this information came from

This is an independent, third-party profile of Dropbox Sign (HelloSign) Unclaimed Draft 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.