Finding your way around the V3 Developer Portal

The V3 API Developer Portal comprises three distinct components:

  • API Docs - home to conceptual, procedural, API how-to’s with examples and best practices
  • API Reference - describes each endpoint and method in detail with a Try feature to make real API calls to your CTCT account
  • My Applications - self-service portal to sign up for an account, register your application, generate and manage API keys

API Docs

API Docs is the home to user guides for each endpoint grouping (Contacts, Lists, etc.). The user guides provide:

  • a conceptual overview of each API resource
  • detailed use cases illustrating common sets of tasks with step-by-step instructions and code samples in multiple languages
  • API best practice guidelines, along with guidelines on what to avoid
  • Detailed explanation of the V3 API OAuth 2.0 implementation and how to implement Client and Server OAuth flows in your integrations

Code Samples

Code samples are used in the API Docs to provide examples of a properly constructed API call in a specific language. Code samples are provided in multiple languages: cURL, JAVA and PHP. The sample do not specify or rely on a specific version or framework, and do not call specific libraries.

You will have to modify the examples to make them work in your environment.
Code Samples in multiple languages

At the bottom of most API Docs pages is a set of Tags that link to curated lists of related topics.

Tags that link to related topic list

API Reference

The API Reference provides documentation describing each V3 API endpoint with the following details:

  • Supported methods
  • All query and path parameters
  • Response type
  • Response codes and messages
  • For PUT & POST methods - sample request payloads and JSON schema model
  • For all methods - sample response payloads and JSON schema model
  • Try button button for making an API call in the API Reference.

Body and Response Schema

The body (PUT, POST) and response JSON schema for each endpoint and method combination are provided in the right-hand column of the API Reference.

Endpoint/method schema example

The schema provides detailed definitions for the object and all of its properties to which the endpoint provides access. The schema provides the following for each object & property:

  • name
  • type - string, boolean, array, integer

    For string type - List of enumerated values (Enum), Max Length (maximium number of characters) as applicable

  • description - explains how the object or property is used, including any associated business logic

You can download the entire V3 API schema in YAML format here.

Making API Calls

You can make V3 API calls to your Constant Contact account from the API Reference for each endpoint and method available.

To make a call:

  1. Click Oauth button to authenticate and grant access to the API Reference.
  2. If you’re not logged in to your account, the log in screen displays. Log in to your Contant Contact account.
  3. Grant access to the API Tester app. Once you’ve granted access, Signout button appears on the button.
  4. To make a GET call:

    1. For a GET call, select the parameters to include in your call as desired, from the Parameters section
    2. Click Try button to send the request.
    API Tester call results panel

    An overlay displays the results of the API call.

    API Tester call results panel
  5. To make a PUT or POST call:

    1. Click the Body Sample to populate the body field with that JSON example and modify it as needed, or use your own request payload.
    API Tester POST request
    1. Click Oauth button to authenticate if needed.
    2. Click Try button to send the request.

My Applications

My Applications is where you register and manage your applications in our V3 API ecosystem.

Developers are limited to a total of 50 active and deactivated apps.

Getting Started

You need to have a Constant Contact account to use My Applications. Clicking My Applications brings you to the log in or sign up page. If you don’t already have a Constant Contact account, you can sign up for one here. Otherwise, log in with your existing Constant Credentials. Once you are logged in, the My Applications page displays.

Registering an Application

Register your application to get an API key, client_secret, and set a redirect_uri.

  1. Click New Application button to register your application. The New Application overlay displays.
  2. Enter the name of your application, up to 50 characters. Users will see this name when they grant it access to their Constant Contact account.
  3. Click Save. The App details page displays.
Application details screen

The App details page shows current information about your app, including:

  • API key
  • Redirect URI
  • App Name
  • App logo URL
  • Description

You can update any information on this page except for the API key value.

Generating a Client Secret

You need a client_secret in addition to the API key and redirect uri to implement OAuth2.0 authorization flows for your app. We only show you the client secret once when it is initially created. Make sure you copy and save it in a secure place.

If you have forgotten or lost your secret, we do not provide it to you after its initial creation. You can only generate a new secret.
  1. Click New Application button generate and display the client secret.
  2. The disclaimer appears, letting you know you’ll have to update your code to use the new secret if a client secret was previously created for your app. Click Cancel if you do not want to generate a new secret, or click Generate Secret.
  3. The App Secret overlay displays.

    App secret displays

    Copy the secret to your clipboard and store it in a secure location.

  4. Click Close.

Redirect URI

When you register your app, we provide a default redirect URI of https://localhost. You can change it or add additional redirect URIs on the App details page. Your app must have at least one redirect URI.

What Your Users Will See

The Public Description section of the App details page has the three properties that your users will see when initially interacting with and granting access to your app in the OAuth flow:

  • App Name (required)
  • App Logo URL
  • Description