> ## Documentation Index
> Fetch the complete documentation index at: https://www.composer.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Dropbox Sign

> Dropbox Sign (Signature & Contract Management): the API posture, publish target and field mapping composerID publishes a decision reference through.

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.

<Info>
  Category: Signature & Contract Management. Coverage status: Specification mapped. Vendor documentation: public developer portal.
</Info>

## Integration path

How composerID connects to this destination, at a glance.

| Step                 | Detail                                                                                                            |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Authentication       | API key over HTTP Basic (key as the username), or an OAuth 2.0 Bearer access token (JWT) for multi-account apps.  |
| composerID publishes | Signature Request: POST /signature\_request/send                                                                  |
| Intent ID lands on   | `signature_request` `metadata.intent_id`, written into the destination record                                     |
| Back-sync            | Webhooks: the destination pushes events; composerID verifies each delivery and lands it on the intent's timeline. |

## Vendor documentation

<Columns cols={2}>
  <Card title="Dropbox Sign API Reference" icon="external-link" href="https://developers.hellosign.com/api/reference/overview/" horizontal />

  <Card title="Authentication" icon="external-link" href="https://developers.hellosign.com/api/reference/authentication/" horizontal />

  <Card title="Developer docs: events & callbacks" icon="external-link" href="https://developers.hellosign.com/docs/" horizontal />

  <Card title="Official OpenAPI spec (GitHub)" icon="external-link" href="https://github.com/hellosign/hellosign-openapi" horizontal />
</Columns>

## API posture

| Aspect         | Detail                                                                                                                                                                                                                                                                 |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Authentication | API key over HTTP Basic (key as the username), or an OAuth 2.0 Bearer access token (JWT) for multi-account apps. Test-mode calls are supported with the API key.                                                                                                       |
| Style          | REST, JSON                                                                                                                                                                                                                                                             |
| Base URL       | [https://api.hellosign.com/v3](https://api.hellosign.com/v3)                                                                                                                                                                                                           |
| Webhooks       | Native callbacks at account or API-app level. Events: signature\_request\_sent, signature\_request\_viewed, signature\_request\_signed, signature\_request\_all\_signed, signature\_request\_declined, signature\_request\_downloadable, signature\_request\_canceled. |
| Events posture | Webhooks                                                                                                                                                                                                                                                               |
| Rate limits    | Per-API-key rate limiting surfaced via X-RateLimit-Limit / X-RateLimit-Remaining / X-Ratelimit-Reset headers; HTTP 429 on exceed: back off and retry.                                                                                                                  |
| Objects        | signature\_request, template, bulk\_send\_job, unclaimed\_draft, team, account, api\_app, report                                                                                                                                                                       |

## 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.

<AccordionGroup>
  <Accordion title="Signature Request" icon="arrow-right-left" description="Send an agreement for signature">
    | Mapping                  | Detail                             |
    | ------------------------ | ---------------------------------- |
    | Canonical to destination | signer, document, subject, message |
    | Target                   | POST /signature\_request/send      |
    | Requirement              | Required                           |
    | Notes                    | Ad-hoc eSignature engagement       |
  </Accordion>

  <Accordion title="Signature Request from Template" icon="arrow-right-left" description="Templated agreement">
    | Mapping                  | Detail                                        |
    | ------------------------ | --------------------------------------------- |
    | Canonical to destination | template\_id, signers\[], custom\_fields      |
    | Target                   | POST /signature\_request/send\_with\_template |
    | Requirement              | Tenant required                               |
    | Notes                    | Reusable templates configured per account     |
  </Accordion>

  <Accordion title="Intent ID correlation" icon="arrow-right-left" description="Carry the Intent ID">
    | Mapping                  | Detail                                                                        |
    | ------------------------ | ----------------------------------------------------------------------------- |
    | Canonical to destination | intent\_id, intent\_version                                                   |
    | Target                   | metadata\[intent\_id] on the signature request                                |
    | Requirement              | Required                                                                      |
    | Notes                    | Dropbox Sign metadata is arbitrary key-value, returned on reads and callbacks |
  </Accordion>

  <Accordion title="Callback event" icon="arrow-right-left" description="Read for back-sync">
    | Mapping                  | Detail                                      |
    | ------------------------ | ------------------------------------------- |
    | Canonical to destination | event\_type, signature\_request\_id, status |
    | Target                   | account / API-app callback\_url             |
    | Requirement              | Required                                    |
    | Notes                    | Used for reconciliation                     |
  </Accordion>
</AccordionGroup>

<Note>
  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.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="How composerID connects" icon="plug-zap" href="/guides/connect">
    The five ways composerID reaches a destination, and the minimum a destination must offer.
  </Card>

  <Card title="Publishing" icon="send" href="/concepts/publishing">
    Plan, preflight and publish: how a decision becomes a valid record in a destination.
  </Card>

  <Card title="All destinations" icon="plug" href="/destinations">
    Every destination composerID documents, with its category and coverage status.
  </Card>
</Columns>