Fellowship One Developer Forums

Posted By: Nick Floyd on September 25, 2009

We’ve just launched a forum dedicated to all things development/API. This is going to be a great place for developers to ask questions, discuss ideas, etc. By giving one central location for these discussions, it will allow for a lot more interaction within the development community.

This is also a great place for churches, vendors, and devs who are interested to learn more about the Fellowship One API offerings or development in general. The topics range from basic getting started topics to how to write the code!

To find the new forums, you can click on “Forum” at the top of the page or get it directly here.

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

Ten Commandments of API Consumption

Posted By: Nick Floyd on September 10, 2009

We have created ten basic guidelines for consuming the REST API. The first 5 commandments are to help consumers interact with the API. The last 5 are how consumers can interact with others in the community to grow, learn, and build.

Ten Commandments of API Consumption

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

REST API Enhancements / Fixes deployed to Sandbox and Production 09.09.09

Posted By: Nick Floyd on September 9, 2009

The following enhancements and fixes have been deployed to the Sandbox and Production environments:

#918 (Sifter) Add Address / Communication Collection results to people search results
Notes: Now when using the include parameter in People/Search all addresses and communications returned will match data with what is returned when calling People/{id}/Addresses and People/{id}/Communications respectively.
Supporting docs
Ex: people/search?searchfor=fl,ni&include=addresses, communications

#853 (Sifter) Add new search parameter to People search: BarCode
Notes: Consumers can now do a people search by barcode
Supporting docs
Ex: people/search?barcode=12341234

#1037 (Sifter) Returning a 403 instead of oa 400 when churches do not have the association
Supporting docs

These changes will not cause consumer interface contract breakage unless the consumer was checking for status code 400 when…

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