Postmark Account-level API

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

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey23 EndpointsREST

For Agents

Manage Postmark account infrastructure including servers, domains with DNS verification, sender signatures, and cross-server template distribution.

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:
"verify email sending domain DNS records"

# → 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 within a Postmark account

Create and manage sender signatures with SPF verification and DKIM rotation

Push email templates from one server to others for consistent cross-environment deployment

GET STARTED

Start building with Postmark Account-level API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Postmark Account-level API 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

Why though Jentic?

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

Credential isolation

Postmark account tokens (X-Postmark-Account-Token header) are stored encrypted in the Jentic vault. Agents receive scoped access that injects the token automatically — raw account credentials never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'verify email domain DNS') and Jentic returns matching Postmark Account operations with parameter schemas, so agents can manage infrastructure without memorizing endpoint paths.

Time to first call

Direct Postmark Account API integration: 1-2 days for token management and domain verification workflows. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Postmark Server API

Server-level email sending, bounce handling, and message statistics

Choose the Server API when you need to send emails, track bounces, or view delivery statistics — the Account API handles infrastructure management (servers, domains, senders).

Alternative

SendGrid Mail API

High-volume email delivery with domain authentication and IP management

Choose SendGrid when you need high-volume sending with dedicated IPs and advanced domain management — Postmark focuses on transactional email with fast delivery and simpler infrastructure.

Alternative

SparkPost API

Enterprise email delivery with sending domain and IP pool management

Choose SparkPost for enterprise-scale sending with granular IP pool management — Postmark emphasizes deliverability for transactional messages with simpler account structure.

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 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 sign up at https://app.jentic.com/sign-up.

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.