top of page

API Integration

CC API.png

OVERVIEW

This project involved the use of REST API endpoints in Constant Contact to automate account creation (Constant Contact account) when FCA staff filled out a form in RegFox. This process had been manual for many years, performed by FCA's support staff, which could delay account access for staff based on the amount of volume of calls and support tickets being worked on. The goal of this project was to give FCA staff instant account creation/access and lessen the work load on support staff.​

​

​MY ROLE:

API Development and Integration

APPLICATIONS AND ENDPOINTS

Applications

The two applications that needed to be connected together were RegFox (form submission with account creation information) and Constant Contact. 

orig.png
CC_release_thumb.png

Endpoint

The endpoint access that was needed was through Constant Contact's v3 API. All account actions needed (account creation and account activation/billing update) were found under the "Partner Account" endpoint. This endpoint required basic authentication for endpoint access.

Screenshot 2024-10-24 at 12.45_edited.jp

API SETUP

Automation Trigger

Since account creation was requested from a RegFox form submitted by users, the trigger for the automation would be whenever a new submission was received. Because of the need for this instant trigger and the need for API endpoints (see below) Zapier was chosen to run the automation.

zapier-vector-logo-2023.png

Custom Integration

To access the "Partner Account" endpoint to begin an API session for each form submission, a custom integration was designed through Zapier's developer platform. This allowed for custom actions (account creation and account activation) to be set up to pass along the form submission data needed. See the JSON below for passing along the required fields in the body of the API request. 

image_edited.jpg

API Flow

The final API flow resulted in account creation and activation in Constant Contact upon submission of the RegFox form. Below is a diagram of the API calls with the passed back outputs needed in the next actions.

Screenshot 2024-10-24 at 1.45_edited.jpg
dGX Hi-Def.png

© 2024 by Michael de Graaf

bottom of page