Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / Dynosend API
Dynosend API logo

Dynosend API

68
AI ReadinessAI-Aware (B+)68/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticCommunicationsEmail Deliverybearer17 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send transactional emails, manage contacts and audiences, control campaign lifecycle (start, pause, resume), record customer events, and check or update the deliverability blacklist.

Use for: I want to send a transactional welcome email through Dynosend, Add a new contact to an audience with a custom tag, Pause an active campaign because of a deliverability issue, Check whether an email address is blacklisted before adding it

Not supported: Does not provide template authoring, SMS or voice sending, or detailed deliverability analytics dashboards - use for contact management, campaign control, and email transactional sends only.

Jentic publishes the only available OpenAPI specification for the Dynosend API, keeping it validated and agent-ready. Dynosend is an email marketing and transactional messaging platform that exposes endpoints for managing audiences and contacts, controlling campaign lifecycle, sending transactional messages, recording customer events, and maintaining a deliverability blacklist. The API is built around the audience-and-contact model used by marketing teams running drip campaigns and event-triggered transactional sends from one provider.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Dynosend API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dynosend 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.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdynosend.com%2Fdynosend" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdynosend.com%2Fdynosend" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Dynosend API.

Send a transactional message to an individual recipient with template content

Add, update, subscribe, unsubscribe, or delete contacts within an audience

Tag contacts to drive segmented campaigns and dedupe with the duplicate-finder endpoint

Start, pause, and resume campaigns to control marketing send windows

Record customer events that trigger event-based automations and journeys

Check whether an email address is on the deliverability blacklist before sending

Add an email address to the blacklist to suppress future sends

Use Cases

Patterns agents use Dynosend API for, with concrete tasks.

★ Transactional Welcome and Receipt Emails

When a user signs up or completes a purchase, the application calls /transactional with the template ID, recipient details, and merge data so Dynosend renders and sends the email. This separates transactional sends from marketing campaigns and keeps deliverability isolated per stream.

POST /transactional with template_id, recipient email, and merge variables to send a welcome email to a newly registered user

Event-Triggered Marketing Automation

An e-commerce app posts customer events ('cart_abandoned', 'order_completed') to /events, and Dynosend automations route those into the appropriate sequence (recovery, upsell). This pattern replaces ad-hoc trigger code in the application with a single event sink that the marketing team controls.

POST /events with event_name 'cart_abandoned', the contact email, and product details so the abandoned-cart automation picks it up

Audience Hygiene with Tagging and Blacklisting

An audience-management workflow finds duplicates via /contacts/duplicate, tags engaged contacts with PATCH /contacts/addtag, and pushes hard-bounced addresses onto the blacklist via /blacklist/add. Combined, these endpoints keep the active audience clean without manual list edits.

GET /contacts/duplicate to find duplicates, then POST /blacklist/add for each hard-bounced address before the next campaign send

Agent-Driven Campaign Control via Jentic

When a deliverability issue spikes, an AI ops agent calls Dynosend through Jentic to pause active campaigns, then resumes them once health metrics recover. The agent searches Jentic for 'pause a Dynosend campaign', loads the operation, and executes it - the bearer token never enters the agent context.

Use Jentic to search 'pause a Dynosend campaign', load the operation for POST /campaigns/pause, and execute it for the affected campaign ID

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for the dynosend api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/transactional

Send a transactional message

POST

/contacts

Add a new contact to an audience

PATCH

/contacts/update

Update contact data

POST

/events

Send a customer event for automation triggers

POST

/campaigns/start

Start sending a campaign

POST

/campaigns/pause

Pause an active campaign

POST

/blacklist

Check whether an email is blacklisted

POST

/blacklist/add

Add an email to the blacklist

POST

/transactional

Send a transactional message

POST

/contacts

Add a new contact to an audience

PATCH

/contacts/update

Update contact data

POST

/events

Send a customer event for automation triggers

POST

/campaigns/start

Start sending a campaign

POST

/campaigns/pause

Pause an active campaign

POST

/blacklist

Check whether an email is blacklisted

POST

/blacklist/add

Add an email to the blacklist

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

D

Dynosend API

- AI-Aware (B+)
68/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
48
AI-Readiness & Agent Experience
94
Agent Usability
60
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

48

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
38%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

60

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1
60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Dynosend by hand means setting up its bearer auth against the /api/v2 host and coding the separate contact, event, campaign, and transactional calls yourself. Through Jentic you install once, import Dynosend from the API Directory, store the token once, and your agent calls it.

Permission scoping

Dynosend addresses contacts and campaigns through the request body rather than the URL path, so scope your agent to the operations it needs, such as sending a transactional email or creating a contact. Campaign control like starting or pausing, and blacklist changes, stay out of the allowed set unless you add them.

Credential isolation

Your Dynosend token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a transactional email' or 'pause a campaign', and Jentic returns the matching Dynosend operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

E-goi Marketing API

→

Multi-channel marketing automation (email, SMS, push, voice) with broader scope than Dynosend's email-first surface

Choose E-goi when the campaign needs SMS or push channels alongside email; choose Dynosend for email-focused workflows

Complementary

DynTube API

→

Embed DynTube-hosted videos in Dynosend transactional or campaign emails

Pick DynTube when the email needs a hosted video link rendered alongside Dynosend send logic

Complementary

DynaPictures API

→

Generate personalised banner images for use inside Dynosend transactional or campaign emails

Use DynaPictures upstream of Dynosend to render the per-recipient image, then send via /transactional

FAQs

Specific to using Dynosend API through Jentic.

Why is there no official OpenAPI spec for the Dynosend API?

Dynosend does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Dynosend API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Dynosend API use?

The API uses bearer token authentication - pass your Dynosend API key in the 'Authorization: Bearer <token>' header. Through Jentic, the token is held in the vault and replaced with a scoped execution token at call time.

Can I send transactional emails with the Dynosend API?

Yes. POST /transactional accepts a template ID, recipient details, and merge variables and sends the email through Dynosend's transactional stream, separate from campaign sends. This isolates transactional deliverability from marketing volume.

What are the rate limits for the Dynosend API?

The OpenAPI spec does not declare a numeric rate limit. Dynosend applies plan-based send and event quotas - high-volume callers should batch contact updates via /contacts and rely on /events for trigger fan-out rather than issuing many transactional calls.

How do I trigger a marketing automation through Jentic?

Run pip install jentic, search for 'send a customer event to Dynosend', load the operation for POST /events, then execute it with the event name, contact email, and event payload. Dynosend's automations subscribed to that event will fire automatically.

Can I check if an email is blacklisted before sending?

Yes. POST /blacklist returns whether an address is on the suppression list, and POST /blacklist/add adds a new address to the list. Use this before importing a new audience to avoid sending to known bounces.

Can I limit what my agent is allowed to do with the Dynosend API?

Yes. Because you run Jentic One yourself, your own rules decide which Dynosend operations and credentials the agent can use, so you can allow only what a task needs, such as sending a transactional email via POST /transactional or creating a contact via POST /contacts. Dynosend addresses contacts and campaigns through the request body rather than the URL path, so you scope by operation rather than by resource ID. Campaign control such as POST /campaigns/start and POST /campaigns/pause, and blacklist changes via POST /blacklist/add, stay outside the allowed set unless you add them.

GET STARTED

Start building with Dynosend API

Explore with Jentic One
View OpenAPI Document