L1 Api Cc Email AppConnect V3
★ Only Publicly Available OpenAPI DocumentMarketingEmail MarketingapiKey10 EndpointsREST
For Agents
Manage Constant Contact AppConnect contacts and contact lists: list, retrieve, create, update, and delete contacts and lists for email marketing campaigns.
Use for: I need to add a new contact to Constant Contact, I want to remove a contact who unsubscribed, List all my Constant Contact lists, Update the email address for an existing contact
Not supported: Does not handle campaign sends, email templates, or engagement reporting — use for AppConnect contact and list management only.
Jentic publishes the only available OpenAPI specification for AppConnect V3, keeping it validated and agent-ready. AppConnect V3 is Constant Contact's contact and contact-list management API, exposing CRUD on contacts and contact lists for marketing email programs. Authentication uses an x-api-key header alongside an OAuth 2.0-style Authorization header. The endpoints cover listing, retrieving, creating, updating, and deleting both contacts and lists.
Install Jentic One Beta
Connect the AppConnect V3 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AppConnect V3, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AppConnect V3 API.
Create contacts via POST /contacts with email, name, and custom fields for downstream campaigns
Update an existing contact via PUT /contacts/{contact_id} when CRM data changes
Delete a contact via DELETE /contacts/{contact_id} for opt-outs and right-to-be-forgotten requests
Create and update contact lists via POST /lists and PUT /lists/{list_id} for segmentation
List all contact lists in the account via GET /lists for audit and reporting
Retrieve a single contact's full record via GET /contacts/{contact_id} including list memberships
Use Cases
Patterns agents use AppConnect V3 API for, with concrete tasks.
★ Sign-Up Form to Email List
Push new sign-ups from a website form into a Constant Contact list. POST /contacts creates the contact and attaches it to the right list IDs returned from /lists. The same flow handles double opt-in by reading back the contact via GET /contacts/{contact_id} after creation to confirm subscription status.
On a new sign-up event, GET /lists to resolve the target list ID and POST /contacts with the email and list membership.
CRM-to-Email Sync
Mirror CRM contact changes into AppConnect so marketing email programs always have current data. When a CRM record updates, the agent looks up the AppConnect contact by ID and PUTs the new fields. Deletions from the CRM are mirrored with DELETE /contacts/{contact_id} to honour opt-outs.
On a contact.updated event from the CRM, PUT /contacts/{contact_id} with the new email, first name, and custom field values.
List Hygiene and Segmentation
Maintain clean, focused contact lists by creating segment-specific lists and pruning obsolete ones. POST /lists creates a new segment list, PUT /lists/{list_id} renames or repositions it, and DELETE /lists/{list_id} removes lists that are no longer used in any campaign.
POST /lists to create a 'Q3 webinar attendees' list and DELETE /lists/{list_id} on lists older than 12 months with no recent send history.
AI Agent Email Marketing Assistant
An assistant in a marketer's chat client adds contacts, creates segment lists, and prunes outdated entries on instruction. Through Jentic, the assistant calls AppConnect by intent without holding the OAuth token or x-api-key in the agent runtime.
On 'add jane@example.com to the newsletter list', search Jentic for 'create AppConnect contact' and POST /contacts with the resolved list ID.
Key Endpoints
10 endpoints — jentic publishes the only available openapi specification for appconnect v3, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/contacts
Create a contact
GET
/contacts
List contacts
PUT
/contacts/{contact_id}
Update a contact
DELETE
/contacts/{contact_id}
Delete a contact
POST
/lists
Create a contact list
PUT
/lists/{list_id}
Update a contact list
DELETE
/lists/{list_id}
Delete a contact list
POST
/contacts
Create a contact
GET
/contacts
List contacts
PUT
/contacts/{contact_id}
Update a contact
DELETE
/contacts/{contact_id}
Delete a contact
POST
/lists
Create a contact list
PUT
/lists/{list_id}
Update a contact list
DELETE
/lists/{list_id}
Delete a contact list
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AppConnect's x-api-key and OAuth tokens are stored encrypted in the Jentic MAXsystem vault. Jentic injects both headers at execution time so the agent never holds the raw credentials.
Intent-based discovery
Agents search by intent (e.g. 'add a Constant Contact contact' or 'create an AppConnect list') and Jentic returns the matching operation with its input schema.
Time to first call
Direct integration: 1 day for OAuth setup, dual-header auth, and contact modelling. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AppConnect V3 API through Jentic.
Why is there no official OpenAPI spec for AppConnect V3?
Constant Contact does not publish a stable OpenAPI specification for AppConnect V3 outside of SwaggerHub. Jentic generates and maintains this spec so that AI agents and developers can call AppConnect V3 via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AppConnect V3 API use?
AppConnect V3 expects two headers: x-api-key for the application identifier and Authorization for the OAuth 2.0 access token issued to the user. Through Jentic, both are stored encrypted in the MAXsystem vault and injected per request.
Can I add a contact to an existing list with the AppConnect V3 API?
Yes. POST /contacts accepts list memberships as part of the contact body, and PUT /contacts/{contact_id} updates list membership for an existing contact. Use GET /lists to resolve the right list ID first.
How do I delete a contact through Jentic?
Search Jentic for 'delete an AppConnect contact'. Jentic returns DELETE /contacts/{contact_id} with its schema. Provide the contact ID and Jentic executes the call using your stored credentials.
What are the rate limits for the AppConnect V3 API?
Per-account rate limits aren't exposed in the public spec. Refer to Constant Contact's developer portal for current ceilings before scaling, and contact webservices@constantcontact.com for higher allocations.
Can I create a new contact list with the AppConnect V3 API?
Yes. POST /lists creates a new contact list, returning the list ID you can then attach contacts to via POST /contacts or PUT /contacts/{contact_id}.
GET STARTED