> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Infobip

The Infobip connector lets your AI agent act in each user's Infobip account. Each user connects their own Infobip API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 65 tools.

**Authentication:** API Key
**Categories:** Communication, Marketing
**Tools:** 65: 22 read, 37 write, 6 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=INFOBIP)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Infobip connection

   In **AgentKit > Connections**, create an Infobip connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'infobip'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Infobip:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'infobip_2fa_applications_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "infobip"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Infobip:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="infobip_2fa_applications_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Infobip credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'infobip_2fa_application_get',
  toolInput: {
    application_id: '<application_id>',
  },
  connector: 'infobip',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="infobip_2fa_application_get",
    tool_input={
        "application_id": "<application_id>",
    },
    connection_name="infobip",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `infobip_2fa_application_get`

Get 2FA Application · Read-only

Get one Infobip 2FA application and its PIN rules.
Returns applicationId, name, enabled and configuration (pinAttempts, pinTimeToLive, rate limits).
Use infobip_2fa_application_get to read an application's limits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E

Example input: `{"application_id":"<application_id>"}`

### `infobip_2fa_applications_list`

List 2FA Applications · Read-only

List your Infobip 2FA applications (each holds PIN rules such as attempts and time-to-live).
Returns applications with applicationId, name, configuration and enabled.
Use infobip_2fa_applications_list to find the applicationId for the PIN tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `infobip_2fa_message_template_get`

Get 2FA Message Template · Read-only

Get one PIN message template of an Infobip 2FA application.
Returns messageId, messageText, pinType, pinLength, senderId, language and voice settings.
Use infobip_2fa_message_template_get to check a template's text and PIN format.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `message_id` (`string`, required): ID of the message template. Example: 9C815F8AF3328

Example input: `{"application_id":"<application_id>","message_id":"<message_id>"}`

### `infobip_2fa_message_templates_list`

List 2FA Message Templates · Read-only

List the PIN message templates of an Infobip 2FA application.
Returns templates with messageId, messageText, pinType, pinLength, senderId and language.
Use infobip_2fa_message_templates_list to find the messageId for infobip_2fa_pin_send_sms or _voice.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E

Example input: `{"application_id":"<application_id>"}`

### `infobip_2fa_verification_status_get`

Get 2FA Verification Status · Read-only

Get the verification history of a phone number or email address in an Infobip 2FA application.
Returns verifications with msisdn, verified, verifiedAt and sentAt.
Use infobip_2fa_verification_status_get to check whether a number has already been verified.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `msisdn` (`string`, required): Phone number (international format without +) or email address. Example: 41793026727
- `sent` (`boolean`, optional): Only attempts whose message was sent (true) or not (false). Example: true
- `verified` (`boolean`, optional): Only verified (true) or unverified (false) attempts. Example: true

Example input: `{"application_id":"<application_id>","msisdn":"<msisdn>"}`

### `infobip_account_balance_get`

Get Account Balance · Read-only

Get the current balance of your Infobip account.
Returns balance and currency.
Use infobip_account_balance_get to check credit before large sends.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `infobip_account_free_messages_get`

Get Free Messages Count · Read-only

Get how many free messages are left on your Infobip account (for example on a trial).
Returns freeMessages.
Use infobip_account_free_messages_get to check trial allowance.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `infobip_email_domain_get`

Get Email Domain · Read-only

Get one Infobip sending domain with the DNS records (SPF, DKIM, MX, tracking CNAME) it needs.
Returns domainId, domainName, active, tracking, dnsRecords with verified flags, and blocked.
Use infobip_email_domain_get to see which DNS records to publish before infobip_email_domain_verify.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_name` (`string`, required): The domain name. Example: mail.example.com

Example input: `{"domain_name":"<domain_name>"}`

### `infobip_email_domains_list`

List Email Domains · Read-only

List the sending domains on your Infobip account with their verification and tracking settings.
Returns paging and results with domainId, domainName, active, tracking, dnsRecords and blocked.
Use infobip_email_domains_list to see which domains can send. Use infobip_email_domain_get for DNS records of one domain.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number, starting at 0. Example: 0
- `size` (`integer`, optional): Domains per page, up to 20. Defaults to 10. Example: 20

Example input: `{}`

### `infobip_email_logs_list`

List Email Logs · Read-only

List logs of emails sent in the last 48 hours, with status and timing.
Returns results with messageId, bulkId, destination, sender, sentAt, doneAt, status, error and price, plus a cursor.
Use infobip_email_logs_list to check delivery; it can be read repeatedly. infobip_email_delivery_reports_get returns each report only once.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, optional): Only messages from this bulk (comma-separate several IDs). Example: 2034072219640523072
- `cursor` (`string`, optional): Cursor from the previous page (with use_cursor). Example: eyJpZCI6IjEyMyJ9
- `destination` (`string`, optional): Only messages to this email address. Example: jane@example.com
- `general_status` (`string`, optional): Only messages in this status group. Example: DELIVERED. One of: `ACCEPTED`, `PENDING`, `UNDELIVERABLE`, `DELIVERED`, `EXPIRED`, `REJECTED`.
- `limit` (`integer`, optional): Maximum logs to return, up to 1000. Defaults to 50. Example: 100
- `message_id` (`string`, optional): Only these message IDs (comma-separated). Example: 2250be2d4219-3af1-78856-aabe-1362af1edfd2
- `sender` (`string`, optional): Only messages from this sender. Example: InfoSMS
- `sent_since` (`string`, optional): Only messages sent after this time (ISO 8601). Logs are kept for 48 hours. Example: 2026-11-12T00:00:00.000+0000
- `sent_until` (`string`, optional): Only messages sent before this time (ISO 8601). Example: 2026-11-13T00:00:00.000+0000
- `use_cursor` (`boolean`, optional): Set true to page with cursor. Example: true

Example input: `{}`

### `infobip_email_scheduled_get`

Get Scheduled Email · Read-only

Get the scheduled send time of a bulk of emails.
Returns bulkId and sendAt.
Use infobip_email_scheduled_get to check when a scheduled email goes out.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, required): The bulkId of the scheduled send. Example: receipts-2026-11-13

Example input: `{"bulk_id":"<bulk_id>"}`

### `infobip_email_suppressions_list`

List Email Suppressions · Read-only

List suppressed addresses (bounces, complaints, over quota) of a sending domain; Infobip does not send to them.
Returns paging and results with domainName, emailAddress, type, createdDate and reason.
Use infobip_email_suppressions_list to check why an address is not receiving mail.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_name` (`string`, required): The sending domain. Example: mail.example.com
- `type` (`string`, required): Suppression type. Example: BOUNCE. One of: `BOUNCE`, `COMPLAINT`, `OVER_QUOTA`.
- `created_date_from` (`string`, optional): Only suppressions created after this time (ISO 8601). Example: 2026-11-01T00:00:00Z
- `created_date_to` (`string`, optional): Only suppressions created before this time (ISO 8601). Example: 2026-11-13T00:00:00Z
- `email_address` (`string`, optional): Only this address. Example: john.smith@example.com
- `page` (`integer`, optional): Page number, starting at 0. Example: 0
- `recipient_domain` (`string`, optional): Only addresses at this domain. Example: example.com
- `size` (`integer`, optional): Results per page, up to 1000. Example: 100

