Moonwalker | Posts: 1

How do I tell if delete package failed?

Friday, March 17, 2017 at 01:40pm
0 votes
When I delete a package with: 
DELETE /packages/{packageId}
It returns status code 200, with no response payload. I can call this repeatedly, and it always gives the same response, even when it is already deleted. If DELETE fails - what response is given? How can I be sure that DELETE is actually deleting the package, short of: 
GET /packages/{packageId}
after every delete.
mwilliams | Posts: 957

Reply to: How do I tell if delete package failed?

Tuesday, March 21, 2017 at 06:35am
0 votes
If you're getting a 200 response, I think you can be assured it's deleted. The reason you continue to get a 200 response upon subsequent calls is likely because there is probably still a record of the package within the database that only contains the package ID and no other information besides a status of DELETED. So, a 200 request again would be confirming that the package is deleted. If you wanted to do testing to try to pull the package afterwards for error checking, that would probably be your only other method. A failure to delete would likely only happen if your request didn't reach eSignLive and in that case, you'd not receive the 200 response. If I find anything different than what I've said here, I will update this thread.

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