Dropbox Sign API

Name: Dropbox Sign API
Brand: Dropbox Sign API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCollaborationbasic, bearer73 EndpointsREST

Install Jentic One Beta

Connect the Dropbox Sign API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dropbox Sign API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Dropbox Sign API.

Send a document for electronic signature via POST /signature_request/send

Create reusable templates and dispatch them with POST /signature_request/send_with_template

Issue embedded signing and template editing URLs via /embedded/sign_url and /embedded/edit_url

GET STARTED

Start building with Dropbox Sign API

Explore with Jentic

View OpenAPI Document

For Agents

Send documents for e-signature, manage templates, and embed signing flows with Dropbox Sign. Supports bulk dispatch, embedded signatures, and OAuth-scoped agent access.

Use for: I need to send a contract for electronic signature, Send the same NDA to 200 candidates in one batch, Generate an embedded signing URL for a customer, Retrieve the signed PDF after a signature request completes

Not supported: Does not handle file storage, document collaboration, or notarization - use for electronic signature workflows only.

Use Cases

Patterns agents use Dropbox Sign API for, with concrete tasks.

★ Sales Contract Dispatch

Send sales contracts and order forms for signature directly from a CRM or deal-room workflow. POST /signature_request/send accepts the document, signers, and field placement, then issues an email request and returns a signature_request_id the agent can poll. Round-trip from draft to fully signed PDF typically takes minutes once signers respond.

POST /signature_request/send with a PDF, two signer emails, and required fields, then poll GET /signature_request/{id} until status is signed and download the file via GET /signature_request/files/{id}

Embedded Signing in a Web App

Embed a Dropbox Sign signing flow inside a web product so users sign without leaving the app. The agent calls /embedded/sign_url to mint a single-use signing URL after creating a request with embedded=true, then the front-end loads the URL in the Dropbox Sign iframe. This avoids handling document storage and signature legality in your own stack.

Create an embedded signature request via POST /signature_request/create_embedded, then call GET /embedded/sign_url/{signature_id} and return the URL to the front-end

Bulk Signature Dispatch from a Template

Send the same templated document to hundreds or thousands of recipients in a single bulk operation, useful for HR onboarding waves or compliance attestations. POST /signature_request/bulk_send_with_template accepts a template_id and a CSV-style signer list and creates a bulk_send_job whose status the agent polls via /bulk_send_job/{id}.

POST /signature_request/bulk_send_with_template with template_id and 500 signer rows, then poll GET /bulk_send_job/{bulk_send_job_id} until completed

Agent-Driven Signature Workflows via Jentic

Wire Dropbox Sign into agent workflows that draft, dispatch, and reconcile signed documents. Through Jentic the agent searches by intent, loads the schema for /signature_request/send, and executes without scraping HelloSign's reference, which keeps the integration loop short and keeps API keys out of agent context.

Search Jentic for 'send a document for signature', load the Dropbox Sign /signature_request/send schema, and execute with signer details supplied by the parent workflow

Key Endpoints

73 endpoints — jentic publishes the only available openapi specification for dropbox sign api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/signature_request/send

Send a document for signature

GET

/signature_request/{signature_request_id}

Get a signature request

POST

/signature_request/send_with_template

Send a signature request from a template

GET

/embedded/sign_url/{signature_id}

Get an embedded sign URL

POST

/embedded/edit_url/{template_id}

Get an embedded template edit URL

GET

/bulk_send_job/{bulk_send_job_id}

Get bulk send job status

GET

/account

Get account details

POST

/signature_request/send

Send a document for signature

GET

/signature_request/{signature_request_id}

Get a signature request

POST

/signature_request/send_with_template

Send a signature request from a template

GET

/embedded/sign_url/{signature_id}

Get an embedded sign URL

POST

/embedded/edit_url/{template_id}

Get an embedded template edit URL

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Dropbox Sign API key or OAuth bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a document for signature' or 'check signature status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the HelloSign reference.

Time to first call

FAQs

Specific to using Dropbox Sign API through Jentic.

Why is there no official OpenAPI spec for Dropbox Sign API?

Dropbox does not publish an OpenAPI specification for Dropbox Sign that matches the live v3 surface. Jentic generates and maintains this spec so that AI agents and developers can call Dropbox Sign API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Dropbox Sign API use?

The API accepts HTTP Basic with an API key as the username, or OAuth 2.0 bearer tokens for end-user-scoped access. Through Jentic the credential is stored in the vault and injected at execution, so it never enters the agent prompt.

Can I send a document for signature with the Dropbox Sign API?

Yes. POST /signature_request/send accepts the document, signers, and field placement and returns a signature_request_id you can poll via GET /signature_request/{signature_request_id}.

What are the rate limits for the Dropbox Sign API?

Limits are not declared in the OpenAPI spec. Dropbox Sign documents account-level quotas in the dashboard; have your agent retry on HTTP 429 with exponential backoff.

How do I run a bulk signature dispatch through Jentic?

Search Jentic for 'bulk send signature requests', load the schema for POST /signature_request/bulk_send_with_template, and execute with a template_id and signer list. Then poll GET /bulk_send_job/{bulk_send_job_id} for completion. Install with pip install jentic.

Can I embed signing inside my own application?

Yes. Create an embedded request, then call GET /embedded/sign_url/{signature_id} to mint a single-use signing URL that loads in the Dropbox Sign iframe.

Can I limit what my agent is allowed to do with the Dropbox Sign API?

Yes. Because you self-host Jentic One, your own rules decide which Dropbox Sign operations and credentials the agent may use, so you can allow only the endpoints a task needs, such as sending a request from a template or checking signature status via GET /signature_request/{signature_request_id}. Since the request or template is identified in the request body, the agent can act only on the operations you permit. Broader actions like bulk dispatch through POST /signature_request/bulk_send_with_template stay off unless you explicitly add them.

Dropbox Sign API

Connect the Dropbox Sign API to your agent

Capabilities

Start building with Dropbox Sign API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs