- KB0014510: Resend a failed callback notification

Introduction:

When a callback notification delivery fails, the package sender by default should receive a callback failure notification email coming from OneSpan to inform them, however, OneSpan will not retrigger nor resend those notifications emails as the client can retrigger those failed notifications.

Technical details:

To resend a callback, you will need to send an API call as following:

HTTP Request

POST / {your listener URL}

HTTP Headers:

Accept: application/json

Content type: application/json

Authorization: Basic {Your callback authorization key}

Request payload: The payload in the email callback failure.

Practical Example Using Postman:

Assuming that we need to resend the following failed callback for “package activate” event using "Postman":

Callback failure email:

{"@class":"com.silanis.esl.packages.event.ESLProcessEvent","name":"PACKAGE_ACTIVATE","sessionUser":"8QS1yr3q8DEZ","packageId":"xT9OeZ-j2jIynQBaLeLdgp9CtZk=","message":null,"documentId":null,"createdDate":"2019-10-09T19:32:12.255Z"}

And we have the following listener for instance, configured in the OneSpan sign account where the callback failed:

https://fathomless-castle-26131.herokuapp.com/eslNotification

Using Postman, you can simply resend the failed callback:

POST / https://fathomless-castle-26131.herokuapp.com/eslNotification

Accept: application/json

Content type: application/json

Authorization: Basic {Your callback authorization key}

Please note that if you don’t have a callback authorization key, you won’t need the authorization header.

And here is the payload:

Simply use the payload in your email callback failure notification between the curly brackets:

Once you click send, the above failed callback will be re-triggered.