Example input: `{"domain_name":"<domain_name>","type":"BOUNCE"}`

### `infobip_number_get`

Get Owned Number · Read-only

Get one phone number your Infobip account owns.
Returns numberKey, number, country, type, capabilities, applicationId, entityId and price.
Use infobip_number_get for one number. Use infobip_numbers_list to browse.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `number_key` (`string`, required): Unique key of the number, from infobip_numbers_list. Example: E1C5F6B8F1C1D8D6E4C0C3B4B1F0A2C3

Example input: `{"number_key":"<number_key>"}`

### `infobip_numbers_available_list`

Search Available Numbers · Read-only

Search the phone numbers Infobip has available to buy, by country, capabilities or digits.
Returns numberCount and numbers with numberKey, number, country, type, capabilities, shortCode, monthlyPrice and setupPrice.
Use infobip_numbers_available_list before infobip_number_purchase. Use infobip_numbers_list for numbers you own.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `capabilities` (`array`, optional): Required capabilities. Example: ["SMS"]
- `country` (`string`, optional): ISO 3166-1 alpha-2 country code. Example: GB
- `limit` (`integer`, optional): Numbers to return. Example: 20
- `npa` (`integer`, optional): US only: area code. Example: 212
- `number` (`string`, optional): Digits the number should contain. Example: 447
- `state` (`string`, optional): US only: state code. Example: NY

Example input: `{}`

### `infobip_numbers_list`

List Owned Numbers · Read-only

List the phone numbers your Infobip account owns.
Returns numberCount and numbers with numberKey, number, country, type, capabilities, applicationId and price.
Use infobip_numbers_list to find a numberKey. Use infobip_number_get for one number.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`integer`, optional): Numbers per page. Example: 50
- `number` (`string`, optional): Only numbers containing these digits. Example: 4475
- `page` (`integer`, optional): Page number, starting at 0. Example: 0

Example input: `{}`

### `infobip_sms_logs_list`

List SMS Logs · Read-only

List logs of SMS sent in the last 48 hours, with status, price and timing.
Returns results with messageId, bulkId, destination, sender, sentAt, doneAt, status, error and price, plus a cursor.
Use infobip_sms_logs_list to check delivery of sent SMS; it can be read repeatedly. infobip_sms_delivery_reports_get returns each report only once.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, optional): Only messages from this bulk (comma-separate several IDs). Example: 2034072219640523072
- `cursor` (`string`, optional): Cursor from the previous page (with use_cursor). Example: eyJpZCI6IjEyMyJ9
- `destination` (`string`, optional): Only messages to this phone number. Example: 41793026727
- `general_status` (`string`, optional): Only messages in this status group. Example: DELIVERED. One of: `ACCEPTED`, `PENDING`, `UNDELIVERABLE`, `DELIVERED`, `EXPIRED`, `REJECTED`.
- `limit` (`integer`, optional): Maximum logs to return, up to 1000. Defaults to 50. Example: 100
- `mcc` (`string`, optional): Only messages to this mobile country code. Example: 228
- `message_id` (`string`, optional): Only these message IDs (comma-separated). Example: 2250be2d4219-3af1-78856-aabe-1362af1edfd2
- `mnc` (`string`, optional): Only messages to this mobile network code (needs mcc). Example: 01
- `sender` (`string`, optional): Only messages from this sender. Example: InfoSMS
- `sent_since` (`string`, optional): Only messages sent after this time (ISO 8601). Logs are kept for 48 hours. Example: 2026-11-12T00:00:00.000+0000
- `sent_until` (`string`, optional): Only messages sent before this time (ISO 8601). Example: 2026-11-13T00:00:00.000+0000
- `use_cursor` (`boolean`, optional): Set true to page with cursor. Example: true

Example input: `{}`

### `infobip_sms_preview`

Preview SMS · Read-only

Preview how Infobip will encode an SMS text: character count, number of parts and characters left, with and without transliteration or a language table. Nothing is sent.
Returns originalText and previews with textPreview, messageCount, charactersRemaining and configuration.
Use infobip_sms_preview before infobip_sms_send to estimate the cost of a long or non-Latin message.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `text` (`string`, required): The message text to check. Example: Let's see how many characters remain unused in this message.
- `language_code` (`string`, optional): National language table code (TR, ES, PT) or AUTODETECT. Example: AUTODETECT
- `transliteration` (`string`, optional): Transliteration to apply, for example TURKISH, GREEK or NON_UNICODE. Example: NON_UNICODE

Example input: `{"text":"<text>"}`

### `infobip_sms_scheduled_get`

Get Scheduled SMS · Read-only

Get the scheduled send time of a bulk of SMS.
Returns bulkId and sendAt.
Use infobip_sms_scheduled_get to check when scheduled SMS go out. Use infobip_sms_scheduled_status_get for the bulk's status.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, required): The bulkId of the scheduled send. Example: order-batch-2026-11-13

Example input: `{"bulk_id":"<bulk_id>"}`

### `infobip_sms_scheduled_status_get`

Get Scheduled SMS Status · Read-only

