API V2.x Discussion

A place for developers to advertise their TheTVDB.com enabled app and get help from other developers with the API.
codegrabber
Posts: 19
Joined: Wed Mar 11, 2015 11:47 am

Re: API V2.x Discussion

Postby codegrabber » Sat Apr 14, 2018 11:57 am

Another thing which I just encountered:

The model for Series says that seriesId is an integer, but the query yields a string:

Code: Select all

"data": {
    "id": 343949,
    // ...
    "seriesId": "343949",
    // ...
}


This is rather annoying unfortunately...

Nozavi
Posts: 2
Joined: Sat May 05, 2018 9:28 pm

Summary

Postby Nozavi » Sat May 05, 2018 11:49 pm

Is there a reason why /series/{id}/episodes/summary is not integrated into /series/{id}/episodes ?

MattS
Posts: 221
Joined: Sat Mar 27, 2010 12:17 am
Contact:

Re: API V2.x Discussion

Postby MattS » Sun May 06, 2018 10:47 am

Stingray wrote:Greetings,

I've tried to use swagger.json for new API to autogenerate some client code and realized that swagger definition is incorrect.
Specifically, /search/series returns an object with "data" field that is an array of Series object, and not a single object as swagger.json says.

What I can do to fix the definition?

Thanks

codegrabber wrote:
Stingray wrote:Greetings,

I've tried to use swagger.json for new API to autogenerate some client code and realized that swagger definition is incorrect.
Specifically, /search/series returns an object with "data" field that is an array of Series object, and not a single object as swagger.json says.

What I can do to fix the definition?

Thanks


It's also out of date when querying for episodes:

The newest poll returns additional language info:

"language": {
"episodeName": "en",
"overview": ""
},

Which is nowhere mentioned...


codegrabber wrote:Another thing which I just encountered:

The model for Series says that seriesId is an integer, but the query yields a string:

Code: Select all

"data": {
    "id": 343949,
    // ...
    "seriesId": "343949",
    // ...
}


This is rather annoying unfortunately...


These fixes should be up on dev now (https://api-dev.thetvdb.com/swagger). I'll look at getting it pushed live shortly, have some other things I'd like to finish before deploying to prod.

For future issues, it's best to create a GitLab account (if you haven't already) and submit issues there (https://gitlab.thetvdb.com/site/thetvdb_api/issues). It's difficult to keep up with here and Trello isn't much better.

dremy
Posts: 1
Joined: Thu May 10, 2018 8:56 am

Re: API V2.x Discussion

Postby dremy » Thu May 10, 2018 9:12 am

Apologies if this is a little off topic, but is there a way to find the newest poster of a series using the API? The api doesn't appear to return the upload date for artwork, and I had been going by the poster file name, which usually had an integer at the end of it to denote it was added after lower integer files. But it appears with the site remodel that poster names are now completely random. I'd like my app to always display the newest poster if at all possible. Has anyone else found a solution for this?

codegrabber
Posts: 19
Joined: Wed Mar 11, 2015 11:47 am

Re: API V2.x Discussion

Postby codegrabber » Sun May 13, 2018 11:54 am

MattS wrote:
Stingray wrote:Greetings,

I've tried to use swagger.json for new API to autogenerate some client code and realized that swagger definition is incorrect.
Specifically, /search/series returns an object with "data" field that is an array of Series object, and not a single object as swagger.json says.

What I can do to fix the definition?

Thanks

codegrabber wrote:
Stingray wrote:Greetings,

I've tried to use swagger.json for new API to autogenerate some client code and realized that swagger definition is incorrect.
Specifically, /search/series returns an object with "data" field that is an array of Series object, and not a single object as swagger.json says.

What I can do to fix the definition?

Thanks


It's also out of date when querying for episodes:

The newest poll returns additional language info:

"language": {
"episodeName": "en",
"overview": ""
},

Which is nowhere mentioned...


codegrabber wrote:Another thing which I just encountered:

The model for Series says that seriesId is an integer, but the query yields a string:

Code: Select all

"data": {
    "id": 343949,
    // ...
    "seriesId": "343949",
    // ...
}


This is rather annoying unfortunately...


These fixes should be up on dev now (https://api-dev.thetvdb.com/swagger). I'll look at getting it pushed live shortly, have some other things I'd like to finish before deploying to prod.

For future issues, it's best to create a GitLab account (if you haven't already) and submit issues there (https://gitlab.thetvdb.com/site/thetvdb_api/issues). It's difficult to keep up with here and Trello isn't much better.


Good to know I can submit issues over there. If I can make it easier for you guys to keep track of them, I'll most certainly do.

brandbrilliance
Posts: 3
Joined: Tue May 15, 2018 12:28 pm

Re: API V2.x Discussion

Postby brandbrilliance » Tue May 15, 2018 5:38 pm

Can't login to my account. Also, forgot password isn't sending out any e-mails. So now Im unable to retrieve my userkey for the new API.

Hansaplastique
Posts: 1
Joined: Wed Oct 10, 2018 4:52 pm

Re: API V2.x Discussion

Postby Hansaplastique » Wed Oct 10, 2018 5:09 pm

I'm new to this forum, and have been searching through all the posts and carefully studying the v2 API, and could not find an answer.

I'm wondering if a "lastupdated" field could be added to search results when searching for a show (for example: https://api.thetvdb.com/search/series?name=lost). This way I know if I can rely on my local data, or if I need to refresh my local data, for the show details.

Case:

Here is the usual workflow;
1) a user enters a name of a TV show he/she is looking for. For example "lost" (https://api.thetvdb.com/search/series?name=lost)
2) a long list is returned from which the user can select the best match.
3) The user can now select a show in the list to see the details of the show (for each show for example https://api.thetvdb.com/series/73739)
4) When the user found the correct show, he/she can then retrieve all episodes of the selected show.

Now, previous each data retrieval will be stored in a local SQLite database, so the application doesn't need to pull all the info from TheTVDB.
The only problem I'm running into is that the search (step 1) doesn't provide a "lastupdated" field.
Therefor I will not know if I can rely on my local data in step 3 or not, so effectively I have to download the show details each and every time, for every selected show, even if the data has not changed - which seems like a waste of resources.

I can imagine a proper "lastupdated" field in the result results could save a nice number of queries per day, and it most certainly will speed up my application.

(obviously, for the episodes I'm already relying on "lastupdated" in the show details query (https://api.thetvdb.com/series/73739)

My apologies if this has been addressed elsewhere - I couldn't find it in this forum.