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.
Prior to the change if you either
[POST] https://churchcode.fellowshiponeapi.com/v1/people + a payload with a value for status/comment
[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…
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.
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…
- 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