Get the status of a scheduled bulk of SMS: pending, paused, processing, canceled, finished or failed.
Returns bulkId and status.
Use infobip_sms_scheduled_status_get to check a scheduled send.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, required): The bulkId of the scheduled send. Example: order-batch-2026-11-13

Example input: `{"bulk_id":"<bulk_id>"}`

### `infobip_viber_logs_list`

List Viber Logs · Read-only

List logs of Viber messages sent in the last 48 hours, with status and timing.
Returns results with messageId, bulkId, destination, sender, sentAt, doneAt, status, error and price.
Use infobip_viber_logs_list to check delivery of Viber messages.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, optional): Only messages from this bulk (comma-separate several IDs). Example: 2034072219640523072
- `cursor` (`string`, optional): Cursor from the previous page (with use_cursor). Example: eyJpZCI6IjEyMyJ9
- `destination` (`string`, optional): Only messages to this phone number. Example: 41793026727
- `general_status` (`string`, optional): Only messages in this status group. Example: DELIVERED. One of: `ACCEPTED`, `PENDING`, `UNDELIVERABLE`, `DELIVERED`, `EXPIRED`, `REJECTED`.
- `limit` (`integer`, optional): Maximum logs to return, up to 1000. Defaults to 50. Example: 100
- `message_id` (`string`, optional): Only these message IDs (comma-separated). Example: 2250be2d4219-3af1-78856-aabe-1362af1edfd2
- `sender` (`string`, optional): Only messages from this sender. Example: InfoSMS
- `sent_since` (`string`, optional): Only messages sent after this time (ISO 8601). Logs are kept for 48 hours. Example: 2026-11-12T00:00:00.000+0000
- `sent_until` (`string`, optional): Only messages sent before this time (ISO 8601). Example: 2026-11-13T00:00:00.000+0000
- `use_cursor` (`boolean`, optional): Set true to page with cursor. Example: true

Example input: `{}`

### `infobip_whatsapp_template_get`

Get WhatsApp Template · Read-only

Get one WhatsApp template of a sender.
Returns id, name, language, status, category, quality and structure (header, body, footer, buttons).
Use infobip_whatsapp_template_get to see a template's placeholders and buttons.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `sender` (`string`, required): Your WhatsApp sender number, international format without +. Example: 441134960000
- `template_id` (`string`, required): Numeric template ID, from infobip_whatsapp_templates_list. Example: 111

Example input: `{"sender":"<sender>","template_id":"<template_id>"}`

### `infobip_whatsapp_templates_list`

List WhatsApp Templates · Read-only

List the WhatsApp message templates of a sender, with their approval status.
Returns templates with id, businessAccountId, name, language, status, category and structure.
Use infobip_whatsapp_templates_list to find approved templates for infobip_whatsapp_template_send.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `sender` (`string`, required): Your WhatsApp sender number, international format without +. Example: 441134960000

Example input: `{"sender":"<sender>"}`

### `infobip_2fa_application_create`

Create 2FA Application · Write

Create an Infobip 2FA application that sets PIN rules for one use case, such as login or password reset.
Returns applicationId, name, configuration and enabled.
Use infobip_2fa_application_create, then add a message template with infobip_2fa_message_template_create.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Application name. Example: Login 2FA
- `configuration` (`object`, optional): PIN rules: pinAttempts (default 10), pinTimeToLive (for example 15m), allowMultiplePinVerifications, and rate limits such as sendPinPerPhoneNumberLimit (for example 3/1d) and verifyPinLimit (for example 1/3s). Example: {"pinAttempts": 5, "pinTimeToLive": "10m", "sendPinPerPhoneNumberLimit": "5/1d", "verifyPinLimit": "1/3s"}
- `enabled` (`boolean`, optional): Whether the application is active. Defaults to true. Example: true

Example input: `{"name":"<name>"}`

### `infobip_2fa_application_update`

Update 2FA Application · Write

Update an Infobip 2FA application's name, enabled flag or PIN rules.
Returns the updated application.
Use infobip_2fa_application_update to change limits or disable an application.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `name` (`string`, required): Application name. Example: Login 2FA
- `configuration` (`object`, optional): PIN rules, as in infobip_2fa_application_create. Example: {"pinAttempts": 5, "pinTimeToLive": "10m"}
- `enabled` (`boolean`, optional): Whether the application is active. Example: true

Example input: `{"application_id":"<application_id>","name":"<name>"}`

### `infobip_2fa_email_template_create`

Create 2FA Email Template · Write

Create an email PIN message template for an Infobip 2FA application, based on an existing Infobip email (Broadcast) template.
Returns messageId, emailTemplateId, from, pinType and pinLength.
Use infobip_2fa_email_template_create before infobip_2fa_pin_send_email.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `email_template_id` (`integer`, required): ID of an Infobip email template whose content contains the {{pin}} placeholder. Example: 1234
- `from` (`string`, optional): Sender address on a verified domain, optionally with a name. Example: Acme <security@example.com>
- `pin_length` (`integer`, optional): PIN length. Example: 6
- `pin_type` (`string`, optional): NUMERIC, ALPHA, HEX or ALPHANUMERIC. Example: NUMERIC. One of: `NUMERIC`, `ALPHA`, `HEX`, `ALPHANUMERIC`.

Example input: `{"application_id":"<application_id>","email_template_id":1234}`

### `infobip_2fa_message_template_create`

Create 2FA Message Template · Write

Create an SMS or voice PIN message template for an Infobip 2FA application.
Returns messageId, messageText, pinType and pinLength.
Use infobip_2fa_message_template_create once per application before sending PINs.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `message_text` (`string`, required): Message text containing the {{pin}} placeholder; other {{name}} placeholders are filled at send time. Example: Your Acme code is {{pin}}
- `pin_type` (`string`, required): PIN characters: NUMERIC, ALPHA, HEX or ALPHANUMERIC. Example: NUMERIC. One of: `NUMERIC`, `ALPHA`, `HEX`, `ALPHANUMERIC`.
- `language` (`string`, optional): Language of the voice message, for example en or de. Example: en
- `pin_length` (`integer`, optional): PIN length. Defaults to 4. Example: 6
- `repeat_dtmf` (`string`, optional): Voice only: key that replays the message, for example 1#. Example: 1#
- `sender_id` (`string`, optional): SMS sender name. Example: Acme
- `speech_rate` (`number`, optional): Voice only: narration speed from 0.5 to 2. Example: 1

