We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
batch API endpoints can't return errors?
I am trying to inderstand the philosophy of the batch APIs (copy_batch, delete_batch, move_batch). I understand the general flow, but I am confused by the modality of these operations being able to ...
Greg-DB
Dropbox Community Moderator
Dropbox Community ModeratorThat's correct, the batch endpoints don't return errors themselves. These would only be returned by the check endpoints. I can't speak to why it's constructed this way, but I suspect it's just that the batch endpoints don't use the same mechanism as the non-batch endpoints and the error information isn't available at the time of the first call.
I get that, and that would make total sense if these API endpoints didn't also have the ability to fully complete and return results without batching.
I guess my point is, if there is some set of circumstances that make the backend say "hey, this one looks easy, I don't need to batch it, I'll just do this real quick and return the result", OK, fine. But if you encounter an error in that case, now all of the sudden that's something that requires a /check to get the completion (failure)?
I'd prefer they not even have the non-batch shortcut return mode and always just made you get the completion (or error) from /check. That would make a lot more sense and make the client code path a lot simpler.
- Greg-DBThanks for the feedback! I don't know what the specific conditions may be, but I'll send this feedback along to see if we can simplify this in the future.
About Dropbox API Support & Feedback
Find help with the Dropbox API from other developers.
