Exchange apps and integrations

To connect a third-party product to Infobip, there are two build paths. Which one you build depends on where your users work:

• Exchange app: Extends Infobip. It runs inside Infobip products, for example as a Bot block, a context card, a data sync, or a Journey element. Build this when your users work mostly in Infobip.
• Integration: Extends your platform with Infobip. It puts Infobip channels (SMS, WhatsApp, RCS, Viber, Email, Voice) inside your own product. Build this when your users work mostly in your product.

Both paths require becoming an Infobip partner. For the full decision, including the integration types and how they combine, see Build for the Infobip ecosystem. To build, start with the Exchange overview or the Integrations overview.

What you build with

Both paths call the Infobip REST API, but the build models differ:

• Exchange app: Built on integration points and an app manifest, plus Exchange OAuth to act on behalf of a customer. The manifest connects your endpoints to Chatbots, Inbox, or Journeys. See Build apps for Exchange.
• Integration: Mostly channel API calls surfaced in the UI of your platform.

If your integration or Exchange app calls Infobip channel APIs, you must append an integration identifier to those calls. Contact exchange@infobip.com for details.

For either path, the REST API is the foundation. Call it directly, or use an official SDK to skip the boilerplate. Before you build, read about API authentication and error handling.

To connect an AI agent to the platform rather than build an app, see MCP servers.