Skip to main content
Pushpay/CCB integration: Setting up the API

Need to add a new API user in Pushpay/CCB? Here's the walkthrough - both via video and text.

Jason Alexis avatar
Written by Jason Alexis
Updated over 7 months ago

In order to create a sync between Pushpay/CCB (CCB) and Display.Church, you need to create an API user in your CCB account. You will need to have permission to do this. 

To check whether or not you have permission to do this, log in to your Pushpay/CCB account. 

Click here to go to the OLD VERSION if needed.


NEW VERSION

(1) Click on Settings (blue box in image to the left).

If you see the API option, you have the needed permission to continue.

If you do not see this option or are unsure about anything, be in touch with your database administrator.

(2) Click on the API option. You will see the API summary screen (image below).

(3) Click on Add a new API User (blue box and arrow in image above).

(4) You will see the New API User form. Complete this form with the needed details.

  • For the name, we recommend something simple such as ‘displaychurch’ (one word, no spaces). Your name must be unique. In other words, it must be different from any name already in the system.

  • For the username, we recommend using the same ‘displaychurch’ (one word, no spaces).

  • Your password should be something which is difficult to guess. According to Pushpay/CCB, passwords must include at least 8 characters; must include at least 1 upper case letter; and must include at least 1 number.

  • The Primary Organization Contact Information is optional. If you wish, you can use the Display.Church contact information, but again, this is totally optional.

Make a note of the username and password. You will need this later to update your integration in Display.Church.

(5) Then, click on Save which is located at the bottom, right-hand corner of the form.

(6) You will again see the API summary screen. Click on the Users tab.

NOTE: If you do not see the API summary screen again, look at the top of the page for an error message. You might see the word "undefined" or a different message. "Undefined" mostly likely means that the name you chose was not unique. You can choose a different name. You can add to your name to make it unique.

For example: The name you chose was "PrayerGroup". This returned an error message. Try adding a number (such as PrayerGroup1) or another word (such as PrayerGroupMonday).

(7) Scroll up and down the Users dropdown list to find the account you have just created. Usually, it will be easy to find because most churches only have a few accounts.

(8) Select your new user account from the list of users.

(9) Now, click on the name of your new API user. This is the first item in the API User Account Details section. You will be brought to the API User's Information page.

(10) Click on the Services tab. You will see the list of API services.


(11) To allow full communication and functioning of all the Display.Church features, it is necessary to enable ALL the 13 services listed below:

Enabled services

Mandatory:

  • campus_list

  • campus_profile

(identifies either Calendar or Groups data across your church)

Calendar:

  • event_profiles

  • group_profiles

  • public_calendar_listing

(pulls in all events from your public, groups, and individual calendars)

Groups:

  • area_detail

  • area_list

  • group_profiles

  • group_type_detail

  • group_type_list

(pulls in basic information about your groups)

RSVP:

  • add_individual_to_event

  • individual_id_from_login_password

(used when a person RSVPs to an event)

Private Events:

  • individual_calendar_listing

(pulls in private events)

Locate each service in the dropdown list.

Click on the box to the left of the service name to enable the service.

(12) Make sure you have a check mark next to the 13 services.

(13) Click Save which is located at the bottom, right-hand corner of the Services list. Alternatively, look at the Actions menu in the upper, right-hand corner and choose Save this API User.

The screen will refresh to the API summary screen. You have now successfully created a new API user.

Look at the line ‘Your API URL’. Make a note of your account name. This is the word between the forward slash and the ‘.ccbchurch’. For example, in the URL “https://multisite.ccbchurch.com/api.php”, the account name is “multisite”.


OLD VERSION

Scroll all the way over to the right and click on Settings which is the Gear Icon. 


If you see the API option, you have the needed permission to continue.


 If you do not see this option or are unsure about anything, be in touch with your database administrator.

Click on the API option. You will see the API summary screen. 

Click on Add a new API User which is located to the right of the summary screen. 

You will see the New API User form. Complete this form with the needed details. 

  • For the name, we recommend something simple such as ‘ccbevents’ (one word, no spaces). Your name must be unique. In other words, it must be different from any name already in the system.

  • For the username, we recommend using the same ‘ccbevents’ (one word, no spaces). 

  • Your password should be something which is difficult to guess. Please note that CCB passwords can only be characters and numbers (no special characters) with at least one number. 

  • Make a note of your API username and password. You will need them later.

  • The Primary Organization Contact Information is optional. If you wish, you can use the Display.Church contact information, but again, this is totally optional.

Then, click on Save which is located at the bottom, right-hand corner of the form.

You will again see the API summary screen. Click on the Users tab.

NOTE: If you do not see the API summary screen again, look at the top of the page for an error message. You might see the word "undefined" or a different message. "Undefined" mostly likely means that the name you chose was not unique. You can choose a different name. You can add to your name to make it unique.

For example: The name you chose was "PrayerGroup". This returned an error message. Try adding a number (such as PrayerGroup1) or another word (such as PrayerGroupMonday).

Scroll up and down the Users dropdown list to find the account you have just created. Usually, it will be easy to find because most churches only have a few accounts. 

Select your new user account from the list of users. Now, click on the name of your new API user. This is the first item in the API User Account Details section.

You will be brought to the API User's Information page.

Click on the Services tab.

Enabled services

Mandatory:

  • campus_list

  • campus_profile

(identifies either Calendar or Groups data across your church)

Calendar:

  • event_profiles

  • group_profiles

  • public_calendar_listing

(pulls in all events from your public, groups, and individual calendars)

Groups:

  • area_detail

  • area_list

  • group_profiles

  • group_type_detail

  • group_type_list

(pulls in basic information about your groups)

RSVP:

  • add_individual_to_event

  • individual_id_from_login_password

(used when a person RSVPs to an event)

Private Events:

  • individual_calendar_listing

(pulls in private events

To allow full communication and functioning of all the Display.Church features, it is necessary to enable ALL the services.

Locate each service in the dropdown list.

Click on the box to the left of the service name to enable the service. 

Make sure you have a check mark next to the 13 services, and then, click Save which is located at the bottom, right-hand corner of the Services list.

You will see the API summary screen. You have now successfully created a new API user.

Look at the line ‘Your API URL’. Make a note of your account name. This is the word between the forward slash and the ‘.ccbchurch’. For example, in the URL “https://multisite.ccbchurch.com/api.php”, the account name is “multisite”. 

At this point, you have the three pieces of information needed to register your new API user with Display.Church: your API username, your API password, and your account name.

Did this answer your question?