Postmarkapp Postmark Account-level API
Browse all Postmarkapp APIs69
AI ReadinessAI-Aware (B+)69/100
Official vendor OpenAPI document · agent-readyCommunicationsEmail DeliveryapiKey23 EndpointsREST
For Agents
Manage Postmark account infrastructure including servers, domains with DNS verification, sender signatures, and cross-server template distribution.
Use for: I need to create a new mail server in my Postmark account, I want to verify DKIM records for a sending domain, List all sender signatures configured in the account, Check whether a domain's SPF record is properly configured
Not supported: Does not handle individual email sending, bounce processing, or message statistics - use for account-level infrastructure management (servers, domains, senders) only.
The Postmark Account-level API enables management of servers, domains, sender signatures, and template distribution across a Postmark account with 23 endpoints. It handles domain DNS verification (DKIM, SPF, Return-Path), sender identity configuration, server provisioning, and cross-server template deployment for organizations managing multiple sending environments.
Install Jentic One Beta
Connect the Postmark Account-level API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Postmark Account-level 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%2Fpostmarkapp.com%2Fpostmark-account-api" | sh2
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%2Fpostmark-account-api" | 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.
Capabilities
What an agent can do with Postmark Account-level API.
Provision and configure mail servers within a Postmark account
Register and verify sending domains with automated DKIM, SPF, and Return-Path DNS checks
Create and manage sender signatures with SPF verification and DKIM rotation
Push email templates from one server to others for consistent cross-environment deployment
Rotate DKIM keys on domains to maintain email authentication security
Verify domain ownership through DNS record validation workflows
Use Cases
Patterns agents use Postmark Account-level API for, with concrete tasks.
★ Multi-Environment Server Management
Manage separate Postmark servers for development, staging, and production environments within a single account. The Account-level API allows agents to create servers with distinct configurations, push templates between them for deployment consistency, and maintain isolated sending environments. Each server maintains its own API token and sending statistics.
Create a new server via POST /servers with a name and color label, then push templates from an existing server to the new one using POST /templates/push
Domain Authentication Setup
Configure and verify sending domains with proper DNS authentication records. The API provides endpoints to register domains, check DKIM and SPF verification status, rotate DKIM keys, and verify Return-Path configuration. Agents can monitor verification status and alert when DNS records become invalid or need rotation.
Create a domain via POST /domains, then verify its DKIM record using PUT /domains/{domainid}/verifydkim and check the SPF status with PUT /domains/{domainid}/verifyspf
Sender Identity Management
Register and verify sender email addresses and signatures for use across the account. The API supports creating sender signatures, resending verification emails, requesting new DKIM keys, and verifying SPF for individual senders. This ensures all sending identities maintain proper authentication for deliverability.
List all senders via GET /senders, identify any with unverified SPF, and trigger SPF verification for each using PUT /senders/{signatureid}/verifyspf
AI Agent Email Infrastructure Automation
Enable AI agents to manage Postmark account infrastructure through Jentic. Agents can provision servers, verify domains, manage sender identities, and deploy templates across environments without hardcoding API paths or managing account-level tokens directly.
Search Jentic for 'verify email sending domain DNS', load the operation schema for domain DKIM verification, and execute against a specified domain ID
Key Endpoints
23 endpoints — the postmark account-level api enables management of servers, domains, sender signatures, and template distribution across a postmark account with 23 endpoints.
METHOD
PATH
DESCRIPTION
GET
/servers
List all servers in the account
POST
/servers
Create a new server
GET
/domains
List all sending domains
PUT
/domains/{domainid}/verifydkim
Verify DKIM DNS record for a domain
PUT
/domains/{domainid}/verifyspf
Verify SPF record for a domain
GET
/senders
List all sender signatures
POST
/templates/push
Push templates between servers
PUT
/domains/{domainid}/rotatedkim
Rotate DKIM key for a domain
GET
/servers
List all servers in the account
POST
/servers
Create a new server
GET
/domains
List all sending domains
PUT
/domains/{domainid}/verifydkim
Verify DKIM DNS record for a domain
PUT
/domains/{domainid}/verifyspf
Verify SPF record for a domain
GET
/senders
List all sender signatures
POST
/templates/push
Push templates between servers
PUT
/domains/{domainid}/rotatedkim
Rotate DKIM key for a domain
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.
P
Postmark Account-level API
- AI-Aware (B+)69/100
99
Foundational Compliance69
Developer Experience & Jentic Compatibility46
AI-Readiness & Agent Experience94
Agent Usability100
Security59
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
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.
69
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.
75%
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.
46
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
23%
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.
62%
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.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
59
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
59%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Postmark Account-level API by hand means handling its X-Postmark-Account-Token header and attaching it to every server, domain, and sender request yourself. Through Jentic you install once, import the Postmark Account-level API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Postmark puts the domain id in the URL path (/domains/{domainid}/...), so a rule can pin your agent to one domain: you choose the operations it may call, so writes like rotating DKIM or creating servers are not included unless you add them.
Credential isolation
Your Postmark account 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 'verify an email domain's DNS' or 'list servers', and Jentic returns the matching Postmark Account 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.
FAQs
Specific to using Postmark Account-level API through Jentic.
What authentication does the Postmark Account-level API use?
The Postmark Account-level API uses an account token passed in the X-Postmark-Account-Token header with every request. This is different from server-level tokens used for sending emails. Through Jentic, the account token is stored encrypted in the credential vault and injected into requests automatically.
Can I provision new mail servers with the Postmark Account API?
Yes. POST to /servers creates a new server with configurable name, color label, and delivery settings. Each server gets its own API token for sending and its own statistics. You can also retrieve and update server configurations via GET and PUT /servers/{serverid}.
How do I verify domain DNS records with this API?
Use PUT /domains/{domainid}/verifydkim to check DKIM, PUT /domains/{domainid}/verifyspf for SPF, and PUT /domains/{domainid}/verifyreturnpath for Return-Path records. Each returns the current verification status and expected DNS record values. You can also rotate DKIM keys via PUT /domains/{domainid}/rotatedkim.
How do I push templates between servers through Jentic?
Search Jentic for 'push email templates between servers', load the operation schema for POST /templates/push, and execute with the source server ID and destination server ID. This deploys all templates from one server to another. Install with pip install jentic and run it through Jentic One, the self-hosted execution layer.
What is the difference between the Account API and the Server API?
The Account-level API manages infrastructure across your entire Postmark account - servers, domains, and sender signatures. The Server API handles individual email operations - sending messages, tracking bounces, and viewing statistics for a specific server. They use different authentication tokens.
Can I manage sender signatures programmatically?
Yes. GET /senders lists all signatures, POST /senders creates a new one, and PUT /senders/{signatureid}/verifyspf triggers SPF verification. You can also resend the confirmation email via POST /senders/{signatureid}/resend and request new DKIM keys via POST /senders/{signatureid}/requestnewdkim.
Can I limit what my agent is allowed to do with the Postmark Account API?
Yes. Because you run Jentic One yourself and it is self-hosted, your own rules decide which Postmark Account operations and credentials the agent may use. Since Postmark carries the domain id in the URL path, such as /domains/{domainid}/verifydkim, you can pin the agent to a single domain and grant only read operations like GET /domains and GET /servers. Write operations such as PUT /domains/{domainid}/rotatedkim or POST /servers are excluded unless you explicitly add them.
GET STARTED