Page 1 of 1

Suggestions for API-20141201

PostPosted: Sun Mar 15, 2015 6:33 pm
by achuk
Thought I'd start a new thread for suggestions for the new API-20141201.

Please standardize references to lineups. Mostly I'd like to see the ID property (instead of lineup property) standardized across all returned lineups.

Status currently returns lineups as:

{
"ID": "USA-OTA-60030",
"modified": "2014-05-17T15:47:42Z",
"uri": "/20140530/lineups/USA-OTA-60030"
}

List of headends in a postal code currently returns lineups as:

{
"name": "Antenna",
"uri": "/20140530/lineups/USA-OTA-60030"
}

and listing subscribed lineups currently returns lineups as:

{
"lineup": "BRA-0003288-X",
"name": "Nossa TV Brasileira - Digital",
"type": "Cable",
"location": "Brazil",
"uri": "/20140530/lineups/BRA-0003288-X"
}

Adrian

Edit - Refer to the correct new API version.

Re: Suggestions for API-20140530

PostPosted: Sun Mar 15, 2015 6:38 pm
by achuk
The wiki doesn't currently offer any hints to the format of possible notifications in the returned status api call - except for the fact it's an array.

I believe the same goes for messages.

Adrian

Re: Suggestions for API-20140530

PostPosted: Sun Mar 15, 2015 9:01 pm
by rkulagow
I think you mean 20141201? I will look at standardizing the names and will let you know.

Re: Suggestions for API-20141201

PostPosted: Wed Mar 18, 2015 3:25 pm
by achuk
Doh! Sorry about that. I've updated the title to reflect the correct version.

I also wanted to mention that the lineup metadata from the /lineup/{COUNTRY}-{LINEUP}-{DEVICE} endpoint returns a 'transport' property versus the /lineups endpoint returning it as 'type' (assuming that it is the same property).

I hope it doesn't sound like I'm nit-picking. I just like consistency.

Adrian

Re: Suggestions for API-20141201

PostPosted: Mon Mar 23, 2015 12:49 pm
by rkulagow
Please see

viewtopic.php?f=17&t=2645&p=8379

and let me know if you're still seeing discrepancies in the responses.