Example input: `{"application_id":"<application_id>","message_text":"<message_text>","pin_type":"NUMERIC"}`

### `infobip_2fa_message_template_update`

Update 2FA Message Template · Write

Update an Infobip 2FA PIN message template's text, PIN format, sender or voice settings.
Returns the updated template.
Use infobip_2fa_message_template_update to reword a PIN message.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `message_id` (`string`, required): ID of the message template. Example: 9C815F8AF3328
- `message_text` (`string`, optional): Message text containing {{pin}}. Example: {{pin}} is your Acme code
- `pin_length` (`integer`, optional): PIN length. Example: 6
- `pin_type` (`string`, optional): NUMERIC, ALPHA, HEX or ALPHANUMERIC. Example: NUMERIC. One of: `NUMERIC`, `ALPHA`, `HEX`, `ALPHANUMERIC`.
- `sender_id` (`string`, optional): SMS sender name. Example: Acme

Example input: `{"application_id":"<application_id>","message_id":"<message_id>"}`

### `infobip_2fa_pin_resend_email`

Resend 2FA PIN by Email · Write

Resend the same PIN by email for an existing 2FA verification.
Returns pinId, to and emailStatus.
Use infobip_2fa_pin_resend_email when the user did not get the first email.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `pin_id` (`string`, required): pinId returned when the PIN was first sent. Example: 9C817C6F8AF3D48F9FE553282AFA2B67
- `placeholders` (`object`, optional): Values for extra placeholders in the template. Example: {"firstName": "John"}

Example input: `{"pin_id":"<pin_id>"}`

### `infobip_2fa_pin_resend_sms`

Resend 2FA PIN by SMS · Write

Resend the same PIN by SMS for an existing 2FA verification.
Returns pinId, to and smsStatus.
Use infobip_2fa_pin_resend_sms when the user did not get the first SMS.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `pin_id` (`string`, required): pinId returned when the PIN was first sent. Example: 9C817C6F8AF3D48F9FE553282AFA2B67
- `placeholders` (`object`, optional): Values for extra placeholders in the template text. Example: {"firstName": "John"}

Example input: `{"pin_id":"<pin_id>"}`

### `infobip_2fa_pin_resend_voice`

Resend 2FA PIN by Voice · Write

Resend the same PIN in a voice call for an existing 2FA verification.
Returns pinId, to and callStatus.
Use infobip_2fa_pin_resend_voice to fall back from SMS to a call.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `pin_id` (`string`, required): pinId returned when the PIN was first sent. Example: 9C817C6F8AF3D48F9FE553282AFA2B67
- `placeholders` (`object`, optional): Values for extra placeholders in the template text. Example: {"firstName": "John"}

Example input: `{"pin_id":"<pin_id>"}`

### `infobip_2fa_pin_send_email`

Send 2FA PIN by Email · Write

Generate a one-time PIN and email it to an address, using a 2FA application and email message template.
Returns pinId, to, emailStatus.
Use infobip_2fa_pin_send_email to verify an email address, then infobip_2fa_pin_verify.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `message_id` (`string`, required): ID of the email message template. Example: 5E3A2B1C4D9F8
- `to` (`string`, required): Email address to send the PIN to. Example: john.smith@example.com
- `from` (`string`, optional): Override the template's sender. Example: Acme <security@example.com>
- `placeholders` (`object`, optional): Values for extra placeholders in the template. Example: {"firstName": "John"}

Example input: `{"application_id":"<application_id>","message_id":"<message_id>","to":"<to>"}`

### `infobip_2fa_pin_send_sms`

Send 2FA PIN by SMS · Write

Generate a one-time PIN and send it to a phone number by SMS, using a 2FA application and message template.
Returns pinId, to, ncStatus, smsStatus and callStatus.
Use infobip_2fa_pin_send_sms to start verification, then infobip_2fa_pin_verify with the pinId and the code the user enters.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `message_id` (`string`, required): ID of the SMS message template. Example: 9C815F8AF3328
- `to` (`string`, required): Phone number in international format without +. Example: 41793026727
- `from` (`string`, optional): Override the template's sender name. Example: Acme
- `nc_needed` (`boolean`, optional): Run a Number Lookup first and skip sending if the number is unreachable (extra charge). Example: false
- `placeholders` (`object`, optional): Values for extra placeholders in the template text (keys without braces; pin is filled automatically). Example: {"firstName": "John"}

Example input: `{"application_id":"<application_id>","message_id":"<message_id>","to":"<to>"}`

### `infobip_2fa_pin_send_voice`

Send 2FA PIN by Voice · Write

