Page 2 of 6

Re: Issues with the API

Posted: Thu Nov 14, 2019 5:43 am
by rudis1261
I am definitely setting the details in the POST. Tried using insomnia, tried swagger interface, my code via PHP Curl. None of it works, it's like its not reading the posted JSON content. Tried setting the version headers as described, with no effect.

Re: Issues with the API

Posted: Thu Nov 14, 2019 6:09 am
by LLloody
I found that the /login route will not accept:
{
"apikey": "string",
"userkey": "string",
username: string
}
but does accept:
{
"apikey": "string",
"userkey": "string"
}
OR
{
"apikey": "string",
}
this leads to all calls to the /user routes, using the returned JWT Token, returning:
results for the same person (even tho I supplied my own userkey)
{
"data": {
"userName": "abrazite",
...,
...,
}
}

Re: Issues with the API

Posted: Thu Nov 14, 2019 6:51 am
by Tracy
The /updated/query route is not working either - even specifying the version and obtaining the JWT Token by not sending the username.

Re: Issues with the API

Posted: Thu Nov 14, 2019 11:01 am
by szsori
This should be fixed. We also updated the user routes caching. Thank you all for your patience.

Re: Issues with the API

Posted: Thu Nov 14, 2019 11:37 am
by imthedoctor12
The links section in the response seems to be having an issue as well. It's always returning

Code: Select all

"links": {
        "first": 1,
        "last": 1,
        "next": null,
        "prev": null
    }
even if there are more pages

examples from https://api.thetvdb.com/swagger vs https://api-dev.thetvdb.com/swagger

curl -X GET --header 'Accept: application/json' --header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.[..]m1DyVAmA' 'https://api-dev.thetvdb.com/series/78804/episodes'

yields

Code: Select all

{
  "links": {
    "first": 1,
    "last": 3,
    "next": 2,
    "prev": null
  }
while

curl -X GET --header 'Accept: application/json' --header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.[..]K-j6ow' 'https://api.thetvdb.com/series/78804/episodes'

yields

Code: Select all

{
  "links": {
    "first": 1,
    "last": 1,
    "next": null,
    "prev": null
  }
I'm trying to send the accept header to specify version 2.2.2 but no matter what value I pass the response appears to always be coming from X-Thetvdb-Api-Version 3.0.0

In postman I'm setting the header with a Key of Accept and a Value of application/vnd.thetvdb.v2.2.2, is that the proper way to specify the version?

Re: Issues with the API

Posted: Thu Nov 14, 2019 12:18 pm
by Tracy
I can confirm that the /updated/query route is now working but I still cannot get a JWT Token via the /login route in swagger.

Re: Issues with the API

Posted: Thu Nov 14, 2019 2:51 pm
by dlflannery
My app uses just the API key but is now failing to get tokens.

Re: Issues with the API

Posted: Thu Nov 14, 2019 2:53 pm
by ChristyEzzell
What app are you using?

Re: Issues with the API

Posted: Thu Nov 14, 2019 6:36 pm
by dlflannery
ChristyEzzell wrote:
Thu Nov 14, 2019 2:53 pm
What app are you using?
It's metagenerator 3 which I program. Has been working fine with api v2 up until yesterday.

Re: Issues with the API

Posted: Thu Nov 14, 2019 6:56 pm
by szsori
Does your API key end in C33 or 1AE?