LDSTechForumProjects

Talk:Mormon Channel Web Services

Are the ID's guaranteed to be unique for their category and stay the same across multiple API calls? I.e.

<conference ID="7">
     <title>October 2005</title>
     <full_title>175th Semiannual General Conference, October 2005</full_title>
     <month>10</month>
     <year>2005</year>
</conference>

Will always be conference ID="7".

And when support for other languages is added, will these ID's be shared?

i.e. querying for:

http://tech.lds.org/radio/?action=lds.radio.conferences.query&languageID=1

and querying for:

http://tech.lds.org/radio/?action=lds.radio.conferences.query&languageID=N

Will return sets of conferences with ID's that do not overlap - or will those ID's be re-used so that

 <conference ID="7">
     <title>(foreign language text)</title>
     <full_title>(foreign language full title)</full_title>
     <month>10</month>
     <year>2005</year>
</conference>

Just curious as I start to build out an app that will be caching the data locally in an sqllite db as I retrieve it, and I want to try to make my db schema works ok.

--Ryebrye 19:56, 29 September 2009 (UTC)

No, the ID is the actual record number. So, conference ID = 7 means that it is record # 7 in the conference table. Moving to a different language would give a different ID for the same conference. THis is why you have to query the services for each language to get the proper ID's. However, ID's will not change.

Tom Welch 19:29, 21 June 2010 (UTC)

Live feed for general conferences

I'd like to know if it is possible to get the live video stream for general conference through these REST API's.

thanks,

Mathew

No, sorry but this is not available at this time. Tom Welch 13:40, 13 October 2011 (UTC)

I am wondering how soon after a general conference are the http://tech.lds.org/mc/api/conference/talklist api results updated with the newest talks?

This page was last modified on 27 April 2016, at 15:00.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.