Infobip

Infobip is a cloud communications (CPaaS) platform for sending and managing SMS, WhatsApp, and Email messages across a single API. The Nexla connector reads delivery reports, message logs, templates, and phone-number inventory, and sends outbound SMS, WhatsApp, and Email messages.

Power end-to-end data operations for your Infobip API with Nexla. Our bi-directional Infobip connector is purpose-built for Infobip, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Infobip or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Infobip workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Infobip credential, you need an Infobip account and an API Key. Infobip authenticates every API request with an API Key sent in the Authorization header using the App scheme (for example, Authorization: App {your_api_key}).

To obtain an API Key, follow these steps:

1. Sign in to your Infobip account at portal.infobip.com.

2. Open the Developer Tools section from the sidebar, then select API Keys.

3. Click Create API key and enter a descriptive name for the key (e.g., "Nexla Integration").

4. Select the API scopes to grant. Scopes limit the key to a subset of API endpoints, so include the scopes that match your intended use (for example, SMS, WhatsApp, Email, and Numbers).

5. Create the key and copy the generated API Key value immediately. Store it securely, as it authenticates all requests made on behalf of your account.

Because an API Key is tied to your Infobip account, keep it confidential and rotate it if it is ever exposed. For complete information about authentication, scopes, and available endpoints, see the Infobip API documentation and the Infobip API authorization guide.

Authenticate

Credentials required

Infobip authenticates requests with an API Key generated in the Infobip portal (Settings > API Keys), sent as 'Authorization: App <api_key>' on every request.

Field	Required	Secret	Description
API Key	Yes	Yes	Infobip API Key generated at portal.infobip.com > Settings > API Keys.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Infobip API Key in the API Key field. This key authenticates Nexla with the Infobip API and is sent in the Authorization header on every request, so it must be kept confidential.

   If your API Key is compromised, revoke it in the Infobip portal under Developer Tools > API Keys and generate a new one. Ensure the key includes the API scopes required for the endpoints you intend to use.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Infobip connector tile, then select the credential that will be used to connect to Infobip, and click Next; or, create a new Infobip credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Infobip endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] Get SMS Delivery Reports

Get real-time delivery reports for sent SMS messages (available for approximately 48 hours after sending).

• Optionally filter results by Bulk ID, Message ID, and Limit (maximum number of reports to return). All parameters are optional; leave them empty to retrieve the most recent reports.

Delivery reports are available for a limited window after a message is sent, so schedule this source to run frequently enough to capture reports before they expire. For details, see the Infobip API documentation.

[Rest API] Get SMS Logs

Get historical logs of sent SMS messages (up to one year of retention).

• Optionally filter results by Sender, Destination, Bulk ID, Sent Since and Sent Until (ISO 8601 lower and upper bounds on sent time), and Limit. All parameters are optional.

Use the Sent Since and Sent Until bounds to page through historical data by time range. For details, see the Infobip API documentation.

[Rest API] Get SMS Inbox (MO) Reports

Get received (mobile-originated) SMS messages sent to your Infobip number(s).

• Optionally set Limit to cap the number of inbound messages returned in a single request.

[Rest API] Get SMS Bulk Status

Get the status (such as PENDING, PAUSED, or PROCESSING) of a scheduled SMS bulk.

• Enter the Bulk ID of the scheduled SMS message(s). This parameter is required.

[Rest API] List WhatsApp Templates

List WhatsApp message templates across all senders on the account.

• Optionally filter by Sender (WhatsApp sender number) and Status, and page through results with Page and Page Size. All parameters are optional.

[Rest API] List WhatsApp Sender Templates

List WhatsApp message templates registered for a specific sender.

• Enter the Sender (WhatsApp sender number) whose templates you want to list. This parameter is required.

[Rest API] Get WhatsApp Sender Quality

Get the quality rating and messaging limit tier for WhatsApp sender(s).

• Enter one or more Senders as a comma-separated list of WhatsApp sender numbers. This parameter is required.

[Rest API] Get Email Logs

Get historical logs of sent email messages.

• Optionally filter by Sender, Destination, Bulk ID, Sent Since and Sent Until (ISO 8601 bounds on sent time), and Limit. All parameters are optional.

[Rest API] Get Email Delivery Reports

Get real-time delivery reports for sent email messages.

• Optionally filter by Bulk ID, Message ID, and Limit. All parameters are optional.

