LDS Tools API Access/Information

[avonnied]

We are looking to build a communication tool for our local ward and I am trying to find the webservices information/api for the lds tools application? Since they retired the LDSTech Volunteer initiative and locked everything up from us members behind a lengthy top down blocking processes was going to look at just expanding some desperately needed functionality for our ward..

i found some old information on the webservices but it seems fairly outdated.. does anyone know or have a link to the latest documentation for the webservices?

[eblood66]

I'm afraid the church doesn't allow any use of the webservices by anything other than authorized church sponsored apps and they don't provide any documentation on the webservices.

[sochsner]

My YSA ward is also wanting to build a communication tool that members can download and recieve push notifications. The only things we want from an API are SSO tokens and the account’s ward Unit ID to check if they are a ward member. Or even just a true/false if we query if SSO token belongs to the unit associated with the API access.

[Mikerowaved]

My YSA ward is also wanting to build a communication tool that members can download and recieve push notifications. The only things we want from an API are SSO tokens and the account’s ward Unit ID to check if they are a ward member. Or even just a true/false if we query if SSO token belongs to the unit associated with the API access.

The post before yours from eblood66 sums up the church's stance on API's. We're not given any more info, other than "no". I can only guess it's a stipulation from the church's legal department.