Fellowship One

Fellowship One 

Setup information

As we get started on integrating F1 and ServiceReef, this will be your guide to key information and steps you (or someone at your organization) will need to complete.  As always, please reach out if there are any questions.  Please note that there is an Appendix at the end of this document which walks you through this in a step-by-step format.

Overview of Environments

First, let’s understand your current F1 environment.  The FellowshipOne system typically employs two environments for your organization.  The first is “Staging”, which is like a test environment and is sometimes referred to as “Sandbox”.  For you, this was likely created a while ago and has a backup of your organization’s data from some point in the past.  This is helpful for any testing that you want to do between ServiceReef and F1.  However, please note that because this was established at some point in the past, it may not have all of the funds/sub-funds, ministries, etc. that you have in your current production environment.

The second F1 environment is your production environment.  This is where you spend your day-to-day activities and this is your current data.  The two environments are kept separate by using a different url and different keys to access these environments.  Additionally, the user access will vary between environments.

Why does this matter? 

You will need to reach out to your FellowshipOne account rep and request a 2^nd Party Key that ServiceReef will use for this integration.  Specifically, we will need two keys (one for Staging and one for Production)… if you have both environments set up.  If you only have a Production environment, then you will only need production keys.

A Quick Understanding of the Consumer Keys

This key will only access your organization’s database.  No other F1 church can use it to access their data.  Therefore, each church needs to request their own 2^nd Party key to use with the ServiceReef integration solution.  Successful login requires the key information and the username/password.  After everything is working correctly in Staging, a Production key can be requested which will have a different API Key & Secret value and URL address.  Everything else should work the same except the People/Contributor records, Fund/SubFunds and Ministry/Activities to be used may be different between staging and production (based solely on what data you have in your staging environment).

Who do I contact at F1?

Your individual contact at F1 may vary, so check with your teams to determine who the best contact might be.  From the FellowshipOne website, the general customer support information is:

FellowshipOne Support:

866-383-2437

Customer Support Portal

F1Support@fellowshipone.com

What will I need to provide ServiceReef?

To integrate the two systems, you need to provide the following information.  Again, please ignore the “Staging” information if you do not have a staging/sandbox environment with FellowshipOne.

Staging/Sandbox Information:

Fellowship One Staging Portal

URL: (example might look like https://portal.staging.fellowshipone.com/login.aspx )

Username: (example: servicereef)

Password:

ChurchCode:

Please note: The user that is created must be linked to the API Account/person for the sync process to function properly.  If not linked, the following error will appear: “ Your Fellowship One Portal user needs to be linked to a Person before you can use this application.  Please talk to your Fellowship One administrator to get your User account linked.”

Fellowship One Staging API

URL: (example might look like https://yourorganization.staging.fellowshiponeapi.com/v1/ )

API Consumer Key:

API Consumer Secret:

Type: 2^nd Party

Username: (example: servicereef)

Password:

ChurchCode:

Production Information:

Fellowship One Production Portal

URL: (example might look like https://portal.fellowshipone.com/login.aspx )

Username:

Password:

ChurchCode:

Please note: The user that is created must be linked to the API Account/person for the sync process to function properly.  If not linked, the following error will appear: “ Your Fellowship One Portal user needs to be linked to a Person before you can use this application.  Please talk to your Fellowship One administrator to get your User account linked.”

Fellowship One Production API

URL: (example might look like https://yourorganization.fellowshiponeapi.com/v1/ )

API Consumer Key:

API Consumer Secret:

Type: 2^nd Party

Username:

Password:

ChurchCode:

How does the information flow between systems?

Appendix A: A Step by Step Guide

Step 1 

Determine if you have a FellowshipOne staging environment. 

1. If you do NOT have a staging environment, skip to step 4.
2. If you do have a staging/sandbox environment, create a portal username/password for servicereef and ensure that user is linked to a person/API.
3. Create a username/password for the Staging API environment (this can be the same as your portal UN/PW)

Step 2: Request a 2^nd party key from FellowshipOne for your staging environment.  Specifically, you will need to provide ServiceReef with the following pieces of information (first two are from F1, the other three or four are from Step 1 above and the user you created):

1. API Consumer Key: (e.g. 123)
2. API Consumer Secret: (e.g. a hashed key… should look something like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx)
3. Type: 2^nd Party
4. Username
5. Password
6. ChurchCode

Step 3: Once ServiceReef has configured the test environment, validate that the correct information is being generated in the F1 Staging Portal when applicants apply for trips and/or donations occur.

Step 4: Create a portal username/password for servicereef on your production environment and ensure that user is linked to a person/API.

1. Create a username/password for the Production API environment (this can be the same as your portal UN/PW)
2. Provide the url for the production environment and the credentials of the users you created to ServiceReef

Step 5: Request a 2^nd party key from FellowshipOne for your production environment.  Specifically, you will need to provide ServiceReef with the following pieces of information the first two are from the information you receive from FellowshipOne):

1. API Consumer Key: (e.g. 123)
2. API Consumer Secret: (e.g. a hashed key… should look something like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx)
3. Type: 2^nd Party
4. Username
5. Password
6. ChurchCode

Step 6: ServiceReef will configure your production environment to sync with your production database.  Review the first few days to ensure all data (donations, applications, etc.) are coming in to F1 correctly.