Creating a webhook
Learn how to create webhooks from the Digital River Dashboard.
Last updated
Learn how to create webhooks from the Digital River Dashboard.
Last updated
You can create a webhook to send notifications in five easy steps.
To receive webhook notifications from Digital River, you must open your firewall to all the IP addresses listed in the Digital River safelist.
You can send webhook data as JSON in the POST request body. The POST request body contains the complete event details, which you can use after parsing the JSON into an Event object.
When creating a webhook from the Digital River Dashboard, you need to determine the type of authentication you want to use (either none, basic, or OAuth) and add the endpoint.
From the Webhooks page, click Create Webhook. Note: An event triggers a webhook to notify you. The Create webhook page lists and describes the available events.
Toggle Disabled to Enabled.
If required, select the API version you want to associate with events from the API Version dropdown list. By default, the confidential key version is selected.
Click HTTP for the Authentication method and complete the Username and Password fields.
Enter the URL for the endpoint in the Endpoint URL field.
Select the checkbox next to each event you want to associate with the endpoint, or select the Events Selected checkbox to select all events. At least one event type must be selected.
Scroll down and click Save.
From the Webhooks page, click Create Webhook.
Toggle Disabled to Enabled.
If required, select the API version you want to associate with events from the API Version dropdown list. By default, the confidential key version is selected.
Click OAuth for the Authentication method.
Select one of the following options from the Grant type drop-down list and complete the associated fields.
Select the checkbox next to each event you want to associate with the endpoint or select the Events Selected checkbox to select all events. At least one event type must be selected.
Scroll down and click Save.
Your endpoint must return a 2xx HTTP status code to acknowledge the receipt of an event. If it fails to acknowledge events for several days, it will be disabled.
If Digital River receives any response codes outside this range, it indicates that you did not receive the event. For example, Digital River treats a URL redirection as a failure.
Once you have verified your endpoint can receive, acknowledge, and handle events correctly:
Toggle from Test to Production in the Dashboard.
Go through the same configuration steps again to configure an endpoint for your production integration.
The signing token is unique to each data mode if you're using the same endpoint for both test and production modes.
To verify signatures, you must retrieve your endpoint's token from the Dashboard's Webhook settings. To see an endpoint's token:
From the Webhooks page on the Dashboard, click the Reveal secret token associated with the endpoint you want to verify.
Provide your credentials and click Authenticate. The Token field under Signing secret will display the token.
See Digital River signature for more information.
Password
Client credentials
