AppConnect V3

Name: AppConnect V3 API
Brand: AppConnect V3
Availability: InStock

★ Only Publicly Available SpecMarketingEmail MarketingapiKey10 EndpointsREST

For Agents

Create and update email contacts and lists so an agent can sync subscribers from a product backend into a Constant Contact-aligned email marketing list.

Quickstart

Get started with AppConnect V3 in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"add a contact to an email list"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with AppConnect V3 API.

Create and update contacts via /contacts and /contacts/{contact_id}

Manage email subscriber lists through /lists and /lists/{list_id}

Look up an individual contact by ID for personalisation

Bulk-list contacts with pagination for export jobs

Toggle list membership by re-PUTing the contact record

GET STARTED

Start building with AppConnect V3 API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for AppConnect V3, keeping it validated and agent-ready.

AppConnect V3 is a Constant Contact-aligned contacts and lists API exposing a small surface for syncing email subscribers and segment lists. The 10 endpoints cover contact CRUD on /contacts and list CRUD on /lists, with authentication via an Authorization header or x-api-key header. The API targets developers who need to push subscribers from a product backend into Constant Contact-style email marketing without integrating the wider Constant Contact platform.

Use Cases

Patterns agents use AppConnect V3 API for, with concrete tasks.

★ Product Sign-up to Email List Sync

Push newly registered product users into the marketing email list automatically by calling POST /contacts with the email and profile fields, then attaching the contact to the welcome-series list. This removes the daily CSV export-and-import that growth teams typically run when their product database lives separately from the email marketing tool.

On user registration, call POST /contacts with the email and name, then PUT the list membership to add them to the welcome-series list

Subscriber Profile Update

Keep email marketing personalisation fresh by updating contact metadata whenever the source-of-truth changes upstream. PUT /contacts/{contact_id} accepts the updated profile and the list-membership endpoint reflects subscription changes immediately, removing the lag that drives outdated merge fields in marketing emails.

On profile update event, call PUT /contacts/{contact_id} with the new fields and confirm the response reflects the updated metadata

List Membership Audit

Generate a weekly audit of which subscribers are on which lists by walking GET /lists and GET /contacts. The agent can compare list membership against the source-of-truth to catch drift — subscribers on a list they should not be on, or missing from a list they should be on — without manually exporting from the marketing UI.

List all lists via GET /lists, list contacts on each, and compare against the source-of-truth to flag drift in list membership

Agent-Driven Subscriber Management

Let an AI agent add or remove subscribers from email lists in response to natural-language requests by exposing AppConnect operations through Jentic. The agent searches for the right operation, loads the schema, and executes — never holding the API key, which carries write access to the entire contacts list.

Search Jentic for 'add a contact to an email list', load the POST /contacts schema, and execute with the email from the user's chat message

Key Endpoints

10 endpoints — appconnect v3 is a constant contact-aligned contacts and lists api exposing a small surface for syncing email subscribers and segment lists.

METHOD

PATH

DESCRIPTION

GET

/contacts

List contacts

POST

/contacts

Create a contact

GET

/contacts/{contact_id}

Fetch a specific contact

PUT

/contacts/{contact_id}

Update a contact

GET

/lists

List subscriber lists

POST

/lists

Create a list

GET

/lists/{list_id}

Fetch a list

GET

/contacts

List contacts

POST

/contacts

Create a contact

GET

/contacts/{contact_id}

Fetch a specific contact

PUT

/contacts/{contact_id}

Update a contact

GET

/lists

List subscriber lists

POST

/lists

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AppConnect V3 API keys are stored encrypted in the Jentic vault (MAXsystem). Agents call operations through scoped tokens — the raw key never enters agent context, which matters because the key grants write access to the full contact list.

Intent-based discovery

Agents search by intent (e.g. 'add an email subscriber' or 'list email lists') and Jentic returns the matching contacts or lists operations with their schemas, so the agent calls the right endpoint without studying the resource graph.

Time to first call

Direct AppConnect V3 integration: a few hours for auth and the contacts/lists CRUD. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Constant Contact API

Constant Contact's full API covers campaigns, segments, and email sending beyond the AppConnect V3 contacts/lists subset

Pick the full Constant Contact API when you need campaign sending; pick AppConnect V3 when subscriber sync is the only requirement

Alternative

Mailchimp API

Mailchimp offers a comprehensive marketing API across audience, campaigns, and automation

Use Mailchimp for end-to-end email marketing; use AppConnect V3 for narrow subscriber sync into a Constant Contact-aligned platform

Alternative

SendGrid Marketing Contacts API

SendGrid Marketing Contacts API focuses on contact storage and segmentation for email sending

Use SendGrid Marketing Contacts when you also send email through SendGrid; use AppConnect V3 to feed a Constant Contact list

FAQs

Specific to using AppConnect V3 API through Jentic.

What authentication does the AppConnect V3 API use?

API key in either the Authorization header or an x-api-key header. Through Jentic the API key is stored encrypted in the vault (MAXsystem) and never enters agent context — agents receive scoped access only.

Can I add an email subscriber with the AppConnect V3 API?

Yes. POST /contacts creates a contact with email and profile fields. To attach the contact to a specific list, use PUT /contacts/{contact_id} with the list membership populated, or update the list directly via PUT /lists/{list_id}.

What are the rate limits for the AppConnect V3 API?

The OpenAPI spec does not encode explicit rate limits. The underlying Constant Contact platform applies per-key throttling that returns HTTP 429 when exceeded — inspect response headers for live state and back off on 429.

How do I add a contact to an email list through Jentic?

Run pip install jentic, then search 'add a contact to an email list'. Jentic returns POST /contacts with its input schema — load the schema, populate the email and list ID, and execute. The agent never sees the API key.

How is AppConnect V3 different from the full Constant Contact API?

AppConnect V3 is a focused subset covering contacts and lists only — 10 endpoints rather than the full Constant Contact platform. Use it when subscriber sync is the only requirement; use the full Constant Contact API for campaigns, segments, and email sending.