Same here. This is frustrating. I’ve contacted RapidAPI and they told me that I have to contact Imgur team. I don’t think I’m going to get a response back.
This fix worked for me: Add the ?client_id=<imgur_client_id> query string parameter to your call to the Imgur upload API (POST /3/image).
That change worked for me both locally and after deploying my app to production. No idea why Imgur made this backward-incompatible change without announcing it to app creators.
Where do you find the client_id in Rapid API? or do you need to signup at api.imgur.com directly? and if the latter how do you tie it to the account here at rapid API? all I see is my client secret. no client_id anywhere here.
I did create a new app directly at api.imgur.com and I got a client_id there, and it seems to work with this API… not sure if that is the correct way.
Now I hope that when they fix their endpoint, it does not break our workaround … 😃
We are seeing the same issue as well. However, we are already sending the clientID in the headers. Do we need to send the same with url parameters now?
I’m still a bit confused because if we hit imgur directly, not through rapidAPI, our uploads are successfull…
I’ve noticed that you don’t necessarily have to add ‘client_id’ query. Appending any random query to the end of the url will fix the issue (?banana will work for example).
For example, ‘https://imgur-apiv3.p.rapidapi.com/3/image?banana’
@Fawesum, we did not use underscores on our client_id=myid and it worked just fine.
@RecipesGenerator , thanks for that info…I don’t know that I want to expose our clientID on the actual request? If anything will work, maybe we should take that route?
I have contacted RapidAPI support and they are convinced it is not their issue. I then contacted Imgur support and they too say it is not their issue…but that they would reach out to RapidAPI. Additionally, RapidAPI is saying that the 404 responses they are seeing are because requests have empty body??
me too, did they change the endpoint?
same here
Same here. This is frustrating. I’ve contacted RapidAPI and they told me that I have to contact Imgur team. I don’t think I’m going to get a response back.
Still can’t upload now. It just happens too frequently.
This fix worked for me: Add the
?client_id=<imgur_client_id>
query string parameter to your call to the Imgur upload API (POST/3/image
).That change worked for me both locally and after deploying my app to production. No idea why Imgur made this backward-incompatible change without announcing it to app creators.
me too
error 404
client_id trick worked for me. But cmon, we are paying for this API…
Thanks grantmcconnaughey
Where do you find the client_id in Rapid API? or do you need to signup at api.imgur.com directly? and if the latter how do you tie it to the account here at rapid API? all I see is my client secret. no client_id anywhere here.
I did create a new app directly at api.imgur.com and I got a client_id there, and it seems to work with this API… not sure if that is the correct way.
Now I hope that when they fix their endpoint, it does not break our workaround … 😃
worked for me too, thanks @grantmcconnaughey
add cliend_id on query string that work for me too, thanks @grantmcconnaughey
Error 404 yep! Only since the past 24h. Why unannounced breaking changes? No announcement? No status update?
Even then: 404 is not the correct http response for this situation lol… why not 500 with a real err that actually helps us?
Feels just … so amateur 😦
EDIT: With this change, you can also ditch the Authorization Client-Id header.
Don’t remove it. Maybe someday you’ll need it again.
What’s going on here imgur?? No word after two full days of downtime??
Client-ID trick did not work for me btw.
@Fawesum, it should work, want to paste here how you are doing it and we can help.
The post URL should be like this: 'https://imgur-apiv3.p.rapidapi.com/3/image?client_id=__your_client_id;
@grantmcconnaughey you saved us! thanks for sharing!
We are seeing the same issue as well. However, we are already sending the clientID in the headers. Do we need to send the same with url parameters now?
I’m still a bit confused because if we hit imgur directly, not through rapidAPI, our uploads are successfull…
@Fawesum, are you still having issues as well?
@sreplanski, thanks for trying to help. Here’s what’s I’m using: ‘https://imgur-apiv3.p.rapidapi.com/3/image?client_id=myid’
Do I need the underlines before the id? Or is there another ID other than the one from Imgur I should be using? It was working like intended.
@onelouderapps, yeah still issues here.
I’ve noticed that you don’t necessarily have to add ‘client_id’ query. Appending any random query to the end of the url will fix the issue (?banana will work for example).
For example, ‘https://imgur-apiv3.p.rapidapi.com/3/image?banana’
@RecipesGenerator , thanks for that info…I don’t know that I want to expose our clientID on the actual request? If anything will work, maybe we should take that route?
I confirm what @RecipesGenerator said, you can put any string in query and it fixes the problem.
Anyone tried to contact the support already ?
I’m getting 400 bad request with anything added to the query string.
I have contacted RapidAPI support and they are convinced it is not their issue. I then contacted Imgur support and they too say it is not their issue…but that they would reach out to RapidAPI. Additionally, RapidAPI is saying that the 404 responses they are seeing are because requests have empty body??
RapidAPI, how on earth have you not fixed this yet, let alone not even responded about it publicly?
we experienced this problem too. worked sunday and stopped working after that. suddenly a few minutes ago it started working without changes
10/22/2021
All,
The issue has been resolved, and confirmed by Quality Assurance as well as from customers such as yourself.
Many thanks,
RapidAPI Product Support Team
Thanks for the fix folks. Have a nice weekend.