VX Agents

API directory · Email

Infobip Email Sending & Validation

v1.0.0 · 15 endpoints · 0 connections · shared by vx.ai

For teams that send receipts, reminders and campaigns through Infobip: send templated or HTML email, check an address before you send, pause or reschedule a scheduled bulk, and trace every message through delivery reports and logs. Suppression lists and sending-domain checks help explain why a message bounced.

Connect this API to an AI agent Browse all specs

What you can do with Infobip Email Sending & Validation via MCP

Every endpoint below becomes a governed tool your AI agent (Claude, ChatGPT, or a customer-facing VX agent) can call — with scoped permissions, sandbox testing, and audit logs.

MethodPathOperationDescription
POST /email/3/send sendEmail Send an email (HTML, text or template) to one or more recipients
POST /email/2/validation validateEmailAddress Check whether an email address is valid and deliverable
GET /email/4/reports getDeliveryReports Get delivery reports for sent emails
GET /email/4/logs getMessageLogs Search sent email logs by sender, recipient, status or date
GET /email/1/bulks listScheduledBulks See when a scheduled bulk of emails will go out
PUT /email/1/bulks rescheduleBulk Move a scheduled bulk to a new send time
GET /email/1/bulks/status getScheduledBulkStatus Check whether a scheduled bulk is pending, paused or cancelled
PUT /email/1/bulks/status updateScheduledBulkStatus Pause, resume or cancel a scheduled bulk
GET /email/1/templates listTemplates List saved email templates
GET /email/1/templates/{templateId} getTemplate Get one email template with its subject and content
POST /email/1/templates/{templateId}/preview previewTemplate Render a template preview with sample placeholder values
GET /email/1/suppressions listSuppressions List bounced, complained or unsubscribed addresses
POST /email/1/suppressions addSuppressions Stop sending to specific addresses
GET /email/1/domains listDomains List your sending domains and their verification status
GET /email/1/domains/{domainName} getDomain Get DNS records and tracking settings for a sending domain

Authentication

infobipApiKey

API key — sent as the Authorization header

Infobip API key sent as Authorization: App <api-key> (the word App, a space, then the key).

How to get a credential

  1. Sign in to the Infobip portal (a free trial account works; trial email can only go to your own verified address).
  2. Open Developer tools > API keys and click Create API key.
  3. Give it a name and select the scopes below, then copy the key.
  4. Copy your personal base URL from the same page (e.g. xyz123.api.infobip.com) and set it as the server baseUrl variable.
  5. Register and verify a sender domain under Channels and Numbers > Email before sending to real customers.

Permissions used

API scope Operations
email:message:send sendEmail, getDeliveryReports, listScheduledBulks, getScheduledBulkStatus, rescheduleBulk, listDomains, getDomain
email:logs:read getMessageLogs
email:templates:manage listTemplates, getTemplate, previewTemplate
email:manage every operation above, plus updateScheduledBulkStatus, validateEmailAddress, listSuppressions, addSuppressions

The simplest setup is one key with email:manage.

Common errors

  • 401 Unauthorized: the header is not App <key>, the key was revoked, or the base URL belongs to another account.
  • 403 Forbidden: the key lacks the scope, or the from domain is not registered to your account.
  • 400 Bad Request: missing from/to/subject, an invalid address, or a sendAt time in the past or more than 30 days ahead.
  • 429 Too Many Requests: rate limit hit (for example 10 template calls per second); back off and retry.

Store the value App <api-key> as a VX Agents credential (API key header) and never paste it into chat.

Usage guide

Setup

  1. Create an Infobip API key (Developer tools > API keys) with the email:manage scope and store it as a VX Agents API key credential with the value App <api-key>.
  2. Set the server variable baseUrl to your personal prefix (the xyz123 in xyz123.api.infobip.com).
  3. Worth pinning: from on sendEmail (e.g. Acme Support <[email protected]>, on a verified sending domain) and domainName if you have several domains.

Send and track an email

  1. Optional: validateEmailAddress with {"to": "<address>"} to catch typos and disposable inboxes before sending.
  2. Draft the message and show the recipients, subject and body to the user. Send only after they confirm: sendEmail (form fields) with from, to (repeat the field for several recipients), subject, and text or html. To use a saved template, send templateId plus defaultPlaceholders (JSON string) instead of the body; listTemplates, getTemplate and previewTemplate help pick and check one.
  3. To send later, add sendAt (ISO 8601, up to 30 days ahead) and a bulkId you choose. listScheduledBulks and getScheduledBulkStatus show the plan; rescheduleBulk moves it and updateScheduledBulkStatus sets PAUSED, PENDING (resume) or CANCELED. Confirm before cancelling.
  4. Keep the messageId / bulkId from the response. getDeliveryReports returns the final status per message; getMessageLogs searches by sender, destination, generalStatus or sentSince/sentUntil.
  5. If a message bounced, listSuppressions (filter by domainName, type BOUNCE / COMPLAINT / OVER_QUOTA) shows why; addSuppressions (type BOUNCE or COMPLAINT) blocks addresses you must stop mailing (confirm first).
  6. listDomains and getDomain show whether a sending domain's DNS records are verified, which explains 403s on from.

Good to know

  • getDeliveryReports returns each report only once; getMessageLogs covers the last 48 hours. Store what you need.
  • generalStatus values: ACCEPTED, PENDING, DELIVERED, UNDELIVERABLE, EXPIRED, REJECTED.
  • Placeholders look like {{ph1}} in the subject or body; defaultPlaceholders={"ph1": "Ana"} fills them for every recipient.
  • Trial accounts can send only to the address they signed up with.
  • Sending email reaches customers and may cost credits: always confirm recipients and content first.

Source: Infobip Email API reference (https://www.infobip.com/docs/api/channels/email), checked 2026-10-20.

How to use this spec

  1. Create a free VX Agents account (sandbox tools included).
  2. Open the marketplace and connect “Infobip Email Sending & Validation” to an agent.
  3. Expose it as an MCP server for Claude/ChatGPT, or chat with it directly.

Related APIs

  • Resend Email — Send, schedule and track transactional email through Resend: one-off messages or batches of up to 100, scheduled sends …
  • Loops Email Contacts & Events — For SaaS teams running product email on Loops: keep contacts and their custom properties in sync, check suppression, fi…
  • Omnisend Email & SMS Campaigns — Draft, test and send Omnisend campaigns without opening the editor: create an email or SMS draft for a segment, fill in…
  • GetResponse Contacts & Newsletters — For email marketers on GetResponse: find who is on each list, add new subscribers, keep their tags and custom fields cu…
  • Mailtrap Email Logs & Sending Stats — Did that password-reset email reach the customer, and why are Outlook opens down this week? Search Mailtrap email logs …
  • Postmark Transactional Email — Send transactional email through a Postmark server (plain or from a template), search sent messages and read their deli…