Open topic with navigation

You are here: People Management > Integration > Integration Applications

Enabling Third Party Applications

The Fellowship One application programming interface (APIAPI is an application programming interface.It builds up applications using protocols set out by Operating Systems. They can either be dependent on language or independent of language, depending on whether it can function in several different programming languages or just one. Some examples of interfaces that use API are: Windows Macintosh iPhone Google Maps MediaWiki YouTube PayPal Payment Facebook) allows churches and business partners to easily extend the power of the Fellowship One church management software. The Fellowship One API is built upon REST application architecture principles and is open for use by churches using Fellowship One and for qualified business partners.

A great example of the Fellowship One API in action is the Fellowship One iPhone application called F1Touch. F1Touch allows users to access their Fellowship One database to perform a people search and view individual details.

Applications that integrate with Fellowship One (via the REST API) can be found under Admin>Integration>Applications. Several things are required for an application to work:

  1. The church must give the application permission to access to its data.This can be done from the Applications page.
  2. The user's account must be linked to their individual record. See Adding Fellowship One Users for information on linking.
  3. For some applications, the user must give the application permission to access Fellowship One through their account. They do this when they use the application for the first time.

 

There are three types of applications available via the Fellowship One API:

1st Party: These applications are developed by Fellowship Technologies for its customers. Access to 1st party applications will be granted to all Fellowship One customers. The individual church has the ability to Revoke access to applications at any time.

2nd Party: These applications are developed for your church, by your church--or by an outside developer on behalf of your church. 2nd party applications are church specific and available to only the church it was developed for. For information about developing 2nd party applications and to apply for an API key, visit developer.fellowshipone.com.

3rd Party: These applications are developed by approved partners of Fellowship Technologies for its customers. Access to 3rd party applications will not be granted automatically to all Fellowship One customers. The individual church must choose to Grant access in order for the application to access the church's data. The church has the ability to Revoke access to 3rd party applications at any time. For information about developing 3rd party applications and to apply for an API key, visit developer.fellowshipone.com.

 

To Grant or Revoke access to an application:

  1. Click on the application name.
  2. Click Grant access to allow the application to access church data.
  3. Click Revoke access to disable the application and prevent the application from accessing church data.