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) Embedded API

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

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

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

2 operations 2 paths 10 schemas 1 GET1 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) Embedded 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 2

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

Embedded 2

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

POST
/embedded/edit_url/{template_id}
Get Embedded Template Edit URL
embeddedEditUrl 1 param body → 2004XX
GET
/embedded/sign_url/{signature_id}
Get Embedded Sign URL
embeddedSignUrl 1 param → 2004XX

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are EmbeddedEditUrlRequest (10 properties), ErrorResponseError (3 properties), WarningResponse (2 properties), EmbeddedSignUrlResponseEmbedded (2 properties). Each schema is shown below with its type and property counts.

ErrorResponse
object
1 property 1 required
ErrorResponseError
object
Contains information about an error that occurred.
3 properties 2 required
EmbeddedEditUrlResponseEmbedded
object
An embedded template object.
2 properties
EmbeddedEditUrlRequest
object
10 properties
SubMergeField
object
2 properties 2 required
EmbeddedSignUrlResponseEmbedded
object
An object that contains necessary information to set up embedded signing.
2 properties
WarningResponse
object
A list of warnings.
2 properties 2 required
EmbeddedSignUrlResponse
object
2 properties 1 required
SubEditorOptions
object
This allows the requester to specify editor options when a preparing a document
2 properties
EmbeddedEditUrlResponse
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hellosign-embedded-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) 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) Unclaimed Draft API
Dropbox Sign (HelloSign) Callbacks and Events API
Where this information came from

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