Email marketing
Constant Contact in your product and your AI agents, through one API
The Constant Contact toolkit covers contacts, contact lists, and email campaigns with their activities, scheduling and sending statistics. Through Connect your product or AI agent calls them with one endpoint, while Connect stores and renews the OAuth credentials and logs every execution.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/constant_contact_create_contact/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"create_source": "Account"
}
}How it works
From a connected customer to the first Constant Contact call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Constant Contact account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Constant Contact.
Add subscribers on signup
A SaaS creates a contact in the customer's account when someone signs up, and handles the 409 when the email already exists.
Send a campaign from your app
A product creates a draft campaign with custom HTML, sets its lists and schedules the sending.
Report on campaign results
An AI agent reads the stats of a sent campaign, such as opens, clicks and bounces, and summarizes them for the account owner.
Tools
12 Constant Contact tools
- List contactsGETLists the contacts of the account, leaving deleted ones out by default, optionally filtered by email, list, status or date. The response has contacts and, when there are more, _links.next.href with the cursor of the next page.
- Create contactPOSTCreates a contact and returns it with its contact_id. Send create_source and at least email_address, first_name or last_name. An email address that already exists in the account answers 409.
- Update contactPUTUpdates a contact by replacing its core fields: email_address, names, job_title, company_name, birthday and anniversary left out become empty, so send the current values too, from List contacts. Subresources left out are kept, and one that is sent replaces the current one.
- List contact listsGETLists the contact lists with their list_id, name and description. An account has up to 1000 lists, and one page brings up to 1000.
- Create contact listPOSTCreates an empty contact list and returns it with its list_id. A name already used by another list answers 409.
- List email campaignsGETLists the email campaigns, most recently updated first, with campaign_id, name, type and current_status, including the deleted ones (Removed). Up to 500 per page; reach older ones with before_date and after_date. The activity ids come from Get email campaign.
- Get email campaignGETReturns one email campaign with its name, current_status and campaign_activities. The campaign_activity_id with role primary_email is the one the activity tools take.
- Create email campaignPOSTCreates a draft email campaign with custom HTML content and returns it with campaign_activities, where the primary_email activity is. To send it, set the lists with Update email campaign activity and then use Schedule email campaign activity.
- Get email campaign activityGETReturns an email campaign activity: sender, subject, preheader, contact_list_ids or segment_ids, format_type and current_status. html_content and physical_address_in_footer come back only when asked in include.
- Update email campaign activityPUTUpdates the primary_email activity of a campaign in DRAFT or DONE status. It replaces the properties: send the current sender, subject, preheader and lists from Get email campaign activity along with the changes, because what is left out is cleared. html_content and physical_address_in_footer are kept when not sent.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/constant_contact, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
Questions about the Constant Contact toolkit
Do I need to build against the Constant Contact API?
No. Connect ships 12 Constant Contact tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Constant Contact account?
With the mode the toolkit accepts: OAuth with your product's app. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