[Rest API] Get Email Bulk Status

Get the status of a scheduled email bulk.

• Enter the Bulk ID of the scheduled email message(s). This parameter is required.

[Rest API] List Email Domains

List sender domains registered for sending email.

• Optionally page through results with Page Size and Page. All parameters are optional.

[Rest API] List Email Suppressions

List suppressed email addresses (unsubscribed, bounced, or complained) for a domain.

• Enter the Domain Name (sender domain to check suppressions for) and the Suppression Type (for example, unsubscribe, hardBounce, or complaint). Both parameters are required.

[Rest API] List Email Templates

List reusable email templates on the account.

• Optionally page through results with Page and Page Size. All parameters are optional.

[Rest API] List Numbers

List phone numbers owned by the account.

• Optionally filter by Number and page through results with Limit and Page. All parameters are optional.

[Rest API] List Available Numbers

Search Infobip's inventory of phone numbers available for purchase.

• Optionally filter by Country (ISO country code), Capabilities (for example, SMS, VOICE, or MMS), and Limit. All parameters are optional.

[Rest API] Get Number

Get details of a single owned phone number.

• Enter the Number Key, the unique key of the owned phone number. This parameter is required.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Infobip data sources can also be manually configured to ingest data from any valid Infobip API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Infobip data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Infobip destination, and select the Send to Destination option from the menu. Select the Infobip connector from the list of available destination connectors, then select the credential that will be used to connect to Infobip, and click Next; or, create a new Infobip credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Infobip endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Send SMS (Advanced)

Send single or multiple SMS messages with advanced options such as scheduling and personalization.

• Each record from your Nexset is sent as a JSON request body to the Infobip SMS endpoint. Structure the record to match the Infobip advanced SMS message format, including destinations and message text.

The request body must match the Infobip API's expected format. For details on message structure and available options, see the Infobip API documentation.

[Rest API] Send SMS Messages

Send SMS message(s) via the unified messages endpoint.

• Each record from your Nexset is sent as a JSON request body. Structure the record to match the Infobip messages format for the SMS channel.

[Rest API] Send WhatsApp Text Message

Send a free-form WhatsApp text message. This requires an open session with the recipient.

• Each record from your Nexset is sent as a JSON request body containing the sender, destination, and text content. A session is open only after the recipient has messaged you within the allowed window.

Free-form WhatsApp messages can only be sent inside an active customer-initiated session. To start a new conversation, use the Send WhatsApp Template Message endpoint instead. For details, see the Infobip API documentation.

[Rest API] Send WhatsApp Template Message

Send a pre-approved WhatsApp template message. This can be used to open a new session with a recipient.

• Each record from your Nexset is sent as a JSON request body referencing an approved template and its placeholder values.

[Rest API] Send WhatsApp Document Message

Send a WhatsApp message with a document attachment.

• Each record from your Nexset is sent as a JSON request body containing the sender, destination, and the URL of the document to attach.

[Rest API] Send WhatsApp Image Message

Send a WhatsApp message with an image attachment.

• Each record from your Nexset is sent as a JSON request body containing the sender, destination, and the URL of the image to attach.

[Rest API] Send Email Messages

Send email message(s) via the JSON messages endpoint.

• Each record from your Nexset is sent as a JSON request body containing the sender, recipients, subject, and content. The sender domain must be registered and verified on your Infobip account.

[Rest API] Create Email Domain

Register a new sender domain for sending email.

• Each record from your Nexset is sent as a JSON request body containing the domain to register. After registration, complete DNS verification in the Infobip portal before sending from the domain.

[Rest API] Create Email Suppression

Add an email address to the suppression list for a domain.

• Each record from your Nexset is sent as a JSON request body containing the domain and the address(es) to suppress. Suppressed addresses are excluded from future email sends.

[Rest API] Assign Number SMS Configuration

Configure SMS capability (such as forwarding and keywords) for an owned phone number.

• Enter the Number Key, the unique key of the owned phone number, as the required endpoint parameter. Each record from your Nexset is sent as a JSON request body containing the SMS configuration to apply.

Manual configuration

Infobip destinations can also be manually configured to send data to any valid Infobip API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Infobip APIs expect JSON-formatted request bodies for messaging and configuration operations. Ensure each Nexset record matches the structure required by the target endpoint.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Infobip endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Infobip endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.