Postmarkapp Postmark API

Can I send batch emails with the Postmark API?

Yes. The POST /email/batch endpoint accepts an array of up to 500 messages in a single request. Each message can have its own recipient, subject, and body. For templated batch sends, use POST /email/batchWithTemplates which supports individual template models per message.

What are the rate limits for the Postmark API?

Postmark limits batch sends to 500 messages per request. Listing endpoints use count (max 500) and offset parameters for pagination. Overall sending rate depends on your account tier and server configuration. The API returns appropriate error codes when limits are exceeded.

How do I track email opens and clicks with the Postmark API through Jentic?

Install the SDK with pip install jentic, then search for 'track email open rates'. Jentic returns the GET /stats/outbound/opens operation. For per-message click data, search for 'get email click events' to find GET /messages/outbound/clicks/{messageid}. Execute with date range parameters to retrieve engagement metrics.

Can I process inbound emails with the Postmark API?

Yes. The API provides GET /messages/inbound to list received messages, GET /messages/inbound/{messageid}/details for full message content, PUT /messages/inbound/{messageid}/retry to reprocess failed messages, and PUT /messages/inbound/{messageid}/bypass to skip inbound rules for a specific message.

How do I validate a template before sending with it?

Use POST /templates/validate with your template content and a sample model object. The API checks for syntax errors and missing variables, returning validation results before you deploy the template to production. This prevents runtime rendering failures when sending to recipients.

Can I limit what my agent is allowed to do with the Postmark API?

Yes. Because your Jentic One instance is self-hosted, you set the rules that decide which Postmark operations your agent may call and which server token it uses. Postmark takes the send target in the request body rather than the URL path, so scoping is by operation: you can allow the agent to send email (POST /email) and read outbound stats (GET /stats/outbound) and bounces (GET /bounces) while withholding everything else. Batch sending (POST /email/batch) and template validation (POST /templates/validate) are included only if you add them to the agent's allowed set.