Postmark APIs for AI Agents
CommunicationsEmail DeliveryOfficial Vendor SpecsAPI keyAgent Ready
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... | Use | Why |
|---|---|---|
| Send transactional or templated email and track delivery | Postmark Server API | The Server API sends single, batch, and template-based messages and returns open, click, and bounce statistics for one server. |
| Manage bounces and inbound message processing | Postmark Server API | Bounce listing, reactivation, and inbound trigger rules live on the Server API, scoped to a single sending server. |
| Provision servers or verify sending domains | Postmark Account-level API | The 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 distribution | Postmark Account-level API | Sender 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.
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
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?
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.
