Do I need Multiple APIs for our CMS

New Member

Do I need Multiple APIs for our CMS

We are developing a CMS-type product for a particular industry that will have layouts, features and functions that are specific to the the users in that industry.  Potentially there will be somewhere between 200 - 1,000 different organizations in this industry that will be using the CMS.  Each organization will use the CMS to setup their own discrete website.  The websites will be hosted on our hardware but for all purposes, each website will be a completely independent entity.  We want to use Constant Contact as the email engine and have been looking at the API requirements.


The question is:  do we need a separate API for each website that is created using our CMS or do we need only one API for all websites.


If it is the latter, how would this be configured as such as scenario is not clear from the documentation

Honored Contributor

Re: Do I need Multiple APIs for our CMS

Hello Andrew,


The way Constant Contact works with API keys is that an API key represents an application rather than an account. So you can create a single API key and use it to access a much much greater number of accounts as long as proper authentication is provided for each account.


In addition, with the scale you are looking at, it might be worth your time for your organization to look into our AppConnect partner program. You can find more information on that here:


if you have any more questions, please feel free to reply to this thread and I will be happy to help!



Elijah G.

API Support Specialist

Elijah G.
API Support Engineer
Developer Portal

View API documentation, code samples, get your API key.

Constant Contact would like to hear from you

We want to hear from customers like you about your favorite features and how they have helped your business or organization. Tell us by answering a few questions in...

Read More