Skip to main content
This page records how composerID publishes into Dropbox Sign: the vendor’s API posture, the publish target and field mapping, and the documentation each claim rests on. It is for anyone evaluating the connection or building against it. Dropbox Sign (formerly HelloSign) is a self-service eSignature API. composerID sends agreements for signature and rides the Intent ID in the signature request’s arbitrary metadata, which is returned on reads and callbacks for reconciliation.
Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: public developer portal.

​
Integration path

How composerID connects to this destination, at a glance.

​
Vendor documentation

Dropbox Sign API Reference

Authentication

Developer docs: events & callbacks

Official OpenAPI spec (GitHub)

​
API posture

​
Publish target and field mapping

Each object below pairs the canonical intent fields with the destination’s own fields and operations. The mapping is indicative until it is confirmed against a tenant at onboarding.
Metadata keys are arbitrary and echoed on reads and callbacks, so the Intent ID rides natively. Account-level callbacks are self-service; app-level callbacks require an API App. OAuth is only needed for apps acting on behalf of multiple accounts.

​
Next steps

How composerID connects

The five ways composerID reaches a destination, and the minimum a destination must offer.

Publishing

Plan, preflight and publish: how a decision becomes a valid record in a destination.

All destinations

Every destination composerID documents, with its category and coverage status.