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)

API issues #316

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions