Content & Documents · Integration
Dropbox Sign
Add Dropbox Sign to your product for your customers, and give your AI agents governed access to it.
Dropbox Sign kept the HelloSign API surface after the rebrand, so calls still go to api.hellosign.com/v3 and authenticate with the API key as the HTTP Basic username and an empty password, or with OAuth for accounts you do not own. The core objects are signature requests, templates and the signer roles and custom fields defined on them, and most production integrations send via signature_request/send_with_template rather than uploading a fresh PDF each time. Setting test_mode on a request keeps it free but the resulting documents are watermarked and cannot be promoted to real signatures later, which catches teams who built their whole staging flow that way. Callbacks are the part implementers underestimate: your endpoint has to return the literal string Hello API Event Received or Dropbox Sign treats the delivery as failed and retries, and each payload carries an event_hash you should verify against your API key before trusting it. Downloading the completed document is a separate call that returns binary PDF or ZIP data rather than JSON. fastn holds each customer's own Dropbox Sign credential, refreshes it, and keeps the callback wiring in place so you are not storing keys per tenant yourself.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Dropbox Sign account so contracts go out from their brand and templates, not yours.
Fire a signature request from your app's own workflow, using the customer's template and prefilled custom fields.
Show live signing status in your product by consuming signature request callbacks per tenant.
Pull the completed PDF and its audit trail back into your record once every signer has finished.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which signature requests have been outstanding beyond a threshold and have it send reminders, with every send audited per tenant.
Have an agent prepare a request from an approved template and hold it for human release rather than sending directly.
Let an agent fetch and summarise the signer status and audit trail for a named document on request.
Example prompt
Which Dropbox Sign requests from this month are still waiting on a signer, and who is holding them up?
Set up Dropbox Sign in 4 steps
- 01Enable the Dropbox Sign connector from your fastn dashboard.
- 02Have each customer authorise their own Dropbox Sign account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Dropbox Sign integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Dropbox Sign integration without building it. Your customers connect their own Dropbox Sign account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Dropbox Sign update is not your on-call problem.
- One integration serves your product and your agents. The same governed Dropbox Sign connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Dropbox Sign, across other categories.
Shopify
Stripe
Jira
AsanaDropbox Sign integration FAQ
How do I add a Dropbox Sign integration to my product?
Enable the Dropbox Sign connector in your fastn dashboard, then let each customer authenticate their own Dropbox Sign account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Dropbox Sign client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Dropbox Sign account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Dropbox Sign account and only ever sees their own files, documents and versions. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Dropbox Sign integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which signature requests have been outstanding beyond a threshold and have it send reminders, with every send audited per tenant.
Who maintains the Dropbox Sign integration?
fastn does. When Dropbox Sign changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose permissions does the Dropbox Sign integration run under?
Each customer's own Dropbox Sign grant. Where Dropbox Sign holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Dropbox Sign automatically?
Where Dropbox Sign supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Dropbox Sign integration?
A common starting point: let a customer connect their own Dropbox Sign account so contracts go out from their brand and templates, not yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Dropbox Sign integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Dropbox Sign does not change your per-connector cost. You can start free with 3 connected accounts.
Add Dropbox Sign to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.