Postmarkapp APIs
4 APIs132 Endpoints1 Category
Categories
API Catalog
Postmark Account-level API
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.
23 endpointsPostmark 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.
23 endpointsPostmark API
The Postmark API handles transactional email delivery with 43 endpoints covering sending (single, batch, and templated), bounce management, inbound message processing, outbound message search, delivery statistics, and template management. It tracks opens, clicks, and spam complaints with per-message granularity and supports inbound email processing with bypass and retry controls. Authentication uses a per-server token in the X-Postmark-Server-Token header.
43 endpointsPostmark API
The Postmark Server API provides transactional email sending, bounce management, delivery statistics, template handling, and inbound message processing across 43 endpoints. It supports single and batch email delivery with template rendering, bounce tracking with reactivation workflows, open and click analytics by platform and browser, inbound email processing with rule-based triggers, and server-level configuration.
43 endpointsConnect Your Agent
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.