Account Creation

Posted By: Tracy Mazelin

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

Posted In: API, News,

Comments:
No one has commented yet. Be the first!
Now You Comment

Remember my personal information.   |   Notify me of follow-up comments.

Categories:

Previous Posts:


Subscribe to the RSS feed!