Authentication
Docusign uses OAuth 2.0 to secure your API requests. Using OAuth, your app requests access and performs actions, such as requesting a signature, on behalf of one of your users. Before you can make calls to the Docusign eSignature API, you must authenticate and obtain an access token. This access token, which proves your app’s identity and authorization, must be submitted alongside each request to the Docusign eSignature.
You will need to create an Account record in the fmESignature Link file to link to your chosen Docusign account (Sandbox or Production) and then authenticate with the Docusign API to obtain an access token.
fmESignature Link (Docusign Edition) v2 supports the following Docusign authentication options:
- Authorization Code Grant OAuth Flow
- JWT Grant OAuth Flow
The Authorization Code Grant OAuth Flow uses a FileMaker Web Viewer for a single user to authenticate with Docusign. The user that authenticates is then used as the "sender" of the Docusign envelopes. The access token can be refreshed automatically by the fmESignature Link file.
The JWT Grant OAuth Flow does not require a user to authenticate using a FileMaker Web Viewer and can also be used with the 'Send On Behalf Of' (SOBO) feature where you can dynamically set the sender of the Docusign envelope to one of your Docusign account users (once they have granted consent.
Both authentication methods require the user (or users if you're using the Send On Behalf Of another user feature) to first grant consent to allow your Docusign app/integration to perform tasks on behalf of the user.
We have separate guides for authenticating using both options here:
We also have some short videos demonstrating the setup of each authentication method that you can follow along with – check out the videos page to view these videos.
You can get more information about authenticating with the Docusign eSignature API here:
Docusign Authentication Overview