> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://developers.hellosign.com/docs/guides/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.hellosign.com/_mcp/server. # Guides > Technical documentation for the Dropbox Sign API. ## Docs - [Events and Callbacks](https://developers.hellosign.com/docs/guides/events-and-callbacks.md): The Dropbox Sign API allows you automate your signature flows. To find out how to use Dropbox Sign Events, click here. - [Walkthrough](https://developers.hellosign.com/docs/guides/events-and-callbacks/walkthrough.md): Click here to learn about Dropbox Sign Events how to use webhooks to automate your integration with the Dropbox Sign API. - [Overview](https://developers.hellosign.com/docs/guides/o-auth/overview.md): Keep your users data safe. Click here to learn about using OAuth in your Dropbox Sign API integrations. - [Walkthrough](https://developers.hellosign.com/docs/guides/o-auth/walkthrough.md): OAuth allows you to send signature requests and call the Dropbox Sign API on behalf of your users. Click here to learn about Dropbox Sign's OAuth flows. - [Overview](https://developers.hellosign.com/docs/guides/app-approval/overview.md): Customers using advanced features of the Dropbox Sign API need their apps approved for production. To learn about our app approval process, click here. - [Self Publish](https://developers.hellosign.com/docs/guides/app-approval/self-publish.md): Overview of new process for Self-Publishing your API Apps. - [Submitting](https://developers.hellosign.com/docs/guides/app-approval/submitting.md): App approval is required for Dropbox Sign API customers using Embedded Workflows or OAuth. To learn how to submit your app for approval, click here. - [Approved](https://developers.hellosign.com/docs/guides/app-approval/approved.md): After a Dropbox Sign API app is approved, questions arise about best practices for moving into production. To review tips and frequently asked questions, click here. - [Signer Auth](https://developers.hellosign.com/docs/guides/app-approval/signer-auth.md): Click here to review our official guidance around signer authentication to ensure your documents and signatures stay legally binding. - [API Dashboard](https://developers.hellosign.com/docs/guides/api-dashboard.md): Learn about Dropbox Sign's API Dashboard and how it's used to monitor the health of your integration, troubleshoot, and analyze API activity. - [Embedded Saved Signatures](https://developers.hellosign.com/docs/guides/api-settings.md) - [Overview](https://developers.hellosign.com/docs/guides/pre-filled-document-data/overview.md): Adding your data to your document for a signature request. - [Templates](https://developers.hellosign.com/docs/guides/pre-filled-document-data/templates.md): Adding your data to your document for a signature request using Templates. - [Text Tags](https://developers.hellosign.com/docs/guides/pre-filled-document-data/text-tags.md): Adding your data to your document for a signature request using Text Tags. - [Form Fields](https://developers.hellosign.com/docs/guides/pre-filled-document-data/form-fields.md): Adding your data to your document for a signature request using Form Fields Per Document. - [SMS Tools](https://developers.hellosign.com/docs/guides/sms-tools.md): Find out how to use SMS Tools for both authentication and delivery of signature requests. - [Overview](https://developers.hellosign.com/docs/guides/e-id-signing/overview.md): eID allows you to authenticate users with eID processes provided by organizations in the European Union. Click here to learn more about eID. - [Adding eID](https://developers.hellosign.com/docs/guides/e-id-signing/adding-e-id.md): eID allows you to authenticate users with eID processes provided by organizations in the European Union. Click here to learn more about how to add eID authentication to your flows. - [Using eID](https://developers.hellosign.com/docs/guides/e-id-signing/using-e-id.md): Technical documentation for the Dropbox Sign API. - [NOM 151 Overview](https://developers.hellosign.com/docs/guides/signature-types/nom-151-overview.md): Overview of NOM 151 signature type. - [Implementation](https://developers.hellosign.com/docs/guides/signature-types/implementation.md): Steps to sign with NOM 151 signature type. - [Admin Console Reports](https://developers.hellosign.com/docs/guides/reports.md): Learn about the Reports API and how to use it. - [Fax](https://developers.hellosign.com/docs/guides/fax.md): A guide to assist customers migrating from v1 to v3 of the Fax API ## API Docs - Events and Callbacks Reference > Events [Account Callbacks](https://developers.hellosign.com/docs/guides/events-and-callbacks/events-and-callbacks-reference/events/account-update-event-callback.md) - Events and Callbacks Reference > Events [App Callbacks](https://developers.hellosign.com/docs/guides/events-and-callbacks/events-and-callbacks-reference/events/api-app-create-event-callback.md) - OAuth [OAuth Token Generate](https://developers.hellosign.com/docs/guides/o-auth/token-generate.md) - OAuth [OAuth Token Refresh](https://developers.hellosign.com/docs/guides/o-auth/token-refresh.md) ## OpenAPI Specification The raw OpenAPI 3.1 specification for this API is available at: - [OpenAPI JSON](https://developers.hellosign.com/docs/guides/openapi.json) - [OpenAPI YAML](https://developers.hellosign.com/docs/guides/openapi.yaml)