Account Creation
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”, "urlRedirect":”http://www.mychurchwebsite.com/accountCreated” } }
This will return a 204 CREATED response. It is a 204 instead of 201 because there is no entity body to return for this request as per RFC2616.
Note:
- If the user already has an inFellowship account, a 409 Conflict response will be returned.
- If an existing individual is matched based on the first name, last name AND email address, then that individual will be associated to the new user login. If an existing individual could not be matched then a new individual will be created and associated to the user login.
- The user login will be initially created but not activated. An email will be sent to the email address used in the request with a link that will allow the user to activate the account. If an existing individual was matched for the user login, the user will only be prompted for a password in order to activate the account.
- If a new individual was created for the user login the user will be prompted for a password, DOB, gender, phone and address. Only password, DOB and gender are required for activation.
We are excited to see how this new feature release empowers you to take your API consumption up to the next level. This release is currently in staging and production. Don’t hesitate to give us your feedback, right here on the blog and also in our developer forums.
The documentation is available here: http://developer.fellowshipone.com/docs/v1/Util/accounts.help



Categories:
Previous Posts:
- Include Requirements & Contribution Sub Types
- User Case Story from Hope Community Church
- Group Search Categories and More
- Account Creation
- Single Sign On Functionality Exposed
- API Communication Value Changes
- API Enhancement: Create and Edit Groups!
- API Enhancement: Requirements Exposed
- Webhooks
- Resource Versioning
- Enter Visitor Data via Your Church Website
- Fellowship One & Planning Center Online
- API Libraries and Sample Code
- Building a custom login for your church website using the API
- Roll Foward!
- The Agile Triangle
- Conversation Paralysis
- Picture this, image updates & creates through the REST API
- A REST API double shot : Groups and Events realms
- Increasing Software Delivery by 500%
- Quick people API realm update
- Introducing the new REST API giving realm
- Raising the bar…
- Building a Deployment Pipeline
- The World of Dev Craft
- Running Tests in Parallel with Selenium
- Abstracting Your Code to Remove Duplication
- Documentation in an Agile Environment
- Drowning in Debt
- Intro to Ruby on Rails
- API Strategy & Roadmap
- Staging/Sandbox Environment is Back up!
- Downtime in Sandbox/Staging Environment
- Android & OAuth
- F1 API Static Library with Objective-c
- Programming in F#
- NoSQL: HuMONGOus Benefits (Part 2)
- Our Scrum Team Structure
- SaaS & BI - The History & Future
- Getting Started with Android
- NoSQL: Leaving Schema Behind (Part 1)
- Your Feedback…and a $25 Gift Card!
- A Scrum Ceremony? Is this a wedding or something?
- Variables in PHP
- Data Exchange API Fixes
- F1 Check-in on the iPad
- Be the first to get the news & tips!
- An Introduction to PHP
- Working with Pop Up Windows in Selenium
- List Comprehension
- Source Control: A Time Machine For Your Source Code
- Developer Conference…Lower Price, Same Great Content!
- The Quality Assurance Team
- How does Fellowship Technologies manage complex projects?
- Developer Conference coming in May!
- Sandbox Refresh Complete
- Sandbox Refresh This Week
- Updates coming to the REST API
- Sandbox Environment Down Time
- F1Touch :: Fellowship One On The Go
- Under the Hood
- Sandbox Refresh Complete
- Sandbox Refresh Tomorrow (Oct. 2nd)
- Fellowship One Developer Forums
- Ten Commandments of API Consumption
- REST API Enhancements / Fixes deployed to Sandbox and Production 09.09.09
- Data Exchange URL cut-over complete
- Important Data Exchange URL changes
- Ron Nom Nom
- How to get started using the REST API
