Omnivery Automations API

Name: Omnivery Automations API
Brand: Omnivery Automations API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey13 EndpointsREST

For Agents

Send transactional emails, validate addresses, detect bots, and manage sender domains and webhooks for the Omnivery email platform.

Install Jentic One Beta

Connect the Omnivery Automations API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Omnivery Automations API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

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 | sh

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 instance

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

Capabilities

What an agent can do with Omnivery Automations API.

Send transactional email messages through configured Omnivery sending domains

Validate recipient email addresses before adding them to a send list

Suppress specific addresses to prevent future deliveries to known bouncers

GET STARTED

Start building with Omnivery Automations API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Omnivery Automations API for, with concrete tasks.

★ Transactional Email Delivery

Deliver password resets, receipts, and account notifications through Omnivery's sending infrastructure. The POST /{domain}/messages endpoint accepts the recipient, subject, and body and queues the message against a verified sending domain. Suppression and validation endpoints help keep the sender reputation clean before each send.

Send a transactional email from no-reply@example.com to a verified recipient with subject 'Password reset' and a one-time link in the body.

Bot Filtering on Engagement Metrics

Distinguish real recipients from automated scanners by submitting interaction events to the bot detection endpoint and reading back a request-level verdict. The POST /{domain}/bot endpoint validates an interaction, and GET /{domain}/bot/{request_id} retrieves the stored result for downstream analytics or filtering.

Submit a click event to /{domain}/bot for request_id abc123 and retrieve the bot verdict before counting the click in engagement reports.

Address Validation and Suppression Hygiene

Keep mailing lists clean by validating each address before adding it and suppressing addresses that have hard-bounced. GET /{domain}/validate scores an address for deliverability, and POST /{domain}/suppress adds an address to the per-domain suppression list so future sends skip it automatically.

Validate user@example.com via GET /{domain}/validate; if the response marks it undeliverable, post it to /{domain}/suppress.

Agent-Driven Email Workflows via Jentic

AI agents trigger Omnivery email sends, validate addresses, and react to webhook events through Jentic's intent search without storing the API key in the agent context. The agent searches for the send operation, loads its schema, and executes it with parameters supplied by upstream tools.

Use Jentic search 'send transactional email omnivery' to locate POST /{domain}/messages, load the schema, and execute the send.

Key Endpoints

13 endpoints — the omnivery automations api delivers transactional email, validates recipient addresses, detects bots interacting with messages, and manages sender domains.

METHOD

PATH

DESCRIPTION

POST

/{domain}/messages

Send an email message

GET

/{domain}/validate

Validate a recipient address

POST

/{domain}/suppress

Suppress an address from future sends

POST

/{domain}/bot

Submit an interaction for bot detection

GET

/{domain}/bot/{request_id}

Retrieve a stored bot detection result

POST

/domains/{domain}/webhooks

Subscribe a webhook to delivery events

GET

/domains

List configured sending domains

POST

/{domain}/messages

Send an email message

GET

/{domain}/validate

Validate a recipient address

POST

/{domain}/suppress

Suppress an address from future sends

POST

/{domain}/bot

Submit an interaction for bot detection

GET

/{domain}/bot/{request_id}

Retrieve a stored bot detection result

Why Jentic?

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

Credential isolation

Omnivery API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped reference and never see the raw key in their context.

Intent-based discovery

Agents search by intent (e.g. 'send transactional email omnivery') and Jentic returns the matching operation with its input schema, so the agent can call the right endpoint without scanning docs.

Time to first call

Direct integration: 1-2 days for auth, retries, and webhook plumbing. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Omnivery Automations API through Jentic.

What authentication does the Omnivery Automations API use?

The API uses an API key passed as a request header. Through Jentic the key is held in the encrypted vault (MAXsystem) and never enters the agent context — agents receive a scoped reference only.

Can I send transactional email with the Omnivery Automations API?

Yes. POST /{domain}/messages queues a message against a verified sending domain. Combine with GET /{domain}/validate before adding new recipients to keep bounce rates low.

How does bot detection work in the Omnivery API?

Submit an interaction to POST /{domain}/bot to receive a request id, then call GET /{domain}/bot/{request_id} to read back the verdict. Honeypot link clicks can also be inspected via GET /{domain}/{message_id}/hclick.

What are the rate limits for the Omnivery Automations API?

Rate limits are not declared in the OpenAPI spec; consult docs.omnivery.com for current account-tier limits and burst allowances.

How do I subscribe to delivery webhooks through Jentic?

Search Jentic for 'subscribe omnivery webhook', load the POST /domains/{domain}/webhooks schema, then execute with the target URL and webhook type. Sample payloads are available via GET /domains/{domain}/webhooks/{webhooktype}/sample.

Is the Omnivery API free?

Omnivery offers paid sending tiers; pricing depends on volume and feature mix. Check docs.omnivery.com for current plans before committing production traffic.

Omnivery Automations API

Connect the Omnivery Automations API to your agent

Capabilities

Start building with Omnivery Automations API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs