Blog Archive

Include Requirements & Contribution Sub Types

Posted By: Tracy Mazelin on June 9, 2014

We’ve been busy adding functionality to our REST API and wanted to let you know about a few updates that are currently in production on the People and Giving realms:

Include=Requirements

It’s now possible to pass an additional include attribute to the people search method. You can use include=requirements to get a list of people with their individual requirements. You must pass a custom content type in the header for this to work. For example:

[GET] https://demo.fellowshiponeapi.com/v1/People/Search?searchFor=smith&include=requirements
Content-Type: application/vnd.fellowshiponeapi.com.people.people.v2+json

This will return a paged set of people records with their individual requirements.

Contribution Sub Types

We’ve added a new resource to the giving realm of the API: contribution sub types with list and show methods. It has always been possible to designate a contribution sub type as part of a contribution receipt. However, until this release, it was not possible to query the API to retrieve a list of…

Read the whole entry...
Posted In: API, News,
Comments: 0  Comments

User Case Story from Hope Community Church

Posted By: Tracy Mazelin on October 28, 2013

Today we are featuring a user case story submitted by Todd Darling of Hope Community Church in Raleigh, NC.  Todd has developed a creative solution which utilizes our API to enhance their student check in experience.  Check out the video and post outlining exactly how they are doing this.  Many thanks to Todd and the technology team at Hope Community Church for the work they put into sharing this with our developer community.  Enjoy!

Guest Author: Todd Darling, Web Developer
Hope Community Church in Raleigh, NC



THE SETUP:
For our middle and high school student ministries on the weekend, the students check themselves in, most of the time without a parent. During our midweek middle school service—which often has 300+ middle schoolers—a lot of students bring friends whose families don’t even go to Hope (which is AWESOME!)

How…

Read the whole entry...
Posted In: API, News, Tips,
Comments: 0  Comments

Group Search Categories and More

Posted By: Tracy Mazelin on October 21, 2013

We have released two updates to our Groups Realm.  The first is a new resource for retrieving Group Search Categories.  It is now possible to pull group category IDs via the API and pass the “categoryID” as a search parameter on a group search.  This will allow those who have built their own custom user interface for interacting with small groups to match the search categories on their website, with what they have defined within portal!  Check out the documentation here: http://developer.fellowshipone.com/docs/groups/v1/categories.help

In addition, we added a node to a group resource called “isLocationPrivate”.  If the location of a small group is set to private within Fellowship One, it is now possible to pull that data back via the API.  The node is optional and will not break any existing implementations for retrieving and creating groups.  Consume away!

Read the whole entry...
Posted In: API, News,
Comments: 0  Comments

Account Creation

Posted By: Tracy Mazelin on August 7, 2013

We are excited to announce the release of new functionality within our REST API—the ability to create inFellowship user accounts!  This highly requested feature will allow developers within our developer community the ability to create a seamless user experience when integrating with our API.  Examples of where we expect this to be consumed the most would be within church websites and custom built church applications.  Our 3rd party vendors may benefit from this enhancement also.

Here are the steps to consume it:

Request an empty model of this resource by calling:

[GET] https://demo.staging.fellowshiponeapi.com/v1/Accounts/New

Response:

 { "account":{ "firstName":null, "lastName":null, "email":null, "urlRedirect":null } } 

The firstName, lastName, email fields are self-explanatory.  The urlRedirect is the call back address that you would like your website/app user to be sent to after the inFellowship account is created and activated.

For example:

[POST] https://demo.staging.fellowshiponeapi.com/v1/Accounts REQUEST BODY: { "account":{ "firstName":Tracy, "lastName":Mazelin, "email":”my.email@test.com”,…
				

Read the whole entry...
Posted In: API, News,
Comments: 0  Comments

Single Sign On Functionality Exposed

Posted By: Tracy Mazelin on June 25, 2013

We are excited to announce the latest of additions to our API, Single Sign On!  The following video is the first part of a two part series showing how to consume these new API methods.  Part two will demonstrate using the API to create an Infellowship User Account.  We would love to hear your feedback on this.  Please test it out in the staging area and let us know your thoughts!


Documentation: http://developer.fellowshipone.com/docs/v1/Util/SingleSignOn.help
Example Code: https://github.com/tracymazelin/SingleSignOnDemo

Read the whole entry...
Posted In: API, News, Tips,
Comments: 2  Comments

3rd Party App Showcase

Posted By: Tracy Mazelin on March 22, 2013

App Gallery

Check out our new gallery of 3rd party vendor applications that integrate with Fellowship One using our API!  To enable an application, you can login to Fellowship One and select Admin and Applications. Our new app showcase features screenshots of the apps along with additional details of what the app does and how to contact the vendor.

If you are a vendor looking to integrate with Fellowship One, please use the gallery to view the types of apps we currently offer to determine how you can best integrate and extend the functionality of Fellowship One.  The process starts by applying for an API key.  You will receive a sandbox environment in which to build and test your code.  Once development is complete, you would then need to submit your code to our API Code Review team and…

Read the whole entry...
Posted In: API, News,
Comments: 0  Comments

API Communication Value Changes

Posted By: Tracy Mazelin on November 2, 2012

As many of you know, earlier this year we began to streamline the types of communication values available in Fellowship One.  More information about the project can be found on our community blog here, and also on the developer blog here.

As a result of this project, we enhanced functionality around communication values via our API, and last week we pushed the enhancements to production.  You, our developer community, responded very well to the changes.  You rock!

Here is a review of the changes and enhancements:

Reduction in Communication Types.

GET https:// demo.fellowshiponeapi.com/v1/communications/communicationtypes

Response:

 { "communicationTypes":{ "communicationType":[ { "@array":"true", "@id":"1", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/1", "@generalType":"Telephone", "name":"Home Phone" }, { "@array":"true", "@id":"2", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/2", "@generalType":"Telephone", "name":"Work Phone" }, { "@array":"true", "@id":"3", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/3", "@generalType":"Telephone", "name":"Mobile Phone" }, { "@array":"true", "@id":"138", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/138", "@generalType":"Telephone", "name":"Emergency Phone" }, { "@array":"true", "@id":"5", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/5", "@generalType":"Email", "name":"Home Email" }, { "@array":"true", "@id":"4", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/4", "@generalType":"Email", "name":"Email"…
				

Read the whole entry...
Posted In: API, News, Tips,
Comments: 0  Comments

API Enhancement: Create and Edit Groups!

Posted By: Tracy Mazelin on August 13, 2012

We have released another API enhancement to production!  It is now possible to create and edit Groups via the API.  Check out this video that demonstrates how to consume these new API methods using the Google Chrome HTTP Dev Client:

Read the whole entry...
Posted In: API,
Comments: 2  Comments

API Enhancement: Requirements Exposed

Posted By: Tracy Mazelin on June 25, 2012

We are excited to announce our latest API enhancement - Individual Requirements!  Individual Requirements are typically used for two reasons:  to track items that need to be completed before a person can volunteer for a job and to track different stages of membership.  Requirements can be specific and fully customized.

This API feature enhancement expands the capacity of our API to both churches and vendors alike.  Both will now be able to create, read, update and delete Individual Requirements via the API, which opens up the potential for new vendors to partner with Fellowship One in delivering automated background check solutions.  Active Network | Faith already partners with a few well-known background check companies and the integration is written directly into Fellowship One.  By exposing individual requirements via our publically facing API, the opportunity for any vendor to integrate with Fellowship One is now a reality.

With this release we…

Read the whole entry...
Posted In: API, News,
Comments: 6  Comments

Webhooks

Posted By: Tracy Mazelin on May 23, 2012

 

The video above is a tutorial to show how it is possible to use a web service such as Formstack to collect data on your church website and have the data go directly into Fellowship One via a webhook.  The concepts carry true for other web services that feature webhooks, such as Wufoo - another online form builder solution - or Mail Chimp, which offers email marketing and email list management.

Utilizing webhooks along with the Fellowship One API allows you to keep Fellowship One as the authoritative database of record by intelligently pushing in data - in real time - from other web services.

Watch the video and let us know in the comments section if this is something your church could use!

If you don’t have an API key yet, sign up…

Read the whole entry...
Posted In: API, Tips,
Comments: 9  Comments

Resource Versioning

Posted By: Tracy Mazelin on April 24, 2012

Enhanced Functionality without breaking Compatibility

We’re excited to announce a few changes coming to the API! If you have been following along with the Community Blog, you will be aware of the initiative to streamline communication values. If not take a look at the posts here and here. It follows that these changes will be reflected through the API also.  As part of this effort, the "listed" functionality around each communication resource will soon be discontinued as well as the node being removed. Instead, we will be adding a new node to the people resource called "unsubscribed".

Currently, the "listed" node is returned with each communication resource as follows:

[GET] https://demo.fellowshiponeapi.com/v1/Households/1552366/Communications.json

Response:

... "communicationType":{ "@id":"1", "@uri":"https://demo.fellowshiponeapi.com/v1/Communications/CommunicationTypes/1", "name":"Home Phone" }, "communicationGeneralType":"Telephone", "communicationValue":"214-759-2756", "searchCommunicationValue":"2147592756", "listed":"true", "communicationComment":null, "createdDate":"2005-01-20T01:04:55", "lastUpdatedDate":"2005-01-20T01:04:55" ... 

In 30-45 days, this node will be removed. If you are using the API to retrieve…

Read the whole entry...
Posted In: API,
Comments: 2  Comments

Enter Visitor Data via Your Church Website

Posted By: Tracy Mazelin on March 16, 2012

Possibilities For Ministry Use

  • Capture contact information dynamically during a worship service instead of using visitor cards
  • Allow volunteers to enter simple data into Fellowship One through your church website
  • Setup a kiosk where visitors can enter their own contact information

The Code
The following is the PHP code used to process the form entries and write the data into Fellowship One through the API.  This example uses the PHP Helper Class, ‘FellowshipOne.php’ contributed by a member of our developer community, Daniel Boorn.  A few methods were added to the helper class and you will find a link to all the source code below this code example.  Please feel free to use and adapt this as necessary.  If you don’t already have an API key, you can apply for one here: https://developer.fellowshipone.com/index.php/key

 <?php require('FellowshipOne.php'); $settings = array(…
				

Read the whole entry...
Posted In: API, Tips,
Comments:  Comments

Fellowship One & Planning Center Online

Posted By: Tracy Mazelin on March 1, 2012

How to Fork, Host, Deploy and Contribute to this open source project

It is now possible to sync your Fellowship One people demographic data to your Planning Center Online Account via an open source application that utilizes both the Fellowship One API and the Planning Center Online API.  This blog post is going to walk you through the process of setting up and hosting this application.

What you will need:

  An account on github (free)
  An account on a fully hosted .NET platform as a service such as AppHarbor (free)
  Microsoft SQL Server Management Studio (free)
  Consumer Key and Secret from F1 (apply here)
  Consumer Key and Secret from Planning Center (apply here)

Step 1: Fork the Repo and make a local clone
In order to contribute to another developers project or use their project as a starting…

Read the whole entry...
Posted In: API,
Comments: 6  Comments

API Libraries and Sample Code

Posted By: Tracy Mazelin on February 7, 2012

Code libraries make it easier for you to use the Fellowship One API in the language or framework of your choice.  We have compiled a list of code libraries along with some sample code to help get you started with your API project.  We are thankful to numerous members of our developer community for being willing to contribute their work to help others get their projects off the ground.  If you have developed your own library, or you have any code examples you would be willing to share, please .(JavaScript must be enabled to view this email address).  We would love to add your work to the list.  Check out the library here:

https://developer.fellowshipone.com/libraries

Tracy Mazelin is the newest member of the API Developer Team at Fellowship Technologies (part of Active Network).  She is passionate about evangelizing the API and giving users the tools they need to take them to…

Read the whole entry...
Posted In: API,
Comments: 0  Comments

Building a custom login for your church website using the API

Posted By: Tracy Mazelin on November 29, 2011

Background

The Application Programming Interface (API) of Fellowship One provides a way for churches to leverage their own church data within custom built applications. This tutorial is going to outline how you can use our API to build a custom login to your church website by authorizing the user based on their WebLink or InFellowship login credentials. This is a 2nd party application and this post builds upon the foundation laid by Jas Singh here. You will find links to the PHP oAuth library and more detail about 2nd party authorization in his post.

Step 1: Build a login form

image

First, you will need to build a login form requesting a username and password. If the majority of your church has already converted their WebLink login to an InFellowship login, then you will want to ask for their email address…

Read the whole entry...
Posted In: API, Tips,
Comments:  Comments

Picture this, image updates & creates through the REST API

Posted By: Nick Floyd on May 10, 2011

We just released another API update.  You can now create and update images from the People realm:

Any cool ideas on what you can do with this? Let us know what you’re doing with the API realms via twitter or forum.

Nick Floyd is an Architect for Fellowship Technologies (part of Active Network).  Currently he is focused on improving, designing, and building the architecture around the Fellowship One platform.  He likes learning about new technologies and languages (the obscure and the vanilla) as well as learning about new trends and practices around getting really good software from development to the users, fast.  He is passionate about software development and helping other developers.

Read the whole entry...
Posted In: API, News,
Comments:  Comments

A REST API double shot : Groups and Events realms

Posted By: Nick Floyd on May 9, 2011

We’re back again to bring you two new realms for accessing your data via FellowshipOne.  The Groups Realm and the Events Realm are the two newest members of our API family!  The Groups Realm opens up access to Fellowship One’s Groups 2.0 features and allows churches and vendors to create new Groups 2.0 capabilities or integrate with other solutions.  The Events Realm provides access to a primary event that can be associated with a Group within the Groups Realm.

Note:  The Events Realm does not at this time provide access to Fellowship One Activities, Check-in, or Event Registration.

Groups resources

Groups

Members

  • Members: Search (3rd) | List (3rd) | Show Read the whole entry...
    Posted In: API, News,
    Comments:  Comments

    Quick people API realm update

    Posted By: Nick Floyd on March 16, 2011

    One of our consumers was nice enough to let us know about an “undocumented feature.”  Normally with bug fixes and small enhancements we’d just deliver the changes and let the docs tell the story, however, this change is around a more sensitive area and wanted to make sure that everyone knew about it.

    The change is to Creates and Updates of the people resource on status/comment.

    Prior to the change if you either

    [POST] https://churchcode.fellowshiponeapi.com/v1/people + a payload with a value for status/comment

    or

    [PUT] https://churchcode.fellowshiponeapi.com/v1/people/[id] + a payload with a value for status/comment

    The value for the “comment” node would not “create” or “update.”

    This has been fixed to now do what you might expect it to do in your sand box environment and we are planning on pushing the change to production tomorrow. If you have a chance please go check it out and let…

    Read the whole entry...
    Posted In: API, News,
    Comments:  Comments

    Introducing the new REST API giving realm

    Posted By: Nick Floyd on March 8, 2011

    The dev team has been working hard to bring you the next step in the Fellowship One REST API stack - the Giving Realm! We’ve opened up all sorts of resources to help you bring giving into your church.  From accounts to sub funds - all the resources you’ve been asking for served up on a RESTful plate.

    Realms

    You might also notice that we are using a new term to classify our API resource sets: REALMS. Realms are how we will be classifying groups of functionality exposed through the APIs and will help you manage your consumption through segmentation.  The realms will provide churches with the ability to allow or restrict what data consumer applications use and they will enable developers of consumer applications a platform to request specific application keys for specific functions a al carte or application keys that cover the entire stack. For instance, when…

    Read the whole entry...
    Posted In: API, News,
    Comments:  Comments

    API Strategy & Roadmap

    Posted By: Scott Lowrie on August 17, 2010

    Looking back, only for moment…

    Almost a year ago to the day, Fellowship Technologies deployed the Fellowship One REST API into production. We were excited to achieve this milestone since it represented months of dedicated work by our development team. Since then committed developers, vendors, and our own staff have come together to form a Community dedicated to bring solutions to the church world. I am encouraged and edified by the fantastic work that has been accomplished. Good work!

    If you cook it, then you better be prepared to eat it…

    We believe that the best way to prove our API can accomplish what others need it to accomplish is to use it ourselves. No… I am not talking about for just some things like a mobile app that does this, or a CMS shared login, or vendor solution integration. I am talking about using our own API for the…

    Read the whole entry...
    Posted In: API, News,
    Comments:  Comments