hsamson | Posts: 11

Complex REST Query

Tuesday, September 10, 2019 at 06:27am
0 votes
I can successfully pull Packages in DRAFT, TRASH, and SENT status, but the Sent Status returns Packages that have been Archived. These Archived Packages represent Packages signed by the Customer but manually signed by the legal department in our Company. Is it possible to have a more complex Query to get Sent Status but not Archived? It would look something like this: query=SENT&query>ARCHIVED&from=0&to=100&lastUpdatedStartDate=2018-01-01&lastUpdatedEndDate=2019-12-31 It is possible for me to iterate through the return data and skip the Archived Packages, but the above Query would be more efficient Thank you
Duo_Liang | Posts: 3776

Reply to: Complex REST Query

Tuesday, September 10, 2019 at 06:47am
0 votes
Hi gyurko, Is the "ARCHIVED" refers to the concept in your system? Because in OneSpan Sign, you can only archive a transaction when it's completed, so a package can't be SENT (not yet completed) and ARCHIVED at the same time. Also, both SENT and ARCHIVED are package statuses in OneSpan Sign, since a package can only be in one status at one time, the package retrieval API shouldn't return you packages with multiple statuses if you specified "query" in parameter. Check the transaction status diagram below: Also, can you share me with a SENT package ID as well as an ARCHIVED package ID, so that I can understand your workflow better. Duo

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

LoginSign Up