Fellowship One RESTful API is a REST based web application that uses several open protocols and patterns to provide consumers access to secure resources. STANDARDS, PROTOCOLS, and PATTERNS - nothing else. As developers we see where there is major value in sticking with something that is "tried and true." If we could use web based patterns and protocols for a web based API we could not only get instant adoption but gain the efficiencies and effectiveness of technologies that "just work."   

Enjoy all of the features and benefits of being part of the Fellowship One developer community.
• Engage others in the developer community
• Get access to loads of code to use and learn from
• Create / Share applications that consume the Fellowship One REST API

Since we are community focused, we wanted you to have as much code and information that you'd need to get jump started for the REST API so that you'll be able to discuss / communicate your ideas on consuming the REST API throughout the social-sphere. Please take a moment to check out the current code libraries and blogs.

Include Requirements & Contribution Sub Types

Posted By: Tracy Mazelin

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 contribution sub types. Now it is:

[GET] https://demo.fellowshiponeapi.com/giving/v1/contributiontypes/4/contributionsubtypes.json

Will return:

{
"contributionSubTypes":{
	"contributionSubType":[
	{
		"@id":"29",
		"@uri":"https://demo.fellowshiponeapi.com/giving/v1/contributionTypes/4/contributionsubtypes/29",
		"name":"Property"
	},
	{
		"@id":"30",
		"@uri":"https://demo.fellowshiponeapi.com/giving/v1/contributionTypes/4/contributionsubtypes/30",
		"name":"Stocks or Bonds"
	},
	{
		"@id":"31",
		"@uri":"https://demo.fellowshiponeapi.com/giving/v1/contributionTypes/4/contributionsubtypes/31",
		"name":"Vehicle"
	}
	]
    }
}

The contribution sub type id can be used when creating a contribution receipt. The documentation for this functionality is available here:

https://demo.staging.fellowshiponeapi.com/giving/v1/contributiontypes/contributionsubtypes.help

Let us know if there are any API resources that you need to help you leverage Fellowship One to a greater capacity.

 

 

Posted In: API, News, Tips,
Comments: 0 Comments