Postmark Account-level API

Name: Postmark Account-level API API
Brand: Postmark Account-level API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail DeliveryapiKey23 EndpointsREST

For Agents

Configure Postmark account infrastructure including servers, domains, DKIM/SPF verification, and sender signatures. Manages the account-level resources that underpin email delivery.

Quickstart

Get started with Postmark Account-level API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"configure a Postmark sending domain"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Postmark Account-level API API.

Provision and configure mail servers with custom inbound and bounce hook URLs

Manage sender signatures with identity verification and DKIM key requests

Push email templates across multiple servers in a single operation

GET STARTED

Start building with Postmark Account-level API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Postmark Account-level API, keeping it validated and agent-ready.

The Postmark Account-level API enables management of all servers, domains, and sender signatures associated with a Postmark account. It provides operations for configuring domain authentication (DKIM, SPF, Return-Path verification), managing sender identities, provisioning and configuring mail servers, and pushing templates across servers. The API uses an Account Token for authentication and supports up to 500 records per paginated request.

Use Cases

Patterns agents use Postmark Account-level API API for, with concrete tasks.

★ Multi-Server Email Infrastructure Setup

Provision and configure multiple Postmark servers for different applications or environments within a single account. Each server gets its own API token, inbound address, and webhook configuration. The Account API handles server creation, configuration updates, and deletion across up to 500 servers per paginated listing, enabling centralized infrastructure management for organizations running multiple email-sending applications.

Create a new Postmark server named 'production-notifications' with a custom bounce hook URL and retrieve its server API token

Domain Authentication and Verification

Automate the domain verification workflow for email deliverability by registering domains, triggering DKIM and SPF verification checks, and rotating DKIM keys on schedule. The API provides endpoints for each verification step independently, enabling agents to build automated domain health monitoring that checks authentication status and re-triggers verification when DNS records change.

Sender Identity Management

Manage sender signatures (from addresses) across an account programmatically. Create new sender identities, trigger confirmation emails, request new DKIM keys, and verify SPF records for each sender. This enables automated onboarding flows where new team members or applications need verified sending addresses without manual dashboard interaction.

Create a new sender signature for 'support@example.com', then trigger the SPF verification check

AI Agent Account Configuration

Enable AI agents to manage Postmark account infrastructure through Jentic by discovering server and domain management operations via intent search. Agents can provision servers, verify domains, and manage senders without navigating the Postmark dashboard. Jentic provides the operation schemas so agents know exactly which fields are required for each configuration change.

Search Jentic for 'configure postmark sending domain', load the domain creation schema, and execute to register a new domain with DKIM verification

Key Endpoints

23 endpoints — the postmark account-level api enables management of all servers, domains, and sender signatures associated with a postmark account.

METHOD

PATH

DESCRIPTION

GET

/domains

List all sending domains in the account

POST

/domains

POST

/domains/{domainid}/rotatedkim

Rotate DKIM key for a domain

PUT

/domains/{domainid}/verifydkim

Verify DKIM DNS records for a domain

GET

/senders

List all sender signatures

POST

/servers

Create a new mail server

PUT

/templates/push

Push templates across servers

GET

/domains

List all sending domains in the account

POST

/domains

POST

/domains/{domainid}/rotatedkim

Rotate DKIM key for a domain

PUT

/domains/{domainid}/verifydkim

Verify DKIM DNS records for a domain

GET

/senders

List all sender signatures

Why though Jentic?

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

Credential isolation

Postmark Account Tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens and never see the raw X-Postmark-Account-Token header value directly.

Intent-based discovery

Agents search by intent (e.g., 'verify a sending domain') and Jentic returns matching Postmark Account API operations with their input schemas, so the agent can configure domains without browsing Postmark docs.

Time to first call

Direct Postmark Account API integration: 1-2 days for auth handling and multi-operation workflows. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Postmark API

The server-level API for sending emails, tracking bounces, and managing templates on individual servers

Use the Server API when you need to send emails or check delivery stats. Use the Account API when configuring servers, domains, or sender identities.

Alternative

SendGrid Domain Authentication API

SendGrid's domain authentication and sender verification with automated DNS record management

Choose SendGrid when you need integrated marketing email alongside transactional, or require IP pool management at scale.

Alternative

Mailjet API

Email delivery platform with sender domain management and real-time analytics

Choose Mailjet when you need combined transactional and marketing email with built-in A/B testing and collaborative template design.

FAQs

Specific to using Postmark Account-level API 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 HTTP header. This token is different from per-server tokens and provides access to all account-wide resources. Through Jentic, this token is stored encrypted and agents receive scoped access without handling the raw credential.

Can I verify DKIM records for a domain with the Postmark Account-level API?

Yes. After registering a domain via POST /domains, use PUT /domains/{domainid}/verifydkim to trigger DKIM verification. The API checks your DNS records and returns the verification status. You can also rotate DKIM keys with POST /domains/{domainid}/rotatedkim when key rotation is needed.

What are the rate limits for the Postmark Account-level API?

Postmark applies standard rate limits at the account level. Listing endpoints support pagination with a maximum of 500 records per request using count and offset parameters. If you exceed rate limits, the API returns appropriate error responses and you should implement backoff logic.

How do I push templates across servers with the Postmark Account-level API through Jentic?

Install the SDK with pip install jentic, then search for 'push email templates across Postmark servers'. Jentic returns the PUT /templates/push operation schema. Execute with the source server ID and destination server IDs to replicate templates without manually copying them in the dashboard.

What is the difference between the Account API and the Server API in Postmark?

The Account API manages infrastructure (servers, domains, sender signatures) using an Account Token. The Server API handles email operations (sending, bounces, stats, inbound) using a per-Server Token. Use the Account API to set up and configure your email infrastructure, and the Server API to actually send and track emails.