MyMedicalRecords Sample Application
This is a sample application showcasing an integration between the Docusign eSignature REST API and an Electronic Medical Records system. This application is open source and all of the code is located in our GitHub repository.
Login Code Flow
Selecting Try the App logs the user in using
JSON Web Token (JWT)
Grant authentication, which is one of the OAuth 2.0 flows that Docusign APIs support. For more information about which OAuth flow your application should use, see the
Developer Center.
Note: Every user of this sample application is logged in using the same account to simplify hosting. However, if you are running this application locally, you must use your own developer account. Code flow:
See the source code for this flow.
Step 1
If the user hasn't yet provided consent for the application to impersonate them, create the consent URI and have the user provide consent; then obtain the JWT token with the scopes that the application requires.
Step 2
Using the JWT, obtain and store the access token that will be used to make future API calls.
Step 3
Using the access token, use the /oauth/userinfo API endpoint to get and store the user's base URI and account ID, which are also needed to make API calls.
Note: Every user of this sample application is logged in using the same account to simplify hosting. However, if you are running this application locally, you must use your own developer account. Code flow:
See the source code for this flow.
Step 1
If the user hasn't yet provided consent for the application to impersonate them, create the consent URI and have the user provide consent; then obtain the JWT token with the scopes that the application requires.
Step 2
Using the JWT, obtain and store the access token that will be used to make future API calls.
Step 3
Using the access token, use the /oauth/userinfo API endpoint to get and store the user's base URI and account ID, which are also needed to make API calls.
© 2024 Docusign Inc.