FInky | Posts: 9

Cannot view Package when getting a package using the owner API Key

0 votes

Hi,

 

I been trying to get status' for my packages, but i am hitting a wall.

I am running the following using the owner API Key and attempting to retrieve packages that are owned by a separate sender:

/api/packages/:packageId

eslClient.GetPackage(new PackageId(id))

 

I can run successfully when the Package status of the package im trying to get is is Sent or Completed.

I get error.forbidden.cannotViewPkg or error.forbidden.packageExpired when the package status are expired and opted out, etc.

All i want to do is retrieve the status of the package. Is anyone able to explain why this is happening and how i can handle it??

I'm having difficulty finding documentation for this. 

thanks,

 

 


Duo_Liang | Posts: 3776

Reply to: Cannot view Package when getting a package using the owner API Key

0 votes

Hi FInky,

 

For a quick workaround, you can try using below SDK function to retrieve package status and see if this solved the issue:

SigningStatus pkgStatus = eslClient.GetSigningStatus(packageId, null, null);

However, it doesn't sound expected if the owner API Key can't access an expired or opted-out package created by a separate sender. If the issue still exists, you can submit a support ticket to [email protected] with a failing package ID, your account owner's email so that we can take a closer look at it.

 

TIP: if you are frequently actively polling, it's always suggested to set up a callback listener monitoring the package status change.

 

Duo


FInky | Posts: 9

Reply to:

0 votes

Thank you for the reply, I have attempted to use SigningStatus pkgStatus = eslClient.GetSigningStatus(packageId, null, null); and got the same results. I may end up using it to reduce bandwidth when polling at the very least.

I will submit a ticket with support so they can take a closer look as it seems that another account that we have does not have this issue.

As for the tip, yes we are using callbacks 99% of the time, but we need something to poll statuses just in the event that callbacks fail to reach us.


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