API V2 broken today

Updates on the November 2019 rollout of Version 3, including testing information, TheTVDB Bible, bugs, questions, etc.
Forum rules
Please search this thread for existing bugs before posting a new one. When posting a new bug, please start a new thread.
If you're looking for API support, please take a look at our Developers forum.
ZoomStop
Posts: 4
Joined: Thu Nov 14, 2019 10:57 am

Thu Nov 14, 2019 3:28 pm

ChristyEzzell wrote:
Thu Nov 14, 2019 3:20 pm
This could be a DNS issue. Or you may be using the wrong apikey. If you go to https://www.thetvdb.com/dashboard/account/editinfo and PM me your unique user key or registered email, we can try to troubleshoot this for you.
Thank you for the link. I was on the dashboard yesterday and it looked different, I must have been loading an old version. Clicking your link loaded a newer looking dashboard and the userkey appears to have changed. Everything else is the same though. So setting the new userkey corrected the problem.

Thank you for the support here and wonderful service/api
apeg
Posts: 3
Joined: Wed May 25, 2016 7:08 am

Thu Nov 14, 2019 3:52 pm

This thread has almost 1000 views in under 8 hours.

I don't believe this issue is isolated to a single users DNS issues.

wonderful service, let me know if there is anything i can do to help troubleshoot.
psouza4
Posts: 59
Joined: Thu Sep 17, 2009 4:53 am
Location: Boise, ID, USA
Contact:

Thu Nov 14, 2019 4:56 pm

May or may not be related, but within the last few hours there are now authentication errors with the v2 API when trying to fetch mirrors.xml with a proper API key. Other pages at v2 API seem unaffected.

https://www.thetvdb.com/api/[APIKEY]/mirrors.xml

Now produces:

{"message":"Missing Authentication Token"}

API v2 shouldn't be requiring any other kinds of authentication outside of the app's API key in the URL request.
Peter Souza IV
Media Center Master (MCM)
A powerful solution for mastering your digital media library.
Supporting Emby, Kodi/XBMC/OSMC, Plex, Windows Media Center, and more!
psouza4
Posts: 59
Joined: Thu Sep 17, 2009 4:53 am
Location: Boise, ID, USA
Contact:

Thu Nov 14, 2019 5:09 pm

psouza4 wrote:
Thu Nov 14, 2019 4:56 pm
Other pages at v2 API seem unaffected.
I take it back -- other v2 pages are definitely affected for me also as described earlier in this topic (only partial pagination results being returned, for example).
Peter Souza IV
Media Center Master (MCM)
A powerful solution for mastering your digital media library.
Supporting Emby, Kodi/XBMC/OSMC, Plex, Windows Media Center, and more!
ChristyEzzell
Posts: 950
Joined: Tue Feb 26, 2019 12:01 pm

Thu Nov 14, 2019 5:12 pm

Thank you for flagging this. It appears we are currently having problems with our mirrors route and will begin looking at a fix just as soon as we can get Kodi up and running. Thanks for your patience.
bronley
Posts: 1
Joined: Fri Nov 15, 2019 3:29 am

Fri Nov 15, 2019 3:35 am

I noticed two issues.

1. It seems that the api is sending 301 responses now for any non-https pages, saying that we should use the https version. I'm using a pretty old PHP thetvdb client to load thetvdb data and it doesn't automatically handle 301 redirects, so all of those requests started failing until I updated the url embedded in the PHP client's source code.

2. Having an extra slash in the url after API used to work, but now needs to be removed.

Sending this request results in the "Authentication token required"

https://thetvdb.com/api//GetSeries.php? ... eets+World

But taking away the extra slash causes the request to work.

https://thetvdb.com/api/GetSeries.php?s ... eets+World
Bazzu85
Posts: 251
Joined: Tue Aug 13, 2013 8:34 am

Fri Nov 15, 2019 3:51 am

I'm very interessend with this problem..

I use emby and now the scraped episodes are empty ...

are there some ETA to resolve this issue?
mllarson
Posts: 1
Joined: Fri Nov 15, 2019 5:39 am

Fri Nov 15, 2019 5:48 am

I’m getting
<![CDATA[Chicago fire]]>
When I click on the show to watch it I cannot watch to show
invisiblek
Posts: 2
Joined: Fri Nov 15, 2019 6:01 am

Fri Nov 15, 2019 6:15 am

Was getting 401 errors trying to auth. Went in to my settings and my dashboard and saw my "Unique User Key" had changed. Updated it in my api call and was able to successfully auth, but my favorites list returns empty.

I also notice that if i try to generate a new api key, it's way different than the old one.
invisiblek
Posts: 2
Joined: Fri Nov 15, 2019 6:01 am

Fri Nov 15, 2019 6:32 am

invisiblek wrote:
Fri Nov 15, 2019 6:15 am
Was getting 401 errors trying to auth. Went in to my settings and my dashboard and saw my "Unique User Key" had changed. Updated it in my api call and was able to successfully auth, but my favorites list returns empty.

I also notice that if i try to generate a new api key, it's way different than the old one.
To expand on this, it seems the favorites list did indeed get nuked, re-adding favorites now allows the list to populate. I assume this is related to the user key changing. Now, I notice the returned json from the favorites call now returns a list of series by name rather than their ids. That's going to break every single thing that uses this api...
Post Reply