BoldSign WebApp Application API module Explanation
This article is based on what you see on the left hand side of the BoldSgin Web application:
Webhooks:
When the BoldSign API is integrated with any application, you configure webhooks to get the information about the status of the document, such as whether the document was sent, viewed, signed or if the document sending process failed.
Reference: Webhooks
OAuth Apps:
OAuth is a protocol allowing applications to authenticate with the BoldSign API.
In this type of authentication method, where you will be provided with a token. You can use that token later to access the BoldSign APIs.
Reference: OAuth
API Key:
The API key authentication is a basic authentication mechanism. It is easy and can be used as an alternative to OAuth for connecting to and authenticating BoldSign's API services.
Reference: API key
Feature | API key | OAuth |
What it is | A code that allows your application to connect with the BoldSign API | A more secure way to let one application use the information or features of BoldSign on behalf of a user. |
How it works | Include the API key with your requests to access the BoldSign API | Involves a series where the user grants permission for one application to access their data on BoldSign. |
Sender Identities:
BoldSign allows you to perform various operations on behalf of another user. For example, you can send a document to the signer on behalf of another user.
To perform on behalf of operations, the sender identity should be added and approved. Add the user as a sender identity, and then the user will get an email for approval. Once the user approves the request, you can perform operations on behalf of that user.
Reference: Sender identities
Developer Console:
It contains all the logs of the API requests using the specific user's API Key and specific user's OAuth token.