Generate a one-time PIN and read it out in a voice call to a phone number, using a 2FA application and message template.
Returns pinId, to and callStatus.
Use infobip_2fa_pin_send_voice for landlines or when SMS fails, then infobip_2fa_pin_verify.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_id` (`string`, required): ID of the 2FA application. Example: 1C9E3B2F4D5A6B7C8D9E0F1A2B3C4D5E
- `message_id` (`string`, required): ID of the message template (with voice language settings). Example: 9C815F8AF3328
- `to` (`string`, required): Phone number in international format without +. Example: 41793026727
- `from` (`string`, optional): Caller ID to show. Example: 41793026700
- `placeholders` (`object`, optional): Values for extra placeholders in the template text. Example: {"firstName": "John"}

Example input: `{"application_id":"<application_id>","message_id":"<message_id>","to":"<to>"}`

### `infobip_2fa_pin_verify`

Verify 2FA PIN · Write

Check the PIN a user entered for an Infobip 2FA verification.
Returns pinId, msisdn, verified (true or false), attemptsRemaining and pinError.
Use infobip_2fa_pin_verify after one of the infobip_2fa_pin_send tools.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `pin` (`string`, required): The PIN the user entered. Example: 482910
- `pin_id` (`string`, required): pinId returned when the PIN was sent. Example: 9C817C6F8AF3D48F9FE553282AFA2B67

Example input: `{"pin":"<pin>","pin_id":"<pin_id>"}`

### `infobip_email_address_validate`

Validate Email Address · Write

Check whether an email address is valid and deliverable (syntax, domain, mailbox, disposable or role address) with Infobip. Each validation is charged.
Returns to, validMailbox, validSyntax, catchAll, didYouMean, disposable, roleBased and reason.
Use infobip_email_address_validate before adding an address to a mailing list.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `to` (`string`, required): The email address to check. Example: john.smith@example.com

Example input: `{"to":"<to>"}`

### `infobip_email_delivery_reports_get`

Get Email Delivery Reports · Write

Fetch email delivery reports that have not been fetched or pushed to a webhook yet. Each report is returned only once.
Returns results with messageId, bulkId, to, sentAt, doneAt, status, error and price.
Use infobip_email_delivery_reports_get only when no notify_url is set. Use infobip_email_logs_list to read status repeatedly.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `bulk_id` (`string`, optional): Only reports for this bulk. Example: 2034072219640523072
- `limit` (`integer`, optional): Maximum reports to return, up to 1000. Defaults to 50. Example: 100
- `message_id` (`string`, optional): Only the report for this message. Example: 2250be2d4219-3af1-78856-aabe-1362af1edfd2

Example input: `{}`

### `infobip_email_domain_create`

Add Email Domain · Write

Add a sending domain to your Infobip account.
Returns the domain with the DNS records to publish.
Use infobip_email_domain_create, publish the returned DNS records, then run infobip_email_domain_verify.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `domain_name` (`string`, required): The domain to send from. Example: mail.example.com
- `targeted_daily_traffic` (`integer`, required): Expected emails per day from this domain. Example: 10000
- `dkim_key_length` (`integer`, optional): DKIM key length: 1024 or 2048. Defaults to 1024. Example: 2048. One of: `1024`, `2048`.

Example input: `{"domain_name":"<domain_name>","targeted_daily_traffic":10000}`

### `infobip_email_domain_verify`

Verify Email Domain · Write

Ask Infobip to check the DNS records of a sending domain now.
Returns 202; read the result with infobip_email_domain_get.
Use infobip_email_domain_verify after publishing the records from infobip_email_domain_create.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `domain_name` (`string`, required): The domain name. Example: mail.example.com

Example input: `{"domain_name":"<domain_name>"}`

### `infobip_email_send`

Send Email · Write

Send an email through Infobip to one or more recipients, with text, HTML or a stored template, optionally scheduled.
Returns bulkId and messages with messageId, destination and status.
Use infobip_email_send for transactional or bulk email from a verified domain. Use infobip_email_logs_list to check delivery.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `sender` (`string`, required): From address on a verified domain, optionally with a name: Jane Smith <jane@example.com>. Example: Acme <no-reply@example.com>
- `to` (`array`, required): Recipient email addresses. Example: ["john.smith@example.com"]
- `bcc` (`array`, optional): BCC addresses. Example: ["audit@example.com"]
- `bulk_id` (`string`, optional): Your own ID for this send. Generated if omitted. Example: receipts-2026-11-13
- `callback_data` (`string`, optional): Your own data, returned in delivery reports. Example: order-1234
- `cc` (`array`, optional): CC addresses. Example: ["manager@example.com"]
- `default_placeholders` (`string`, optional): Placeholder values used in the content, as a JSON string, for example {"name": "John"}. Example: {"name": "John"}
- `html` (`string`, optional): HTML body. Example: Hi John, your order <b>1234</b> has shipped.

- `notify_url` (`string`, optional): URL that receives delivery reports. Example: https://example.com/infobip/email-reports
- `reply_to` (`string`, optional): Reply-To address. Example: support@example.com
- `send_at` (`string`, optional): Schedule for this time (ISO 8601), up to 30 days ahead. Example: 2026-11-20T09:00:00.000+0000
- `subject` (`string`, optional): Subject line. Required unless template_id is set. Example: Your order has shipped
- `template_id` (`string`, optional): ID of an Infobip email template to use instead of subject/text/html. Example: 200000000094001
- `text` (`string`, optional): Plain-text body. Example: Hi John, your order 1234 has shipped.
- `track_clicks` (`boolean`, optional): Track link clicks. Example: true
- `track_opens` (`boolean`, optional): Track opens. Example: true

Example input: `{"sender":"<sender>","to":["john.smith@example.com"]}`

### `infobip_email_suppressions_add`

Add Email Suppressions · Write

Add email addresses to a sending domain's bounce or complaint suppression list so Infobip stops sending to them.
Returns 204 on success.
Use infobip_email_suppressions_add to honour opt-outs or known bad addresses.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `suppressions` (`array`, required): Entries, each with domainName, type (BOUNCE or COMPLAINT) and emailAddress (a list of addresses). Up to 10,000 addresses. Example: [{"domainName": "mail.example.com", "type": "COMPLAINT", "emailAddress": ["john.smith@example.com"]}]

Example input: `{"suppressions":[]}`

### `infobip_number_purchase`

Buy Number · Write

Buy an available phone number for your Infobip account. This charges the setup fee and monthly price.
Returns the purchased number with its numberKey.
Use infobip_number_purchase with a numberKey or number from infobip_numbers_available_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `application_id` (`string`, optional): Application to link the number to. Example: my-application
- `entity_id` (`string`, optional): Entity to link the number to. Example: my-entity
- `number` (`string`, optional): The available number. Use either number or number_key. Example: 447860041117
- `number_key` (`string`, optional): numberKey of the available number. Use either number_key or number. Example: E1C5F6B8F1C1D8D6E4C0C3B4B1F0A2C3

Example input: `{}`

### `infobip_number_update`

Update Owned Number · Write

Link an owned Infobip number to an application (and optionally an entity).
Returns the updated number.
Use infobip_number_update to route a number's traffic to an application.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `application_id` (`string`, required): Application ID to link. Example: my-application
- `number_key` (`string`, required): Unique key of the number. Example: E1C5F6B8F1C1D8D6E4C0C3B4B1F0A2C3
- `entity_id` (`string`, optional): Entity ID to link. Example: my-entity

Example input: `{"application_id":"<application_id>","number_key":"<number_key>"}`

### `infobip_sms_delivery_reports_get`

Get SMS Delivery Reports · Write

Fetch SMS delivery reports that have not been fetched or pushed to a webhook yet. Each report is returned only once.
Returns results with messageId, bulkId, to, sentAt, doneAt, status, error and price.
Use infobip_sms_delivery_reports_get only when no notify_url is set. Use infobip_sms_logs_list to read status repeatedly.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `bulk_id` (`string`, optional): Only reports for this bulk. Example: 2034072219640523072
- `limit` (`integer`, optional): Maximum reports to return, up to 1000. Defaults to 50. Example: 100
- `message_id` (`string`, optional): Only the report for this message. Example: 2250be2d4219-3af1-78856-aabe-1362af1edfd2

Example input: `{}`

### `infobip_sms_inbound_get`

Get Inbound SMS · Write

Fetch inbound SMS received on your Infobip numbers that have not been fetched or forwarded yet. Each message is returned only once.
Returns results with messageId, from, to, text, keyword, receivedAt and price.
Use infobip_sms_inbound_get to read replies when your number has no forwarding URL set.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `limit` (`integer`, optional): Maximum messages to return, up to 1000. Defaults to 50. Example: 100

Example input: `{}`

### `infobip_sms_scheduled_reschedule`

Reschedule SMS · Write

Move a scheduled bulk of SMS to a new send time.
Returns bulkId and the new sendAt.
Use infobip_sms_scheduled_reschedule before the bulk is sent. Use infobip_sms_scheduled_status_update to pause or cancel it.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, required): The bulkId of the scheduled send. Example: order-batch-2026-11-13
- `send_at` (`string`, required): New send time (yyyy-MM-ddTHH:mm:ss.SSSZ), up to 180 days ahead. Example: 2026-11-21T09:00:00.000+0000

Example input: `{"bulk_id":"<bulk_id>","send_at":"<send_at>"}`

### `infobip_sms_send`

Send SMS · Write

Send an SMS to one or more phone numbers through Infobip, optionally scheduled for later.
Returns bulkId and messages with messageId, destination and status (group, name, description).
Use infobip_sms_send to send SMS. Use infobip_sms_preview to check length and parts first, and infobip_sms_logs_list to check delivery.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `text` (`string`, required): Message text. Long texts are split into several parts and billed per part. Example: Your code is 482910
- `to` (`array`, required): Recipient phone numbers in international format without + (up to thousands per request). Example: ["41793026727"]
- `bulk_id` (`string`, optional): Your own ID for this send, used to look up or reschedule it. Generated if omitted. Example: order-batch-2026-11-13
- `callback_data` (`string`, optional): Your own data, returned in the delivery report (up to 4000 characters). Example: order-1234
- `campaign_reference_id` (`string`, optional): Your campaign ID, for reporting. Example: black-friday-2026
- `language_code` (`string`, optional): National language shift table code, for example TR, ES or PT, or AUTODETECT. Example: AUTODETECT
- `notify_url` (`string`, optional): URL that receives delivery reports for these messages. Example: https://example.com/infobip/sms-reports
- `send_at` (`string`, optional): Schedule the send for this time (yyyy-MM-ddTHH:mm:ss.SSSZ), up to 180 days ahead. Example: 2026-11-20T09:00:00.000+0000
- `sender` (`string`, optional): Sender ID: an alphanumeric name (up to 11 characters) or a number, where the destination country allows it. Defaults to the account sender. Example: InfoSMS
- `transliteration` (`string`, optional): Replace characters outside the GSM alphabet to keep messages short, for example TURKISH, GREEK, CENTRAL_EUROPEAN or NON_UNICODE. Example: NON_UNICODE
- `validity_period_minutes` (`integer`, optional): Minutes Infobip keeps trying to deliver (max 2880, 48 hours). Example: 60

Example input: `{"text":"<text>","to":["41793026727"]}`

### `infobip_viber_send`

Send Viber Message · Write

Send a Viber Business message (text, image or file, optionally with a button) through Infobip, with optional SMS failover.
Returns bulkId and messages with messageId, destination and status.
Use infobip_viber_send for Viber users when you have an approved Viber Business sender.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `content_type` (`string`, required): TEXT, IMAGE or FILE. Example: TEXT. One of: `TEXT`, `IMAGE`, `FILE`.
- `sender` (`string`, required): Your approved Viber Business sender name. Example: AcmeViber
- `to` (`array`, required): Recipient phone numbers in international format without +. Example: ["41793026727"]
- `button_title` (`string`, optional): Optional button label (TEXT and IMAGE), set together with button_url. Example: Track order
- `button_url` (`string`, optional): URL the button opens. Example: https://example.com/track/1234
- `callback_data` (`string`, optional): Your own data, returned in delivery reports. Example: order-1234
- `file_name` (`string`, optional): File name with extension (FILE). Example: invoice.pdf
- `media_url` (`string`, optional): Public URL of the image (IMAGE) or file (FILE). Example: https://example.com/files/receipt.jpg
- `notify_url` (`string`, optional): URL that receives delivery reports. Example: https://example.com/infobip/viber-reports
- `sms_failover_sender` (`string`, optional): SMS sender for the failover message. Example: InfoSMS
- `sms_failover_text` (`string`, optional): If set, Infobip sends this SMS when Viber delivery fails. Example: Your order has shipped.
- `text` (`string`, optional): Message text (TEXT), up to 1000 characters. With IMAGE it is shown as the caption. Example: Your order has shipped.

Example input: `{"content_type":"TEXT","sender":"<sender>","to":["41793026727"]}`

### `infobip_whatsapp_audio_send`

Send WhatsApp Audio · Write

Send a WhatsApp audio file (AAC, MP3, OGG and more, up to 16 MB) through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `media_url` (`string`, required): Public HTTPS URL of the file. Infobip downloads it when sending. Example: https://example.com/files/receipt.jpg
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"from":"<from>","media_url":"<media_url>","to":"<to>"}`

