Callback for specific package

Hi Ilya,

Unfortunately, you can only specify one callback configuration per account. If your organization has different systems leveraging OneSpan Sign service, you'd either sign up two OneSpan Sign accounts, or implement a middleware triaging and forwarding the callbacks - by adding additional data to the package JSON, your middleware could tell the which system sends this package.

In the near future, subaccount feature could mitigate this pain point by enabling an organization to create child accounts within the organization's master account. However, for the time being, enabling subaccount feature could potentially impact your existing integration.

Duo

Hi Duo,

Thanks for the fast response.

Yes, I was leaning towards a triaging approach as I was guessing the callback may not be configurable for a single account. Your link to "additional data" is not accessible as it seems to link to a staging environment for the community. Can you please resend the link to that information? This extra data in the package should definitely help to tell which was the source system that initiated the package.

Thanks in advance,

Ilya

Hi IIya,

Here's the link:

https://community.onespan.com/documentation/onespan-sign/guides/feature-guides/developer/custom-transaction-data

Duo

Thanks Duo.

Can you point me to any sample event response JSON that gets sent to an end point upon completion of a specific package signing that would include the custom data (pass through data) in the response?

Thanks once again.

Ilya

Hi IIya,

Custom data won't be directly included in the response JSON, see below. You need to additionally invoke package retrieval API - GET /api/packages/{packageId}

{
  "@class": "com.silanis.esl.packages.event.ESLProcessEvent",
  "name": "PACKAGE_COMPLETE",
  "sessionUser": "0787be84-f095-44c7-ba00-787093df86fc",
  "packageId": "KHiRfOXgKK0gpVWwwpFOSNy6o34=",
  "message": null,
  "documentId": null
}

Duo