API issues

[ufoptg]

Currently im getting the response

{"Response":"False","Error":"Invalid API key!"}

This is happening with my pateron API key and when i tried to create a new API key i still get the same issue...

[gouravp11]

Happening with a non patreon too

[jozaco]

Same here, with a free account. After validating the apikey, the requests sent return invalid api key.

[zlemenio]

same here as well.

[izkreny]

It is working for me (Croatia, Europe), just got my API key yesterday. 😕

[EllKyGr]

Same, but worked when I wrote it like this:
http://www.omdbapi.com/?apikey=your_API_key

[ufoptg]

it has started to come better :) dunno what happened... I think we just need some docs on using the API i had to change how it was calling the api

[MayankCh0udhary]

@omdbapi
Anybody will give any solution for this error in API???:
{"Response":"False","Error":"Invalid API key!"}

[MayankCh0udhary]

If anyone still having same issue the do this steps:

1. Click on the URL to activate your key which is in the your API key email.
2. Now, you can use the API key.

[ufoptg]

Get a new key

[BatCountry]

The link they give you in the confirmation email has "apikey" as the last URL argument, and I've verified I can turn the problem on and off by ensuring the end of the string isn't the last character of your key, or that the key isn't the last token:

{"Response":"False","Error":"Invalid API key!"}
https://www.omdbapi.com/?i=tt3896198&apikey=madeupkey

{"Title":"Guardians of the Galaxy Vol. 2","Year":"2017",...}
https://www.omdbapi.com/?i=tt3896198&apikey=madeupkey&

{"Title":"Guardians of the Galaxy Vol. 2","Year":"2017",...}
https://www.omdbapi.com/?apikey=madeupkey&i=tt3896198

It's not simply dropping the last character of the key:

{"Response":"False","Error":"Invalid API key!"}
https://www.omdbapi.com/?i=tt3896198&apikey=madeupkeyY

So it's probably an issue with how the URL parameters are being tokenized, maybe by the underlying server wrapper?

(edit: this happens in both Firefox and Google Chrome, but doesn't happen with curl, so it may be how the GET request is structured by browsers causing the issue, or maybe the presence of some header)