### `infobip_whatsapp_buttons_send`

Send WhatsApp Reply Buttons · Write

Send a WhatsApp message with up to three reply buttons through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body_text` (`string`, required): Message text above the buttons, up to 1024 characters. Example: Confirm your delivery slot?
- `buttons` (`array`, required): One to three reply buttons, each {"type": "REPLY", "id": "...", "title": "..."} (title up to 20 characters). The id comes back when the user taps it. Example: [{"type": "REPLY", "id": "yes", "title": "Yes"}, {"type": "REPLY", "id": "no", "title": "No"}]
- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `footer_text` (`string`, optional): Optional footer, up to 60 characters. Example: Reply within 24 hours
- `header_text` (`string`, optional): Optional text header, up to 60 characters. Example: Delivery
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"body_text":"<body_text>","buttons":[{"type":"REPLY","id":"yes","title":"Yes"},{"type":"REPLY","id":"no","title":"No"}],"from":"<from>","to":"<to>"}`

### `infobip_whatsapp_document_send`

Send WhatsApp Document · Write

Send a WhatsApp document (PDF, Office files and more, up to 100 MB) through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `media_url` (`string`, required): Public HTTPS URL of the file. Infobip downloads it when sending. Example: https://example.com/files/receipt.jpg
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `caption` (`string`, optional): Optional caption shown with the media, up to 3000 characters. Example: Your receipt
- `filename` (`string`, optional): File name shown to the recipient. Example: invoice-1234.pdf
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"from":"<from>","media_url":"<media_url>","to":"<to>"}`

### `infobip_whatsapp_image_send`

Send WhatsApp Image · Write

Send a WhatsApp image (JPG or PNG, up to 5 MB) through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `media_url` (`string`, required): Public HTTPS URL of the file. Infobip downloads it when sending. Example: https://example.com/files/receipt.jpg
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `caption` (`string`, optional): Optional caption shown with the media, up to 3000 characters. Example: Your receipt
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"from":"<from>","media_url":"<media_url>","to":"<to>"}`

