In the previous section, you learned to create an application. Now, you must configure OAuth for your application so that the client-side applications that you build can invoke the Sign APIs.
Click View/Edit to get the Application ID and Secret
Note down the app's Application ID and Secret. You will be using this information to issue access tokens in the Adobe Sign API.
Click Configure OAuth for Application to enable scopes
Remember to limit the scopes that you intend to request through OAuth. The scope denotes the extent of permission that your users will have on your account.
The following modifiers are available:
|self||Perform the specified action on behalf of the authorizing user. This is the default - i.e. "agreement_send:self" is the same scope as "agreement_send"|
|group||Perform the specified action on behalf of any user in the same group as the authorizing user. The authorizing user must be a group admin in order to grant this scope, and must have the Business or Enterprise edition of Adobe Sign.|
|account||Perform the specified action on behalf of any user in the same account as the authorizing user. The authorizing user must be an account admin in order to grant this scope, and must have the Business or Enterprise edition of Adobe Sign.|
Now, you are all set to invoke the Sign APIs from your client-side apps. Note that OAuth is widely used by developers to authorize API access. Adobe Sign's implementation complies with the OAuth 2.0 specification.
The OAuth process requires users of your apps to grant permissions before invoking any API.
IMPORTANT: Before you begin using the Sign APIs, read Using OAuth to Access Adobe Sign APIs.