...
Snaps in the Coupa Snap Pack use the Coupa OAuth2, and Coupa Dynamic OAuth2 accounts to access the Coupa application. For the OAuth2 account to authorize successfully, create, and configure a connected application corresponding to the account as provided in the key steps.
| Tip |
|---|
Dynamic OAuth2 Account: You must generate a token and have it available when configuring this account. You can generate an Access token using the REST POST Snap or through a cURL command in the Postman application. OAuth2 Account: You must authorize the account to generate a token. |
...
| Info |
|---|
To use an existing application, navigate to the Integrations > Oauth2/OpenID Connect Clients.page. In the search box, specify the application name you want to edit. The details of the searched application displays in the search list. Use the edit option provided under Actions to add more Scopes to the existing app as shown in the image. |
...
Scenario for the Grant Type
Grant Type | Scenario when this Grant type is used | Does it require user consent? | ||
|---|---|---|---|---|
Client credentials | This grant type is used when there are no users involved and for system-to-system integrations. The token is automatically accepted and generated. | No, if the Grant type selected is Client credentials, the user does not require consent, and an HTTPS POST request can be made directly to Coupa.
|
Define Scope
Coupa scopes take the form of service.object.right. For example, core.accounting.read or core.accounting.write.
Navigate to the Scope management page Management page in the Coupa Portal to find the list of scopes and their underlying permissions. Learn more about Scopes available in Coupa.
Select the Scopes you want to include in this API setup.
...
Navigate to the Coupa Snap of your choice and configure the Coupa OAuth2 Account. Refer to Coupa OAuth2 Account for more Account- related information.
Click Authorize. You will be redirected to the login page of Coupa.
Log in to Coupa and accept the permissions. The Access token is populated.
Click Apply after the authorization is successful.
Troubleshooting
Common Errors | Reason | Response |
|---|---|---|
The Client ID is invalid or you must have provided multiple credentials. Failed authentication. | Details of the Client secret provided is incorrect. | Provide correct Client Secret value. |
Invalid Scope | The specified scopes are invalid. | Provide Scopes when creating a client app. |
Failed to validate Account | Details of the parameters provided for endpoint are incorrect. | Ensure that the Account is configured correctly. |
...
Frequently Asked Questions
...