Dynosend API

Name: Dynosend API
Brand: Dynosend API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail Deliverybearer17 EndpointsREST

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.

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.

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 | sh

Step 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 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

GET STARTED

Start building with Dynosend API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

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

Credential isolation

The Dynosend bearer token is stored encrypted in the Jentic vault. Agents receive a scoped execution token; the raw token never appears in agent context or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'send a transactional email' or 'pause a campaign') and Jentic returns the matching Dynosend operation with its input schema.

Time to first call

Direct integration: 1-2 days to wire up auth, contact and audience CRUD, event posting, and campaign lifecycle. Through Jentic: under 30 minutes - search, load, execute.

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 at https://app.jentic.com/sign-up.

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.

Dynosend API

Connect the Dynosend API to your agent

Capabilities

Start building with Dynosend API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs