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 / Postmark
Postmark logo

Postmark APIs for AI Agents

postmarkapp.com·Developer portal → postmarkapp.com

CommunicationsEmail DeliveryOfficial Vendor DocumentsAPI keyAgent Ready

For Agents

APIs2 in catalogue
Endpoints66 indexed
AuthAPI key — 1 credential for all 2 APIs
ProvenanceOfficial OpenAPI documents

An agent can send transactional and templated emails, track delivery, opens, clicks, and bounces on a Postmark server, and separately provision servers, verify sending domains via DKIM and SPF, manage sender signatures, and push templates across the account.

Postmark splits its surface into a server-level API for sending and delivery tracking and an account-level API for infrastructure such as servers, domains, and sender signatures, each authenticated by a distinct token. It focuses on fast transactional delivery with per-server statistics rather than marketing campaigns or bulk list management.

Use for: Transactional email sending with delivery, open, click, and bounce tracking on a Postmark server, plus account-level provisioning of servers, domain DKIM and SPF verification, and sender signature management.

Not supported: marketing campaigns, contact list management, SMS messaging, on-prem deployment, custom IP pools

Credentials: No single credential covers both APIs: the Server API uses a per-server token in the X-Postmark-Server-Token header, while the Account-level API uses a separate account token in the X-Postmark-Account-Token header.

All 2 Postmark OpenAPI documents are vendor-official and indexed by Jentic, kept validated and agent-ready.

Postmark is a transactional email platform. Its APIs cover two layers: server-level email operations (sending single, batch, and templated messages, tracking opens and clicks, managing bounces, and processing inbound mail) and account-level infrastructure (provisioning servers, verifying sending domains with DKIM and SPF, managing sender signatures, and distributing templates across environments).

Jentic One on Github

Postmark API Catalog

2 APIs across 1 product group. All share one credential.

Communications2

Postmark Server APISend transactional emails, manage bounces, track delivery statistics, render templates, and process inbound messages for a specific Postmark server.~43 endpointsPostmark Account-level APIManage Postmark account infrastructure including servers, domains with DNS verification, sender signatures, and cross-server template distribution.~23 endpoints

Which Postmark API should I use?

I want to...UseWhy
Send transactional or templated email and track deliveryPostmark Server APIThe Server API sends single, batch, and template-based messages and returns open, click, and bounce statistics for one server.
Manage bounces and inbound message processingPostmark Server APIBounce listing, reactivation, and inbound trigger rules live on the Server API, scoped to a single sending server.
Provision servers or verify sending domainsPostmark Account-level APIThe Account-level API creates servers and verifies domain DKIM, SPF, and Return-Path records, which the Server API cannot do.
Manage sender signatures and cross-server template distributionPostmark Account-level APISender signature creation, verification, and pushing templates between servers are account-level operations.

Install Jentic One Beta

Connect the Postmark APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Postmark APIs, 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%2Fpostmarkapp.com" | 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%2Fpostmarkapp.com" | 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.

Once connected, ask your agent something like: “send transactional email and verify sending domain with Postmark”.

What AI Agents Can Do with Postmark

Each workflow spans multiple Postmark APIs. Jentic routes each operation to the right API automatically.

Stand up a new sending environment end to end

Provision a fresh Postmark server, verify its sending domain, then start sending templated transactional mail through it. The account-level API creates the server and confirms domain DKIM and SPF, and the server-level API sends and tracks the first messages.

Example prompt:

Create a server via POST /servers and verify its domain DKIM and SPF on the account API, then switch to the server token and send a templated message via POST /email/withTemplate, confirming delivery through GET /messages/outbound/{messageid}/details

APIs used

Postmark Account-level API + Postmark Server API

Deploy templates across environments and validate delivery

Push email templates from a staging server to production, then send a test transactional email on the destination server and confirm it renders and delivers. Template distribution is account-level and the test send plus tracking is server-level.

Example prompt:

Call POST /templates/push on the account API to copy templates to the production server, then send a templated message with POST /email/withTemplate and read GET /stats/outbound to confirm the send

APIs used

Postmark Account-level API + Postmark Server API

Audit domain authentication before a sending run

Check that a sending domain's DKIM and SPF records are verified at the account level, then review recent bounce and delivery statistics on the server before scaling up sends. This pairs account-level authentication checks with server-level deliverability signals.

Example prompt:

Verify domain records with PUT /domains/{domainid}/verifydkim and PUT /domains/{domainid}/verifyspf on the account API, then pull GET /bounces and GET /stats/outbound on the server API to confirm the domain is healthy before a larger send

APIs used

Postmark Account-level API + Postmark Server API

Why Jentic?

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

Setup

Wiring Postmark by hand means handling two different token headers, X-Postmark-Server-Token for sending and X-Postmark-Account-Token for infrastructure, and targeting api.postmarkapp.com for every call. With Jentic you install once, add the Postmark APIs you need from the Jentic directory, store each token once, and your agent calls the operations.

Permission scoping

Scoping differs by layer: server operations take the email target in the request body, so you scope by operation such as sending or reading bounce stats, while account operations put the domain id in the path, letting a rule pin the agent to one domain. Your own Jentic One rules decide which operations across both APIs the agent may call, so writes like rotating DKIM or provisioning servers are excluded unless you add them.

Credential isolation

Both the Postmark server token and the account token are stored once, encrypted, by your own Jentic One instance and injected at execution time. Neither enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search the Jentic directory by intent such as 'send a transactional email' or 'verify a sending domain's DNS', and Jentic returns the matching Postmark operation with its input schema, so the agent reaches the right endpoint on the right API without browsing the reference docs.

FAQs

Specific to using Postmark APIs through Jentic.

What is the difference between the Server API and the Account-level API?

The Server API handles individual email operations for one sending server: sending messages, tracking opens and clicks, managing bounces, and processing inbound mail. The Account-level API manages infrastructure across the whole account, including provisioning servers, verifying sending domains, and managing sender signatures. They use different tokens.

Does one credential work across both Postmark APIs?

No. The Server API authenticates with a per-server token in the X-Postmark-Server-Token header, and each server in your account has its own. The Account-level API uses a separate account token in the X-Postmark-Account-Token header. An agent working across both layers needs both tokens.

Can an agent set up a new sending environment from scratch?

Yes. The Account-level API creates a server and verifies its sending domain through DKIM and SPF checks, and the Server API then sends and tracks the first transactional emails on that server. The two APIs together cover provisioning, authentication, and sending.

Are these APIs suitable for marketing email?

Postmark is built for transactional email such as password resets, receipts, and notifications, with fast delivery and per-server statistics. It does not provide contact list management, campaign scheduling, or bulk marketing features, so use a dedicated marketing platform for those needs.

How do templates move between servers?

Template distribution is an account-level operation. POST /templates/push on the Account-level API copies templates from a source server to a destination server, which lets you promote consistent templates from staging to production. The Server API then renders those templates when sending.

How does an agent pick the right API for a task?

If the task is sending, tracking, or bounce handling for one server, use the Server API. If it is provisioning servers, verifying domains, managing sender identities, or distributing templates, use the Account-level API. An agent searching Jentic by intent is routed to the matching operation on the correct API.

If you need a different Communications vendor

All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.

SendGridEmail delivery platform with high-volume sending, dedicated IPs, and marketing plus transactional support.
MailgunTransactional and bulk email API with domain authentication and inbound routing, a direct Postmark alternative.
SparkPostEmail delivery service with sending domain and IP pool management for larger-scale programs.
MandrillTransactional email from Mailchimp with merge-tag templating and conditional content.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo