API Enhancement: Requirements Exposed
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 are introducing a new feature, which allows a user to show, create, or update a document in the context of an individual requirement. This document can contain report data from an outside source. The content-types allowed to be passed for this method are:
A binary stream will be sent or received for the above formats. In short, you will be able to insert documents into Fellowship One via the API for any custom use you may have. Hello paperless church world!
These enhancements are currently live in staging and the documentation can be accessed via application/help. We welcome your feedback and would love to hear the exiting ways in which you plan to use this aspect of our growing API. Thank you for being a part of the Fellowship One Developer Community!
- 3rd Party App Showcase
March 22, 2013
- API Communication Value Changes
November 2, 2012
- API Enhancement: Create and Edit Groups!
August 13, 2012
- API Enhancement: Requirements Exposed
June 25, 2012
May 23, 2012