Welcome to the Dropbox Sign API Community!
Whether you're building your first integration or fine-tuning an existing workflow, you’ve come to the right place, the Community Forum! To aid in your search for answers, we’ve put together a guide that brings together some of the most commonly referenced Dropbox Sign API features in one place. Keep it bookmarked for quick access to documentation, implementation guides, and best practices as you build.
1 Callbacks
Callbacks are the most reliable way to stay informed about signature request activity. Rather than polling the API for status updates, configure callback URLs to automatically receive notifications when events such as signing, declining, or completion occur. This allows your application to respond in real time and keeps your workflows efficient.
Common errors our experts see:
- Typically missing the correct response (200 HTTP code and text “Hello API event received”.
- Ensure these are set up at the appropriate level (Account vs. App)
Learn more:
2 Form Fields
Form fields determine where signers enter information and how documents are completed. Whether you're defining fields through the API or using templates, taking time to correctly configure field types, signer assignments, validation, and required fields helps ensure a smooth signing experience.
Common errors our experts see:
- Outside of the the x and y coordinate boundaries
3 Email Delivery
Dropbox Sign manages email notifications throughout the signature process, including invitations, reminders, and completion notifications. If expected emails aren't arriving, it's often helpful to verify recipient email addresses, review spam or filtering policies, and confirm your account or test mode configuration and review your email notification settings before troubleshooting further. Remember, embedded signing API workflows do not send email notifications like our non-embedded and web app workflows.
Learn more:
4 Embedded Signing
Embedded signing allows your users to complete signature requests directly within your application, creating a seamless experience without redirecting them to Dropbox Sign. When implementing embedded signing, be sure to generate the embedded signing URL correctly and use the appropriate client-side library to launch the signing session within an iFrame on your site.. Note that this requires a Standard API plan or higher to send requests in production, but can be tested using test_mode parameter. Additionally, our embedded testing tool allows you to simulate using the frontend to open an iFrame for testing
Common errors our experts see:
- signature_id vs signature_request_id
- sign_url time to live / one time use
- Invalid requests (resend)
- 429s - exponential backoff retries
Learn more:
5 Text Tags
Text tags make it easy to dynamically place signature and form fields within documents by inserting specially formatted text before uploading the file. They're especially useful for automated document generation workflows and can significantly reduce the need for manual field placement.
Common errors our experts see:
- Improper tag syntax
- Text being read as tags, when they aren’t
Learn more:
More Developer Resources
Looking for something else? The full Dropbox Sign developer documentation includes API references, SDKs, walkthroughs, authentication guidance, and implementation examples to help you get the most from your integration. And if ever you don't find what you're need, please start a discussion in the Developer Forum! Our team, and the community at large is always happy to help!
A Few Community Tips
- Search around in case anyone’s also posted about what you’re looking for.
- Share your workflows since the best ideas often come from other customers.
- Include screenshots when asking for help or reporting errors so the team can help without pestering you for too much information. Be mindful of PII!
- Submit your ideas by leaving a suggestion for our product team on the Ideas Board.
