For Agents
Sync contacts into Cyberimpact groups, retrieve mailing history, and list email templates for CASL-compliant Canadian email marketing.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cyberimpact API, 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.
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 | shStep 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.
What an agent can do with Cyberimpact 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
GET STARTED
Use for: I need to add a new subscriber to a Cyberimpact group, Find all contacts that exist in a specific group, Retrieve the list of mailings sent in the last quarter, List all email templates available in the account
Not supported: Does not handle SMS, push notifications, or campaign send dispatch — use for Cyberimpact contact, group, and mailing-history management only.
Cyberimpact is a Canadian email marketing platform built around CASL-compliant permission management. The API exposes nine endpoints across groups, contacts, mailings, and templates so agents can sync contact lists, fetch sent mailing history, and read template metadata without using the dashboard. It targets small businesses sending opt-in newsletters, with bilingual French/English support and resident Canadian data hosting.
Retrieve historical mailings sent from the account for reporting or audit logs
List available email templates so an agent can pick a brand-approved layout for a campaign
Delete a contact by contactId to honour an unsubscribe or right-to-erasure request
Patterns agents use Cyberimpact 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.
9 endpoints — cyberimpact is a canadian email marketing platform built around casl-compliant permission management.
METHOD
PATH
DESCRIPTION
/contacts
Create or update a contact
/contacts
List all contacts
/contacts/{contactId}
Delete a contact
/groups
List all groups
/mailings
List mailings
/templates
List email templates
/contacts
Create or update a contact
/contacts
List all contacts
/contacts/{contactId}
Delete a contact
/groups
List all groups
/mailings
List mailings
/templates
List email templates
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Cyberimpact 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.