Cyberimpact API

Name: Cyberimpact API API
Brand: Cyberimpact API
Availability: InStock

✓ Official Vendor SpecMarketingEmail Marketingbearer9 EndpointsREST

For Agents

Sync contacts into Cyberimpact groups, retrieve mailing history, and list email templates for CASL-compliant Canadian email marketing.

Quickstart

Get started with Cyberimpact API 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 a Cyberimpact group"

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

Capabilities

What an agent can do with Cyberimpact API API.

Create or update a Cyberimpact contact and assign it to one or more permission-based groups

List every group in the account and read membership counts before targeting a send

Fetch a single contact record by contactId to confirm subscription status before resending

Retrieve historical mailings sent from the account for reporting or audit logs

GET STARTED

Start building with Cyberimpact API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cyberimpact API API for, with concrete tasks.

★ CASL-Compliant Lead Sync

Push newly captured leads from a website form or CRM into Cyberimpact while preserving consent metadata. The API's POST /contacts endpoint creates or updates a contact in a single call and assigns group membership, so agents can keep the marketing list in sync with the source of truth without touching the dashboard. Ideal for Quebec-based businesses that need permission audit trails.

POST a new contact with email, firstName, lastName, and a permission timestamp to /contacts and assign it to group ID 12345.

Mailing Performance Audit

Pull the list of mailings sent from a Cyberimpact account into a reporting tool or BI dashboard. The GET /mailings endpoint returns send history that an agent can join with internal CRM data to attribute pipeline back to specific campaigns, supporting quarterly marketing reviews.

Call GET /mailings and filter the response to mailings sent in the last 90 days, then summarise by month.

Unsubscribe Cleanup Workflow

Process an inbound unsubscribe request received via support channels. The agent looks up the contact via GET /contacts, confirms identity with GET /contacts/{contactId}, and then calls DELETE /contacts/{contactId} to remove them, all without a marketer needing to log into the Cyberimpact UI.

Search /contacts for email 'jane@example.com', then DELETE /contacts/{contactId} once a single match is confirmed.

Agent-Driven Template Selection

An AI agent composing a newsletter via Jentic queries the Cyberimpact template list, picks the brand-approved layout that matches the campaign theme, and reports the template ID back to a human reviewer. Removes the need for a marketer to manually copy template IDs from the UI into a brief.

Call GET /templates, filter for templates whose name contains 'Newsletter', and return the most recently modified template ID.

Key Endpoints

9 endpoints — cyberimpact is a canadian email marketing platform built around casl-compliant permission management.

METHOD

PATH

DESCRIPTION

POST

/contacts

Create or update a contact

GET

/contacts

List all contacts

DELETE

/contacts/{contactId}

Delete a contact

GET

/groups

List all groups

GET

/mailings

List mailings

GET

/templates

List email templates

POST

/contacts

Create or update a contact

GET

/contacts

List all contacts

DELETE

/contacts/{contactId}

Delete a contact

GET

/groups

List all groups

GET

/mailings

List mailings

GET

/templates

List email templates

Why though Jentic?

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

Credential isolation

The Cyberimpact bearer token is stored encrypted in the Jentic vault. Agents receive a scoped runtime credential when they execute an operation, so the raw token never lands in prompt history, logs, or the agent's working memory.

Intent-based discovery

Agents search Jentic for 'add a contact to a Cyberimpact group' or 'list Cyberimpact mailings' and Jentic returns the matching operation with its full input schema, so the agent can call POST /contacts directly without reading the developer documentation.

Time to first call

Direct Cyberimpact integration: roughly half a day for token generation, error handling, and testing. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Mailchimp Marketing API

Larger global email marketing platform with broader campaign automation surface than Cyberimpact.

Choose Mailchimp when the audience is global and the workflow needs automation journeys, A/B testing, or e-commerce attribution that Cyberimpact does not expose.

Alternative

Constant Contact API

North American email marketing platform with a similar SMB target market and richer event marketing features.

Choose Constant Contact when the user already runs events or needs landing pages bundled with email; choose Cyberimpact when CASL compliance and Canadian data residency are the priority.

Complementary

HubSpot Marketing Events API

Pairs CRM-driven marketing event tracking with Cyberimpact's email send list.

Use HubSpot to capture lead and event data, then sync the resulting contacts into Cyberimpact groups for the actual newsletter send.

FAQs

Specific to using Cyberimpact API API through Jentic.

What authentication does the Cyberimpact API use?

The Cyberimpact API uses HTTP Bearer authentication. You generate a personal API token in the Cyberimpact account settings and pass it as Authorization: Bearer <token> on every request to api.cyberimpact.com/v3. Through Jentic, the bearer token is held in the encrypted vault and the agent receives a scoped runtime credential, so the raw token never enters the model context.

Can I create CASL-compliant contacts with the Cyberimpact API?

Yes. POST /contacts accepts the contact email, name fields, and the group IDs the contact should be added to. Cyberimpact treats group membership as the consent record, so the contact you create through the API is treated the same as a contact opted in via a Cyberimpact form for CASL purposes.

What are the rate limits for the Cyberimpact API?

Cyberimpact does not publish hard rate limits in the OpenAPI spec, but the developer documentation recommends keeping bulk imports below a few requests per second and processing large contact loads in batches. Treat sustained traffic above 10 requests per second as a risk for throttling.

How do I add a new subscriber through Jentic?

Install the SDK with pip install jentic, then run an agent with the search query 'add a contact to a Cyberimpact group'. Jentic returns the POST /contacts operation with its input schema, so the agent can call it directly with the email, name, and group ID without browsing API docs.

Does the Cyberimpact API support sending a new mailing?

No. The available endpoints expose mailings for read-only listing only. To trigger a new send you still need to compose and dispatch the campaign in the Cyberimpact UI; the API is scoped to contact, group, and reporting workflows.

Is the Cyberimpact API free?

API access is included with any paid Cyberimpact plan. Cyberimpact also offers a free tier capped at 250 contacts which includes API access, so small lists can be managed via the API at no cost.