Change 403 error code to 404 when requestin g document details
3
votes
Anonymous
shared this idea
-
Just wanted to recommend that the API return a 404 status code when requesting the details for a document that cannot be found. The currently observed behavior is that it returns a 403.
When I get webhook requests for documents, sometimes a user has already deleted the document by the time a request comes in, in which case I'd like to ignore 404 errors. Since it returns 403, it's not as ideal because there could actually be an issue with our API credentials that would also cause that error (which is something we've experienced in the past).