Developer discussion for API 20191022

rkulagow
SD Staff
Posts: 940
Joined: Tue Aug 14, 2007 3:15 pm

Developer discussion for API 20191022

Post by rkulagow »

Please post your questions in this thread.
enternoescape
Posts: 6
Joined: Wed Jul 27, 2016 2:42 pm

Re: Developer discussion for API 20191022

Post by enternoescape »

Will this completely replace the previous version of the API soonish ( < 1 year) or will the previous API version be around for a significant amount of time with no feature improvements?
rmeden
SD Board Member
Posts: 1608
Joined: Tue Aug 14, 2007 2:31 pm
Location: Cedar Hill, TX
Contact:

Re: Developer discussion for API 20191022

Post by rmeden »

We don't have a timeline for retirement of the old API.
emveepee
Posts: 19
Joined: Sat Jan 26, 2013 9:21 am

Re: Developer discussion for API 20191022

Post by emveepee »

rmeden wrote:
Fri Jan 31, 2020 1:54 pm
We don't have a timeline for retirement of the old API.
There are two existing API's the XMLTV tv API and the JSON API. Are you referring to both of these?

Martin
rmeden
SD Board Member
Posts: 1608
Joined: Tue Aug 14, 2007 2:31 pm
Location: Cedar Hill, TX
Contact:

Re: Developer discussion for API 20191022

Post by rmeden »

SD doesn't offer an XMLTV API.

SD does have two APIs... SD-JSON and SD-DD (old Tribune DataDirect format, which is XML based, but not XMLTV)

No changes are planned for the SD-DD API or format.

This new API is for the SD-JSON service (This is the SD-JSON forum board!). Eventually it will replace the current API, but there is no retirement timeframe.
sirbryan
Posts: 1
Joined: Wed Mar 11, 2020 3:23 pm

Re: Developer discussion for API 20191022

Post by sirbryan »

Using Postman, I'm successful in obtaining a token using the 20141201 API, but not with 20191022. It keeps coming back saying "Missing authentication token."

I've tried with both application/json and text/plain, with the same result.
pete318
Posts: 10
Joined: Wed Nov 23, 2016 6:30 pm

Re: Developer discussion for API 20191022

Post by pete318 »

sirbryan wrote:
Wed Mar 11, 2020 4:30 pm
Using Postman, I'm successful in obtaining a token using the 20141201 API, but not with 20191022. It keeps coming back saying "Missing authentication token."

I've tried with both application/json and text/plain, with the same result.
Same result here. I thought I'd have a bash at swapping to the new API. But, I get 403 with the same above message. I tried putting a dummy token in the header to no avail. Something not quite right, or something missing in the documentation.
nzsjb
Posts: 3
Joined: Fri Mar 20, 2020 6:35 pm

Re: Developer discussion for API 20191022

Post by nzsjb »

In the 2014 API there was a request available to 'List the lineups a user has added to their account'.

Has this been removed in the 2019 API? If I send in a Lineup request without a country code/postcode it generates an error response.
gtb
Posts: 113
Joined: Thu Oct 02, 2014 2:07 pm

Re: Developer discussion for API 20191022

Post by gtb »

nzsjb wrote:
Mon Mar 23, 2020 4:19 pm
Has this been removed in the 2019 API?
That endpoint is not in the 2019 API docs, and it does not work, so while I don't remember it being explicitly called out as a deletion, I interpreted that as a design choice.

The information you are looking for, however, has been in the "/status" response for a while, and still is in the 2019 API. You will (likely) have to convert (since it exists in the 2014 API you can do that conversion now).

However, and while it is a small nit, the /status request does not (never has) included the "location" information that you get back from the 2014 /lineups request.
nzsjb
Posts: 3
Joined: Fri Mar 20, 2020 6:35 pm

Re: Developer discussion for API 20191022

Post by nzsjb »

Is it possible to add the location to the status response in the 2019 API?
Post Reply