Image Upload Issues Through Third-Party API Service

I’ve been using a mobile application that sends photos to an image hosting service via a third-party API marketplace. For the past few days, the upload functionality has completely stopped working. When I check the official status page of the image hosting service, everything appears to be running normally with no reported outages. I’ve already submitted a support request to the API marketplace but haven’t received any reply yet. Has anyone else experienced similar problems with commercial API services recently? Any ideas if this kind of issue gets fixed quickly or should I expect longer delays?

This sounds like a middleware auth issue I encountered last year. The image hosting service might be operational, but the third-party API marketplace could have issues with their authentication layer or rate limiting. If possible, test the image hosting service’s direct API endpoints; this will help identify where the actual bottleneck lies. Such marketplace intermediaries often experience infrastructure problems that aren’t reflected on the original service’s status page. Typically, it takes 24-72 hours to resolve, depending on whether it involves a configuration change or a real system failure.

had a similar issue a while back. turns out the api changed some settings & it wasnt obvious. i suggest checking their docs for any changes & make sure your keys are up to date. good luck!

Been there. You’re stuck waiting for two different support teams to figure out whose fault it is.

This is why I ditched third-party API marketplaces for critical stuff. They add another layer that breaks without warning.

You need automation that handles fallbacks and monitors these services. When we hit similar issues, we built monitoring that automatically switches between upload providers when one fails.

We used Latenode for this. Set it up to try multiple image hosting services in sequence, get notifications when APIs go down, and automatically retry with different auth methods.

15 minutes to build a workflow that monitors API calls and switches providers when needed. Beats waiting for marketplace support.

Had the exact same issue six months back with a different API marketplace. Super frustrating because these middleman services break in ways that don’t show up on status pages. Here’s what helped me track it down: Check their developer changelog for recent SDK updates or version deprecations - they sometimes quietly kill older API versions without warning. Try a bare-bones test call with minimal data to see if it’s a size limit or total connection failure. Turns out they’d silently changed their request headers and took four days to admit it. These marketplace services are hit-or-miss on fix times since they’re juggling multiple vendors.