### `infobip_whatsapp_list_send`

Send WhatsApp List · Write

Send a WhatsApp list message with selectable rows through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body_text` (`string`, required): Message text, up to 1024 characters. Example: Choose a delivery slot
- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `list_title` (`string`, required): Label of the button that opens the list, up to 20 characters. Example: Slots
- `sections` (`array`, required): Up to 10 sections, each {"title": "...", "rows": [{"id": "...", "title": "...", "description": "..."}]} with up to 10 rows in total. Example: [{"title": "Tomorrow", "rows": [{"id": "am", "title": "Morning", "description": "8-12"}, {"id": "pm", "title": "Afternoon"}]}]
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `footer_text` (`string`, optional): Optional footer. Example: Times are local
- `header_text` (`string`, optional): Optional text header. Example: Delivery
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"body_text":"<body_text>","from":"<from>","list_title":"<list_title>","sections":[],"to":"<to>"}`

### `infobip_whatsapp_location_send`

Send WhatsApp Location · Write

Send a WhatsApp location pin through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `latitude` (`number`, required): Latitude, -90 to 90. Example: 44.7866
- `longitude` (`number`, required): Longitude, -180 to 180. Example: 20.4489
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `address` (`string`, optional): Place address. Example: Bulevar Mihajla Pupina 10, Belgrade
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `name` (`string`, optional): Place name. Example: Infobip Belgrade
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"from":"<from>","latitude":44.7866,"longitude":20.4489,"to":"<to>"}`

### `infobip_whatsapp_message_mark_read`

Mark WhatsApp Message Read · Write

Mark an inbound WhatsApp message as read, which shows the blue ticks to the user.
Returns 200 with no body on success.
Use infobip_whatsapp_message_mark_read after processing an inbound message.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `message_id` (`string`, required): ID of the inbound message. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da
- `sender` (`string`, required): Your WhatsApp sender number that received the message, international format without +. Example: 441134960000

Example input: `{"message_id":"<message_id>","sender":"<sender>"}`

### `infobip_whatsapp_template_create`

Create WhatsApp Template · Write

Submit a new WhatsApp message template to Meta for approval through Infobip.
Returns the template with id and status (usually PENDING until Meta reviews it).
Use infobip_whatsapp_template_create for new notifications; send it with infobip_whatsapp_template_send once approved.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `category` (`string`, required): MARKETING, UTILITY or AUTHENTICATION. Each category allows different structure fields. Example: UTILITY. One of: `MARKETING`, `AUTHENTICATION`, `UTILITY`.
- `language` (`string`, required): Template language code, for example en, en_GB, es or pt_BR. Example: en_GB
- `name` (`string`, required): Template name: lowercase letters, digits and underscores. Example: order_shipped
- `sender` (`string`, required): Your WhatsApp sender number, international format without +. Example: 441134960000
- `structure` (`object`, required): Template content: body with text (placeholders as {{1}}) and examples, plus optional header, footer and buttons. Example: {"body": {"text": "Hi {{1}}, order {{2}} has shipped.", "examples": ["Ana", "1234"]}, "footer": {"text": "Acme"}}

Example input: `{"category":"MARKETING","language":"<language>","name":"<name>","sender":"<sender>","structure":{}}`

### `infobip_whatsapp_template_send`

Send WhatsApp Template · Write

Send an approved WhatsApp template message through Infobip, filling its placeholders. Templates can start a conversation at any time.
Returns bulkId and messages with messageId, to and status.
Use infobip_whatsapp_template_send outside the 24-hour window or for notifications. Use infobip_whatsapp_templates_list to find template names.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `language` (`string`, required): Template language code, for example en, en_GB or pt_BR. Example: en_GB
- `placeholders` (`array`, required): Values for the body placeholders {{1}}, {{2}} and so on, in order. Pass an empty list for a template without placeholders. Example: ["Ana", "1234"]
- `template_name` (`string`, required): Name of the approved template. Example: order_shipped
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `buttons` (`array`, optional): Button values when the template has dynamic buttons, in order: {"type": "QUICK_REPLY", "parameter": "..."} or {"type": "URL", "parameter": "url-suffix"}. Example: [{"type": "URL", "parameter": "track/1234"}]
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `header` (`object`, optional): Header values when the template has one: {"type": "TEXT", "placeholder": "..."}, or {"type": "IMAGE" | "VIDEO" | "DOCUMENT", "mediaUrl": "..."}, or LOCATION with latitude and longitude. Example: {"type": "IMAGE", "mediaUrl": "https://example.com/files/banner.jpg"}
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports

Example input: `{"from":"<from>","language":"<language>","placeholders":["Ana","1234"],"template_name":"<template_name>","to":"<to>"}`

### `infobip_whatsapp_template_update`

Edit WhatsApp Template · Write

Edit a WhatsApp template's structure or (if not yet approved) its category; the edit goes back to Meta for review.
Returns 200 on success.
Use infobip_whatsapp_template_update to fix a rejected template or update wording.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `sender` (`string`, required): Your WhatsApp sender number, international format without +. Example: 441134960000
- `template_id` (`string`, required): Numeric template ID. Example: 111
- `category` (`string`, optional): New category (not allowed once approved). Example: UTILITY. One of: `MARKETING`, `AUTHENTICATION`, `UTILITY`.
- `structure` (`object`, optional): New template content in the same shape as infobip_whatsapp_template_create. Example: {"body": {"text": "Hi {{1}}, your order {{2}} is on its way.", "examples": ["Ana", "1234"]}}

Example input: `{"sender":"<sender>","template_id":"<template_id>"}`

### `infobip_whatsapp_text_send`

Send WhatsApp Text · Write

Send a WhatsApp text message through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `text` (`string`, required): Message text, up to 4096 characters. Example: Your order 1234 has shipped.
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `preview_url` (`boolean`, optional): Show a link preview for the first URL in the text. Example: true
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"from":"<from>","text":"<text>","to":"<to>"}`

