Dropbox Sign API subscriptions include team member access to Dropbox Sign on the web. With end-user access, teams can send signature requests using their API key.
If you’re only implementing a non-embedded or embedded signing workflow for one account, we recommend assigning a generic email address to the account, such as support@, sign@, or contract@ to avoid sharing your personal email in your email notifications and on the audit trail for requests connected to the account.
If you’d like to change the email address of the sender via the Dropbox Sign API, you can implement Embedded Requesting. You can add a requester's email address with the requester_email_address parameter, which will change the sender email address that appears on your audit trail included in the signature request and email notification.
Sending a signature request with non-embedded signing
-
When sending a signature request with non-embedded signing from different accounts on your team, the reply-to email address will be the sending account connected to the API Key.
- The sending account will be able to view the completed document on hellosign.com.
- The sending account will be able to use their specific branding and email template, if allowed by their admin.
Sending a signature request with embedded signing
-
When sending a signature request with embedded signing from different accounts on your team, the sender email address that appears on the audit trail will be based on the account connected to the API Key.
-
When you’re implementing embedded signing, you’ll have complete control and flexibility with the entire signature process, which includes generating and sending your own email notifications.
-
When sending a signature request with embedded signing, all team members can use the same API app or you can create an API app for each sender.
-
Team members with API access that are set to a Developer or Admin role can create and use their own API key and API apps on their account. All users on the team share the same API quota.
Sending a signature request with embedded requesting
-
When implementing embedded requesting you can set the sender email address with the requester_email_address parameter. This will reflect on email notifications and the audit trail with your signing workflow.
-
The email address value for the requester_email_address parameter will need to be an email address associated with an account that is part of your team. If the email address is outside of your team, the parameter will be ignored and it will default to the account connected to the API Key.
Setting up team accounts with a Dropbox Sign API subscription
The admin can send invites to add other accounts to the team. Read more about inviting team members and team roles:
Team members who will be sending API requests need to have a developer or administrator team role. Users with a member role don’t have API access.
- After a user accepts the team invite they'll be added to the team. The admin on the master account should share any needed templates with other members on the team.
- Once the additional accounts are added to the team, all team members must go to the Integrations page of their account settings to reveal their API key.
- Use the unique API key to send requests from that user's account.
Comments
0 comments
Article is closed for comments.