canonical: https://jentic.com/apis/postmarkapp.com/postmark-account-level-api

# Postmarkapp Postmark Account-level API

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.

## For AI agents

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

## Scope

Does not handle email sending, bounce tracking, or delivery stats - use for account infrastructure configuration only.

## Capabilities

- Provision and configure mail servers with custom inbound and bounce hook URLs
- Register and verify sending domains with DKIM rotation and SPF validation
- Manage sender signatures with identity verification and DKIM key requests
- Push email templates across multiple servers in a single operation
- Verify Return-Path DNS records for improved email deliverability
- List and filter account resources with paginated responses up to 500 records

## Use cases

### 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.

Example prompt: 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.

Example prompt: Register a new domain 'notifications.example.com', trigger DKIM verification, and check the verification status

### 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.

Example prompt: 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /domains | List all sending domains in the account |
| POST | /domains | Register a new sending domain |
| 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 |

## Key resources

- **Domains** — Register, verify, and manage sending domains with DKIM, SPF, and Return-Path configuration
- **Senders** — Create and manage sender signatures with identity verification and DKIM key rotation
- **Servers** — Provision, configure, and manage mail servers within the account
- **Templates** — Push email templates across servers

## Why Jentic

- **Setup:** Wiring the Postmark Account-level API by hand means handling its X-Postmark-Account-Token header and threading it through every domain, sender, and server 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 handling:** 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.
- **Discovery method:** Agents search Jentic by intent such as 'verify a sending domain' or 'list senders', and Jentic returns the matching Postmark Account operation with its input schema so the agent configures domains without browsing the reference docs.

## Related APIs

- **Postmark API** — The server-level API for sending emails, tracking bounces, and managing templates on individual servers
- **SendGrid Domain Authentication API** — SendGrid's domain authentication and sender verification with automated DNS record management
- **Mailjet API** — Email delivery platform with sender domain management and real-time analytics

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Postmark Account-level API?

Yes. Jentic One runs self-hosted, so your own rules decide which operations and credentials the agent may use with the Postmark Account-level API. Because Postmark puts the domain id in the URL path (/domains/{domainid}/...), a rule can pin the agent to a single domain, and you pick exactly which operations it may call. That means write actions like rotating a DKIM key (POST /domains/{domainid}/rotatedkim) or creating a server (POST /servers) are excluded unless you explicitly allow them, while read-only calls such as listing domains or senders stay available.