### `infobip_whatsapp_video_send`

Send WhatsApp Video · Write

Send a WhatsApp video (MP4 or 3GPP, up to 16 MB) through Infobip inside the 24-hour customer service window.
Returns messageId, to and status (group, name, description).
Use this inside the 24-hour window after the user's last message. Use infobip_whatsapp_template_send to start a conversation.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `from` (`string`, required): Your registered WhatsApp sender number, in international format without +. Example: 441134960000
- `media_url` (`string`, required): Public HTTPS URL of the file. Infobip downloads it when sending. Example: https://example.com/files/receipt.jpg
- `to` (`string`, required): Recipient's WhatsApp number in international format without +, or a business-scoped user ID. Example: 441134960001
- `callback_data` (`string`, optional): Your own data, returned in the delivery report. Example: order-1234
- `caption` (`string`, optional): Optional caption shown with the media, up to 3000 characters. Example: Your receipt
- `notify_url` (`string`, optional): URL that receives delivery and seen reports for this message. Example: https://example.com/infobip/whatsapp-reports
- `reply_to_message_id` (`string`, optional): ID of an inbound message to quote as a reply. Example: a28dd97c-1ffb-4fcf-99f1-0b557ed381da

Example input: `{"from":"<from>","media_url":"<media_url>","to":"<to>"}`

### `infobip_email_domain_delete`

Delete Email Domain · Destructive

Delete a sending domain from your Infobip account; it can no longer send.
Returns 204 on success.
Use infobip_email_domain_delete to retire a domain.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `domain_name` (`string`, required): The domain name. Example: mail.example.com

Example input: `{"domain_name":"<domain_name>"}`

### `infobip_email_scheduled_status_update`

Pause, Resume or Cancel Scheduled Email · Destructive

Pause, resume or cancel a scheduled bulk of emails. A canceled bulk cannot be resumed.
Returns bulkId and the new status.
Use infobip_email_scheduled_status_update with PAUSED, PENDING (resume) or CANCELED.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, required): The bulkId of the scheduled send. Example: receipts-2026-11-13
- `status` (`string`, required): PAUSED to pause, PENDING to resume, CANCELED to cancel for good. Example: CANCELED. One of: `PENDING`, `PAUSED`, `CANCELED`.

Example input: `{"bulk_id":"<bulk_id>","status":"PENDING"}`

### `infobip_email_suppressions_delete`

Remove Email Suppressions · Destructive

Remove email addresses from a sending domain's suppression lists so Infobip can send to them again.
Returns 204 on success.
Use infobip_email_suppressions_delete only when you are sure an address is valid again.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `suppressions` (`array`, required): Entries, each with domainName, type (BOUNCE, COMPLAINT or OVER_QUOTA) and emailAddress (a list of addresses). Example: [{"domainName": "mail.example.com", "type": "BOUNCE", "emailAddress": ["john.smith@example.com"]}]

Example input: `{"suppressions":[]}`

### `infobip_number_cancel`

Cancel Number · Destructive

Cancel (release) a phone number your Infobip account owns. It stops working at the end of the billing period.
Returns the canceled number.
Use infobip_number_cancel to stop paying for a number.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `number_key` (`string`, required): Unique key of the number. Example: E1C5F6B8F1C1D8D6E4C0C3B4B1F0A2C3

Example input: `{"number_key":"<number_key>"}`

### `infobip_sms_scheduled_status_update`

Pause, Resume or Cancel Scheduled SMS · Destructive

Pause, resume or cancel a scheduled bulk of SMS. A canceled bulk cannot be resumed.
Returns bulkId and the new status.
Use infobip_sms_scheduled_status_update with PAUSED, PENDING (resume) or CANCELED.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `bulk_id` (`string`, required): The bulkId of the scheduled send. Example: order-batch-2026-11-13
- `status` (`string`, required): PAUSED to pause, PENDING to resume, CANCELED to cancel for good. Example: PAUSED. One of: `PENDING`, `PAUSED`, `CANCELED`.

Example input: `{"bulk_id":"<bulk_id>","status":"PENDING"}`

### `infobip_whatsapp_template_delete`

Delete WhatsApp Template · Destructive

Delete a WhatsApp template by name, in every language it exists in.
Returns 200 on success.
Use infobip_whatsapp_template_delete to remove templates no longer used. The name cannot be reused for 30 days.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `sender` (`string`, required): Your WhatsApp sender number, international format without +. Example: 441134960000
- `template_name` (`string`, required): Template name. Example: order_shipped

Example input: `{"sender":"<sender>","template_name":"<template_name>"}`

## Related

Other Communication connectors ([all 132](/agentkit/connectors/?category=communication)):

- [Gmail](/agentkit/connectors/gmail/): Scalekit connector, OAuth, 48 tools
- [Slack](/agentkit/connectors/slack/): Scalekit connector, OAuth, 96 tools
- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
