What we do
Tools
Industries
Department
How we workLet's talk →
Home/Constant Contact
Constant Contact

The Constant Contact API (v3): OAuth First, Then Contacts and Lists

The API key Constant Contact gives you won't make a call on its own. In v3 it's your application's client ID, and every request against an account also needs an OAuth2 access token that the account's user granted. Once that's in place, contacts, lists and campaigns are straightforward. Here's the setup, the limits, and the sync mistakes worth avoiding.

Where Constant Contact stops

Where does the list come from? New customers, orders and sign-ups don't land on the right list automatically.

Stuck on Constant Contact? Let's solve it →
Your first Constant Contact API call

Register an application in the V3 developer portal. Its API key is the client ID. If the flow you pick uses a client secret, copy it when it's generated: it's only shown once.

Developer portal My Applications

Pick an OAuth2 flow: Authorization Code for a server app, PKCE for a browser or mobile app with no secret, or Device Authorization for something with no browser. Ask for contact_data (and campaign_data if you'll touch campaigns), plus offline_access to get a refresh token.

Swap the code fast and call the API. The authorization code expires after 300 seconds. Exchange it at authz.constantcontact.com, then send Authorization: Bearer <token> to https://api.cc.email/v3/.

Rotating or long-lived refresh tokens?

You choose when you register the app. Access tokens expire within a day either way, so this is about how the connection stays signed in.

Rotating

What Constant Contact recommends

  • Every refresh returns a new access token and a new refresh token.
  • Save the new refresh token straight away. The next refresh needs it.
  • Two workers refreshing at the same moment can leave one holding a token that's already been replaced. Let one process own refreshing.
Long-lived

Simpler, with a bigger downside

  • The refresh token stays the same, so storage is simpler.
  • A leaked token stays useful for longer.
  • Only worth it when you can't reliably save a new token after every refresh.

Use rotating, refresh only when the access token is expired or about to be, and keep the token store in one place.

Constant Contact API rate limits

Go over either limit and you get HTTP 429. The error key tells you which one: throttled for the per-second limit, quota_exceeded for the daily one. Some endpoints have stricter limits of their own.

Limit Value Build for it by
Per second 4 requests Queuing calls instead of firing them in parallel. A backfill of a few thousand contacts one call at a time is slow but safe.
Per day 10,000 requests per API key, reset at 00:00 UTC Remembering it's counted per API key, which is per application. Every account connected through the same app draws on the same 10,000.
Large loads Use the bulk activity endpoints Sending imports as one bulk job rather than thousands of single-contact calls, then checking the activity's status for errors.

Contact sync mistakes that cause real trouble

Using sign_up_form for CRM updates

How you'll know: People who unsubscribed start getting campaigns again after a sync run.

Fix: POST /contacts/sign_up_form creates or updates a contact and sets their permission to explicit, which can re-subscribe someone. Constant Contact says to use it only when the person has just given consent. For syncs, find the contact and update it instead.

New contacts never receive anything

How you'll know: They're in the list, but campaign reports never include them.

Fix: With Confirmed Opt-In switched on, new signups arrive as pending confirmation until they click the confirmation email. That's expected. Check the setting before assuming the sync is broken.

The app works for you and nobody else

How you'll know: Your own account connects fine, but a client's account can't authorize the app.

Fix: New applications are private: only the user who created them can grant access. Contact Constant Contact to have the app approved for other accounts.

A connection that dies overnight

How you'll know: Calls start failing with 401 the morning after a deploy or a server restart.

Fix: The access token expired and the new refresh token wasn't saved. Store each refreshed token before using it, and alert someone if a refresh fails.

What a Constant Contact API integration is usually for

Constant Contact's own automation reacts to what it can see: someone joins a list, a date arrives, an email is opened or clicked. It can't see an order in your store, an invoice paid in QuickBooks or a stage change in your CRM. The API is how those reach it, so a new customer, a booking or a signup lands on the right list the moment it happens, instead of after the next CSV import.

Lists also need to follow status. When a contact becomes a customer, reaches a loyalty tier or cancels in another system, the sync moves them between lists so the next campaign goes to the right people. Our Constant Contact segmentation page covers building those groups. Data can flow back too: opens and clicks from campaign reporting can sit on the CRM record, so a rep sees whether someone read the last email before calling. For Salesforce teams, see Constant Contact and Salesforce.

n-frames builds and runs these Constant Contact API syncs: OAuth that refreshes itself, calls paced inside the limits, and contact updates that leave each person's email permission exactly as they set it.

What this looks like in practice

Community Fitness Studio

Constant Contact lists, signups from three places.

The problem Members who joined on the website, through the booking tool or at the front desk were put on lists by hand, and some were never added at all.

Whichever of the three a new member signs up through, the matching Constant Contact contact and list membership is created or updated on its own, with no export in between.

Questions people ask

What is Constant Contact used for?

Building and sending email campaigns, managing contact lists, and running event promotions and simple e-commerce marketing. It's aimed at small businesses that want something simpler than an enterprise marketing platform.

How much does Constant Contact cost, and is there a free version?

Pricing depends on how many contacts you email and which plan you choose, and it changes often enough that Constant Contact's own pricing page is the place to check. API access itself isn't sold separately: you register an app in the developer portal.

Is Constant Contact a CRM?

No. It sends and tracks email campaigns. Some plans add light contact management, but it has no sales pipeline or support tickets, so most businesses pair it with a separate CRM and sync the two.

Does Constant Contact have an API?

Yes. The current version is the v3 REST API at api.cc.email/v3, covering contacts, lists, campaigns and reporting. Calls are authorized with OAuth2 tokens, and the app's API key acts as its client ID.

Does the Constant Contact API use an API key or OAuth?

Both, in different roles. The API key identifies your application. To read or change an account's data you also need an OAuth2 access token granted by a user of that account, through the Authorization Code, PKCE or Device flow.

What are the Constant Contact API rate limits?

4 requests per second and 10,000 requests per day per API key, with the daily count resetting at midnight UTC. Going over returns HTTP 429, marked throttled or quota_exceeded.

How do I remove the Constant Contact logo from my emails?

The logo in the footer is an account setting, not part of the email design. It sits in your account's email settings, and whether you can turn it off depends on your plan.

Who can build a Constant Contact API integration for us?

n-frames does this work: the app registration and OAuth setup, a sync from your booking tool, store or CRM that respects consent, and monitoring that flags a failed token refresh or a run of 429s.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.