
The Dropbox Sign API allows you to automate document workflows with ease.
By integrating the API into your existing systems, you can reduce manual tasks and increase productivity.
With the API, you can send documents for signature, track progress, and receive notifications, all from a single platform.
This integration can be especially helpful for businesses with multiple teams or locations, as it provides a centralized solution for document management.
Security Measures
Rotating API keys is a good security practice that helps protect your users. This is achieved by periodically creating new API keys and removing old ones.
The Dropbox Sign API supports the creation of multiple API keys, making it easy to implement this security measure.
Access Token
An access token is a base64 encoded string used in the OAuth flow.
The security scheme type for access tokens is HTTP, specifically using the Basic HTTP Authorization Scheme.
The permissions applied to access tokens are controlled by the access scopes set in your API app, which are shown to the end-user completing an OAuth flow.
Please refer to the OAuth Walkthrough for additional information on how to manage access scopes and implement the OAuth flow securely.
Rotating Keys
Rotating Keys is an essential security practice that helps protect your users.
Rotating API keys is a good security practice that helps protect your users. Periodically rotating the API key used in your integration is a good security practice that helps protect your users.
To rotate API keys, you'll need to create multiple API keys. The Dropbox Sign API supports the creation of multiple API keys.
Here's a step-by-step guide to rotating API keys:
1. Go to your API Settings page and look for the API key section.
2. Press the Generate key button above the API key table.
3. Name the new key and press Generate key.
4. The new key appears on the API key table, and your previous key is still designated as the "Primary Key". Don't change primary key yet.
If your app uses Events and Callbacks, you'll need to update your event hash verification to use the new API key. This is to avoid a disruption in service.
For another approach, see: Do I Need Dropbox
Here's what you need to do:
- Update your code so API calls to Dropbox Sign use the new key.
- Verify you updated your event verification and click Make primary.
Once you've completed these steps, interact with the Dropbox Sign features as a user would. Verify two behaviors:
* Once confirmed, the end result is that your API keys are rotated successfully.
API Overview
The Dropbox Sign API is a space for developers to get information, share ideas, and receive support. It's a community-driven platform where developers can collaborate and learn from each other.
The API is specifically designed for Dropbox Sign, which is a tool for electronic signatures and document management. It's a powerful resource for developers looking to integrate e-signature capabilities into their applications.
Developers can use the Dropbox Sign API to get information on the API itself, as well as share ideas and receive support from other developers. This makes it an excellent resource for those looking to get started with e-signatures.
By using the Dropbox Sign API, developers can create custom integrations that meet their specific needs. This is especially useful for businesses that require tailored e-signature solutions.
Take a look at this: Dropbox Sign Support
Parsing and Matching
To assign a signer to a Text Tag, you must specify the signer index, which is represented by the number N in "signerN". This index must match the number of signers configured in the delivery configuration.
The number of signers configured in the document using text tags must match the number of signers configured in the delivery. For example, if you have two Text Tags with signer indices 1 and 2, you must configure two signers in the delivery configuration.
Here's an example of how to specify the signer index in a Text Tag: $$[sig|req|signer1|OptionalLabel|OptionalID]/$/$$$[initial|req|signer2|OptionalLabel|OptionalID]/$/$
Text Tag Parsing
To enable Text Tags, you need to check the box labeled "Use Text Tags". This will convert your tags into UI components that users can interact with.
You can hide the tags from the user by changing the text color to match the background, such as white on white. Alternatively, you can set "Hide Text Tags", but it's not recommended because it can lead to unwanted clipping.
To begin and end a tag, use square brackets [ ] in your document. Within the square brackets, use the pipe character | to divide the parts of the tag.
The first part of the tag is the type, and the second part indicates if it is required or not. The third part indicates which signer in the list of signers needs to complete the field. The last two parts are optional and are for setting a label and unique ID.
For example, a tag might look like this: [text|noreq|signer1|Label|UniqueId]. The types of fields available are the same as when you create a template, and the only valid values for field requirement are "req" and "noreq".
Consider reading: How to Use Dropbox Sign
Matching
Matching is a crucial step in the signing process. You must assign a Text Tag to a specific signer, represented by the number N in "signerN".
The number of signers configured in the document using text tags must match the number of signers configured in the delivery. This ensures that the right people receive the right documents.
You can specify that a signer is required to sign, as in "signer1 is required to sign". This is denoted by the "req" keyword in the Text Tag.
For example, if you have two Text Tags:$[sig|req|signer1|OptionalLabel|OptionalID]/$/$$[initial|req|signer2|OptionalLabel|OptionalID]/$/$, you have specified that signer1 is required to sign and signer2 is required to initial.
The number of signers configured in the document using text tags must match the number of signers configured in the delivery. This is a critical step to ensure that the signing process goes smoothly.
Featured Images: pexels.com