sstickler1286

Listener Not Pulling All Completed Docs

0 votes

We recently put in place a listener that is supposed to pull all completed documents as you would expect. The customer is reporting that there are a large number of documents that didn't get pulled from the OSS cloud. They all were created by the same sender using bulk send. Now some of her bulk send documents did get pulled down of more recent transactions, but older ones did not.

Is there a special condition that needs to be added for bulk send documents? I did grab some sample transaction ID's. 

The account itself is very basic - no sub accounts and the owner created all the senders.

Thanks for the help!

Sam Stickler


Reply to: Listener Not Pulling All Completed Docs

0 votes

Hi Sam,

 

In general, there's nothing special you need to configure in order to monitor the package status change which created by bulk send, through callback listener.

From the troubleshooting's perspective, you can create a support ticket with the sample transaction IDs, asking support team to check in logs and see if the completion notification had been sent to your listener endpoint. So that you could compare against the logs of notification calls recorded at your local.

From the integration's perspective, besides using the callback mechanism, you could also actively polling the package status. For package created by bulk send, a batch ID will be added to the package attribute as "bulkSendBatchUid", which you could loop through the packages and filter by the attribute.

 

Duo
 

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to:

0 votes

We don't see the documentation for the bulkSendbatchUid. When we run a usage report we are only allowed to pull 100 transactions per day per sender. So what do we do when a bulksend has 150 signers and creates 150 transactions? How can we pull that using the REST API? 

Our customer did a bulk send 5/28/2020 that included 154 transactions. We are only able to get 100 of them. 6/4/2020 a bulk send went out for 177 transactions. 7/14 -160 sent via Bulk Send.

 


Reply to: Listener Not Pulling All Completed Docs

0 votes

Hi Sam,

 

"bulkSendbatchUid" is returned when you scheduled the bulk send operation. If you missed to record them, through UI, go find any package created in that batch, build and hit this link: https://{oss_instance}/api/packages/{packageId}, find the batch ID at "data" > "bulkSendbatchUid". Then you can progrommatically list all bulk sent package:
(1)invoke package retrieval API:
GET /api/packages?from=1&to=100&lastUpdatedStartDate={lastUpdatedStartDate}

GET /api/packages?from=101&to=200&lastUpdatedStartDate={lastUpdatedStartDate}

and so on

"lastUpdatedStartDate" should be the sent date, or one day before sent date considering the timezone difference.

(2)loop through package JSONs, filter by "data" > "bulkSendbatchUid" and find matched packages.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off