Infobip OpenAPI Specification
Infobip OpenAPI Specification from Infobip — 652 path(s) described in OpenAPI.
OpenAPI Specification
{
"openapi":"3.1.0",
"info":{
"title":"Infobip OpenAPI Specification",
"description":"OpenAPI Specification that contains all public endpoints and webhooks.",
"contact":{
"name":"Infobip support",
"email":"support@infobip.com"
},
"version":"3.210.0",
"x-generatedAt":"2026-07-23T15:23:37.825639538Z"
},
"tags":[
{
"name":"customer-engagement",
"description":"Complete solutions that will help you drive better outcomes for your customers and business across the entire customer journey.\n",
"x-type":"category",
"x-displayName":"Customer Engagement"
},
{
"name":"people",
"description":"Build rich profiles for each person to create audience segments for more precise targeting. Manage duplicates and import your data over API.\n\nEvents reflect actions that end users take on your website or in your mobile application.\n\nEvents API is a robust way to send those events to Infobip. Event can be sent only to an existing person in People module and an event definition should be created beforehand to describe contents of the event.\n\nOther events tracking options:\n* [ JavaScript SDK ](https://github.com/infobip/people-web-sdk)\n* [iOS SDK](https://github.com/infobip/mobile-messaging-sdk-ios/wiki/Events)\n* [Android SDK](https://github.com/infobip/mobile-messaging-sdk-android/wiki/Events)\n",
"x-type":"product",
"x-displayName":"People"
},
{
"name":"person-profile",
"description":"",
"x-type":"section",
"x-displayName":"Person profile"
},
{
"name":"company-profile",
"description":"",
"x-type":"section",
"x-displayName":"Company profile"
},
{
"name":"tags",
"description":"",
"x-type":"section",
"x-displayName":"Tags"
},
{
"name":"custom-attributes",
"description":"",
"x-type":"section",
"x-displayName":"Custom attributes"
},
{
"name":"custom-attributes-lists",
"description":"",
"x-type":"section",
"x-displayName":"Custom attributes: Lists"
},
{
"name":"contact-information:-push",
"description":"",
"x-type":"section",
"x-displayName":"Contact Information: Push"
},
{
"name":"events",
"description":"",
"x-type":"section",
"x-displayName":"Events"
},
{
"name":"segments",
"description":"",
"x-type":"section",
"x-displayName":"Segments"
},
{
"name":"moments",
"description":"Use Moments to set up and manage automated messaging campaigns with your customers by building conversation workflows.\n",
"x-type":"product",
"x-displayName":"Moments"
},
{
"name":"flow",
"description":"[Flow](https://www.infobip.com/docs/moments/manage-flow) is the Infobip communication builder that helps you create and manage messaging campaigns. The Flows API allows you to add or remove people from communication programmatically for flows with an [active status](https://www.infobip.com/docs/moments/manage-flow#launch-create).\n\nUse the Add Participants to flow endpoint to a person or batches of persons (between 1-1000 persons). The method works asynchronously to queue and process participants at a rate of 10 requests per second. For reporting of operation results, use the notifyUrl field to provide a URL of your callback server that will receive a status report or use the Get a report on participants added to Flow endpoint.\n",
"x-type":"module",
"x-displayName":"Flow"
},
{
"name":"forms",
"description":"[Forms](https://www.infobip.com/docs/forms) is an Infobip platform solution to collect customer data that you can then use for messaging or analytics. Forms API allows you to retrieve an active form from your web page, track events, or collect the field values when the end user submits a form.\n",
"x-type":"module",
"x-displayName":"Forms"
},
{
"name":"conversations",
"description":"Conversations is a solution that allows Enterprises to engage in conversations with their customers over multiple channels. The solution is available either as a web-based cloud platform web interface or over HTTP API for 2-way messaging over SMS, WhatsApp, Viber, and Facebook messenger. It supports conversation threading, conversation management including queues and routing, agent assignment, resolution management and conversation history overview.",
"x-type":"product",
"x-displayName":"Conversations"
},
{
"name":"conversation-management",
"description":"",
"x-type":"section",
"x-displayName":"Conversation management"
},
{
"name":"conversation-tags",
"description":"",
"x-type":"section",
"x-displayName":"Conversation tags"
},
{
"name":"conversation-messages",
"description":"",
"x-type":"section",
"x-displayName":"Conversation messages"
},
{
"name":"conversation-events",
"description":"",
"x-type":"section",
"x-displayName":"Conversation events"
},
{
"name":"conversation-notes",
"description":"",
"x-type":"section",
"x-displayName":"Conversation notes"
},
{
"name":"conversation-agents",
"description":"",
"x-type":"section",
"x-displayName":"Conversation agents"
},
{
"name":"conversation-queues",
"description":"",
"x-type":"section",
"x-displayName":"Conversation queues"
},
{
"name":"conversation-routing",
"description":"",
"x-type":"section",
"x-displayName":"Conversation routing"
},
{
"name":"bots",
"description":"",
"x-type":"section",
"x-displayName":"Bots"
},
{
"name":"metadata",
"description":"",
"x-type":"section",
"x-displayName":"Metadata"
},
{
"name":"templates",
"description":"",
"x-type":"section",
"x-displayName":"Templates"
},
{
"name":"conversation-forms",
"description":"",
"x-type":"section",
"x-displayName":"Conversation forms"
},
{
"name":"account-configuration",
"description":"",
"x-type":"section",
"x-displayName":"Account Configuration"
},
{
"name":"agent-configuration-calls",
"description":"",
"x-type":"section",
"x-displayName":"Agent Configuration (Calls)"
},
{
"name":"outbound-call-conversation-calls",
"description":"",
"x-type":"section",
"x-displayName":"Outbound Call Conversation (Calls)"
},
{
"name":"waiting-strategies-calls",
"description":"",
"x-type":"section",
"x-displayName":"Waiting Strategies (Calls)"
},
{
"name":"recording-configuration-calls",
"description":"",
"x-type":"section",
"x-displayName":"Recording Configuration (Calls)"
},
{
"name":"recording-metadata-calls",
"description":"",
"x-type":"section",
"x-displayName":"Recording metadata (Calls)"
},
{
"name":"recording-calls",
"description":"",
"x-type":"section",
"x-displayName":"Recording (Calls)"
},
{
"name":"wrap-up-configuration-calls",
"description":"",
"x-type":"section",
"x-displayName":"Wrap Up Configuration (Calls)"
},
{
"name":"wrap-up-time-calls",
"description":"",
"x-type":"section",
"x-displayName":"Wrap Up Time (Calls)"
},
{
"name":"transfers-calls",
"description":"",
"x-type":"section",
"x-displayName":"Transfers (Calls)"
},
{
"name":"transfer-to-external-number-configuration-calls",
"description":"",
"x-type":"section",
"x-displayName":"Transfer to External Number Configuration (Calls)"
},
{
"name":"transfer-strategy-calls",
"description":"",
"x-type":"section",
"x-displayName":"Transfer Strategy (Calls)"
},
{
"name":"call-hold-calls",
"description":"",
"x-type":"section",
"x-displayName":"Call Hold (Calls)"
},
{
"name":"hold-configuration-calls",
"description":"",
"x-type":"section",
"x-displayName":"Hold Configuration (Calls)"
},
{
"name":"call-timeout-calls",
"description":"",
"x-type":"section",
"x-displayName":"Call Timeout (Calls)"
},
{
"name":"working-hours",
"description":"",
"x-type":"section",
"x-displayName":"Working Hours"
},
{
"name":"tts-options-calls",
"description":"",
"x-type":"section",
"x-displayName":"TTS options (Calls)"
},
{
"name":"away-audio-messages",
"description":"",
"x-type":"section",
"x-displayName":"Away Audio Messages"
},
{
"name":"web-forms",
"description":"",
"x-type":"section",
"x-displayName":"Web Forms"
},
{
"name":"answers",
"description":"Answers is the Infobip fully-encompassed chatbot building platform that enables you to build, test, and deploy highly customized chatbots of different types. Multiple channels are supported on Answers like WhatsApp, Facebook Messenger, Live Chat, Apple Business Chat, Viber, Google Business Messaging and other. Communication with Bot is achieved through existing Conversations solution infrastructure which enables integration and switching between communicating with bot and a live agent. Processing can start by receiving MO message or by receiving a trigger event. Users can manage bots (create, update, delete, start and stop bots) through a web interface. For more details, visit the [Answers documentation](https://www.infobip.com/docs/answers).\n\nAnswers API is in Early access stage.\n",
"x-type":"product",
"x-displayName":"Answers"
},
{
"name":"answers-testing-start-test",
"description":"",
"x-type":"section",
"x-displayName":"Start Answers test"
},
{
"name":"answers-testing-stop-test",
"description":"",
"x-type":"section",
"x-displayName":"Stop Answers test"
},
{
"name":"answers-testing-send-message",
"description":"",
"x-type":"section",
"x-displayName":"Send inbound message to test"
},
{
"name":"answers-testing-receive-message",
"description":"",
"x-type":"section",
"x-displayName":"Receive testing message"
},
{
"name":"common-assets",
"description":"Reuse assets created on Infobip SaaS products in order to recreate configuration more easily on a single or across multiple accounts. Export or share Moments flows, Answers chatbots or other SaaS assets from your account and import it on another one. \n\nThis feature is in Early access stage.\n",
"x-type":"product",
"x-displayName":"Common Assets"
},
{
"name":"saas-resource-export",
"description":"",
"x-type":"section",
"x-displayName":"Export resource"
},
{
"name":"saas-resource-import",
"description":"",
"x-type":"section",
"x-displayName":"Import resource"
},
{
"name":"saas-resource-share",
"description":"",
"x-type":"section",
"x-displayName":"Share resource"
},
{
"name":"saas-status-request",
"description":"",
"x-type":"section",
"x-displayName":"Get SaaS request status"
},
{
"name":"customer-engagement-webhooks",
"description":"",
"x-type":"section",
"x-displayName":"Customer Engagement Webhooks"
},
{
"name":"vocalize",
"description":"Infobip Vocalize API allows you to integrate AI Gamification features into your application.\n\nWith Vocalize API, you can:\n\n* Create and manage Vocalize campaigns\n* Receive and process user interactions as part of Vocalize campaigns\n* Retrieve Vocalize campaign results and statistics - both for the campaign as a whole and for individual users\n\nPlease note that Vocalize API is currently in beta, and the API endpoints and functionality may change in the future.\n\n[Learn more about Vocalize use cases](https://www.infobip.com/ai-hub/vocalize)\n",
"x-type":"product",
"x-displayName":"Vocalize"
},
{
"name":"campaign",
"description":"",
"x-type":"section",
"x-displayName":"Vocalize Campaign"
},
{
"name":"score",
"description":"",
"x-type":"section",
"x-displayName":"Vocalize Score"
},
{
"name":"knowledge-base",
"description":"Knowledge Base is a centralized content management system for creating, organizing, and retrieving articles, attachments, and structured content. Content is organized into categories, folders, and a hierarchical content tree. Articles support draft and published workflow statuses, tagging, commenting, and file attachments.",
"x-type":"product",
"x-displayName":"Knowledge Base"
},
{
"name":"knowledge-base-search",
"description":"",
"x-type":"section",
"x-displayName":"Search"
},
{
"name":"knowledge-base-articles",
"description":"",
"x-type":"section",
"x-displayName":"Articles"
},
{
"name":"knowledge-base-categories",
"description":"",
"x-type":"section",
"x-displayName":"Categories"
},
{
"name":"knowledge-base-folders",
"description":"",
"x-type":"section",
"x-displayName":"Folders"
},
{
"name":"knowledge-base-content-tree",
"description":"",
"x-type":"section",
"x-displayName":"Content Tree"
},
{
"name":"knowledge-base-tags",
"description":"",
"x-type":"section",
"x-displayName":"Tags"
},
{
"name":"knowledge-base-attachments",
"description":"",
"x-type":"section",
"x-displayName":"Attachments"
},
{
"name":"ai-hub",
"description":"AI-powered tools and services to help you create smarter and more personalized customer experiences.\n",
"x-type":"category",
"x-displayName":"AI Hub"
},
{
"name":"ai-assistants",
"description":"Infobip AI assistant is a retrieval-augmented generation (RAG) solution that performs tasks based on documents and\ninstructions you specify. This means the AI draws answers directly from your documents, resulting in more accurate\nand relevant responses. For more information on use cases and how to build AI assistants, visit our\n[AI Assistant](https://www.infobip.com/docs/ai-hub/ai-assistant) product documentation.\n\nWith AI Assistants API, you can:\n* Query your existing AI assistants created via [Infobip Portal](https://www.infobip.com/docs/ai-hub/ai-assistant/create-ai-assistant)\n* Retrieve context the AI assistant uses to answer your queries\n",
"x-type":"product",
"x-displayName":"AI Assistants"
},
{
"name":"channels",
"description":"Create a perfect customer experience by using the channels your customer already use and love.\n",
"x-type":"category",
"x-displayName":"Channels"
},
{
"name":"sms",
"description":"SMS (Short Message Service) is the most extensive messaging service available in terms of reach and coverage. A SMS can be sent to and from any mobile device in the world and does not necessarily require a data connection.\n\nInfobip SMS API allows you to send and receive text messages (SMS), fetch or receive delivery reports on your endpoint in real time, and see message logs. You can send messages in different languages, schedule your messages, define delivery time window, and much more.\n\nTo utilize SMS in combination with other channels, check out [Messages API](https://www.infobip.com/docs/api/platform/messages-api).\n",
"x-type":"product",
"x-displayName":"SMS"
},
{
"name":"outbound-sms",
"description":"When you send an SMS to a phone number belonging to an end user's device you are sending an Outbound SMS. Historically, this was and still is referred to as a Mobile Terminated (MT) SMS, though nowadays an SMS is not always sent to a mobile device. In an Outbound SMS you can set the From or Sender field with whatever you have registered or purchased with Infobip, either a Long Number, Short Code, or text based Sender.\n",
"x-type":"module",
"x-displayName":"Outbound SMS"
},
{
"name":"send-message",
"description":"",
"x-type":"section",
"x-displayName":"Send a message"
},
{
"name":"manage-scheduled-sms-messages",
"description":"",
"x-type":"section",
"x-displayName":"Manage Scheduled SMS Messages"
},
{
"name":"confirm-conversion",
"description":"",
"x-type":"section",
"x-displayName":"Confirm conversion"
},
{
"name":"inbound-sms",
"description":"When an end user sends an SMS from their device to a Phone Number or Short Code they have sent an Inbound SMS. The Inbound SMS is routed to the Infobip Platform and Infobip in turn routes the SMS to its Customer who has purchased that Phone Number or Short Code. Inbound SMS, for historical reasons, are referred to as Mobile Originated (MO) SMS.\n",
"x-type":"module",
"x-displayName":"Inbound SMS"
},
{
"name":"logs-and-status-reports",
"description":"Status Reports tell you what happened to the SMS you sent, whether it was successfully delivered or failed to be delivered.\nThey also provide timestamps, network information if available, and on SMS delivery failure, a status code indicating the reason. \nStatus Reports can be pushed in real-time to a Customer's webhook or can be retrieved by an API call. \nLogs provide similar information to Status Reports but are available to query for 48hrs.\n",
"x-type":"module",
"x-displayName":"Logs and Status Reports"
},
{
"name":"mms",
"description":"Infobip MMS API allows you to send and receive MMS messages and receive delivery reports on your endpoint in real time. You can send messages up to 1600 characters in length together with multimedia content including images and videos.\n\nTo utilize MMS in combination with other channels, check out [Messages API](https://www.infobip.com/docs/api/platform/messages-api).\n",
"x-type":"product",
"x-displayName":"MMS"
},
{
"name":"send-mms",
"description":"",
"x-type":"section",
"x-displayName":"Send MMS"
},
{
"name":"receive-mms",
"description":"",
"x-type":"section",
"x-displayName":"Receive MMS"
},
{
"name":"logs-and-status-reports-mms",
"description":"",
"x-type":"section",
"x-displayName":"Logs and Status Reports"
},
{
"name":"voice",
"description":"Infobip Voice API allows you to engage into voice communication with your customer using the Voice API features.\n\nWith Calls API, you can use our granular APIs to create any inbound or outbound voice and video scenario you require. Alternatively, you can use our high level APIs such as:\n\n* Voice Message, to send your customers Text-To-Speech or Pre-recorded message\n* Interactive Voice Response, to create and execute inbound or outbound IVR scenarios enabling interactive communication with your customers\n* Click-to-Call or Number Masking solutions, to establish live conversation between two parties and where you can also protect your customer's identity by using anonymization.\n\nHuge benefit of Voice channel is also that you can reach your customers not only on their mobile but also on their landline phones.\n\nAll Voice calls can be recorded.\n\nTo enable recording feature on Voice calls, please check each Channels Voice API.\n\nYou may fetch recorded audio files using [Recording page](https://portal.infobip.com/channels-and-numbers/channels/voice-and-webrtc/recording) section of the portal.\n\n[Learn more about Voice channel and use cases](https://www.infobip.com/products/voice)\n",
"x-type":"product",
"x-displayName":"Voice"
},
{
"name":"calls",
"description":"With Calls API, you can use our granular APIs to create any inbound or outbound voice and video scenario you require.\n\nEvery inbound connection to, or outbound connection from the Infobip platform is designated as a call leg, or simply put, a call. All API methods under the [**Call Legs**](#channels/voice/calls/call-legs) section allow your application to create, answer and perform actions on individual calls.\n\nApplications can connect multiple calls together, no matter if these calls are inbound or outbound, and no matter the type of the endpoint for each of these calls. When your application needs to connect only two calls together, it is not necessary to explicitly manage conference objects and use conferencing APIs – the *connect* API method on calls will manage these conferencing objects on your behalf. When your application needs to put together 3 or more calls together, you need to use the conference methods and their related actions under the [**Conference Calls**](#channels/voice/calls/conference-calls) section.\n\nA [**Calls Configuration**](https://www.infobip.com/docs/api/channels/voice/calls/calls-configurations) is a logical entity that represents a voice or video application you are implementing and hosting in your own environment, whether on premise or at your cloud hosting services. This logical entity includes only ID and Name, and is a placeholder for linking other configurations with your application.\n\nOne mandatory link to set up is linking you Calls Configuration with Subscriptions. Calls API is event-driven platform, and you need to define webhook to receive those events, as a pre-requisite for executing your business logic. Event subscriptions are defined on [**Subscriptions API**](https://www.infobip.com/docs/api/platform/subscriptions-api). One of available parameters, when defining subscription criteria, is `callsConfigurationId`, which allows you to define webhooks for Calls Configurations you create.\n\nAnother mandatory link to Calls Configurations is actual traffic. The reference of the Calls Configuration (`callsConfigurationId`) must be specified in API calls your application will make towards Infobip to create or manipulate calls, conferences and dialogs, ensuring that corresponding events are routed to the right webhooks. All methods to create and manage Calls Configurations are under the **Configurations** section.\n",
"x-type":"module",
"x-displayName":"Calls"
},
{
"name":"calls-configurations",
"description":"Creating Calls Configuration is precondition for using Calls API. You will find APIs for managing your configurations in this section.",
"x-type":"submodule",
"x-displayName":"Configurations"
},
{
"name":"calls-configuration",
"description":"",
"x-type":"section",
"x-displayName":"Calls configuration"
},
{
"name":"call-legs",
"description":"Every inbound connection to, or outbound connection from the Infobip platform is designated as a call leg, or simply put, a call. All API methods in this section allow your application to create, answer and perform actions on individual calls.",
"x-type":"submodule",
"x-displayName":"Call Legs"
},
{
"name":"calls-management",
"description":"",
"x-type":"section",
"x-displayName":"Calls Management"
},
{
"name":"calls-operations",
"description":"",
"x-type":"section",
"x-displayName":"Calls Operations"
},
{
"name":"application-transfer-management",
"description":"",
"x-type":"section",
"x-displayName":"Application Transfer"
},
{
"name":"conference-calls",
"description":"Applications can connect multiple calls together, no matter if these calls are inbound or outbound, and no matter the type of the endpoint for each of these calls. \n\nWhen your application needs to connect only two calls together, it is not necessary to explicitly manage conference objects and use conferencing APIs – the *connect* API method on calls will manage these conferencing objects on your behalf.\n\nWhen your application needs to put together 3 or more calls together, you need to use the conference methods and their related actions.\n",
"x-type":"submodule",
"x-displayName":"Conference Calls"
},
{
"name":"conference-management",
"description":"",
"x-type":"section",
"x-displayName":"Conference Management"
},
{
"name":"conference-operations",
"description":"",
"x-type":"section",
"x-displayName":"Conference Operations"
},
{
"name":"dialog-calls",
"description":"A Dialog offers another way to connect two calls together without relying on the implicit or explicit creation of a conference. \n\nTwo calls connected over a Dialog cannot be joined by additional participants and the overall connection flow will result in less events than when using other methods, such as `conference` or `connect`.\n\nAnother difference between Dialog and Connect/Conference APIs is that, unlike the latter, Dialog allows for early media propagation & media bypass. \n\nWhen creating a Dialog on an unanswered inbound call, the inbound call will be automatically answered once the destination party answers the call.\n",
"x-type":"submodule",
"x-displayName":"Dialog Calls"
},
{
"name":"dialog-management",
"description":"",
"x-type":"section",
"x-displayName":"Dialog Management"
},
{
"name":"dialog-operations",
"description":"",
"x-type":"section",
"x-displayName":"Dialog Operations"
},
{
"name":"sip-trunks",
"description":"Calls API allows your application to handle both inbound and outbound SIP calls. \n\nBefore your application can process an inbound SIP call or create an outbound one, you need to create at least one new SIP trunk with methods listed below.\n",
"x-type":"submodule",
"x-displayName":"SIP Trunks"
},
{
"name":"sip-trunk-management",
"description":"",
"x-type":"section",
"x-displayName":"SIP Trunk Management"
},
{
"name":"sip-trunk-status-management",
"description":"",
"x-type":"section",
"x-displayName":"SIP Trunk Status Management"
},
{
"name":"sip-trunk-service-address-management",
"description":"",
"x-type":"section",
"x-displayName":"SIP Trunk Service Address Management"
},
{
"name":"files-and-recordings",
"description":"Files operations allow the upload, list and delete audio files. These audio files can be played back in calls and conferences.\n\nRecordings methods allow to list, retrieve and delete audio and video recordings performed on calls and conferences.\n",
"x-type":"submodule",
"x-displayName":"Files And Recordings"
},
{
"name":"file-operations",
"description":"",
"x-type":"section",
"x-displayName":"File Operations"
},
{
"name":"recording-operations",
"description":"",
"x-type":"section",
"x-displayName":"Recording Operations"
},
{
"name":"media-stream",
"description":"Calls API allows your application to stream outbound call media to an arbitrary host. Before initiating the stream, you will need to create at least one new media-stream configuration. After creating the configuration, use the configuration ID within a call to start/stop streaming media. Media is streamed as a series of raw bytes. Currently only audio is supported.",
"x-type":"submodule",
"x-displayName":"Media streaming"
},
{
"name":"media-stream-configuration",
"description":"",
"x-type":"section",
"x-displayName":"Media stream configuration"
},
{
"name":"calls-applications",
"description":"Most actions performed on calls, conferences and dialogs using the Calls API will trigger one or several events to confirm the completion of the action’s execution, to update on call status or to raise an error. Events are sent to your exposed application webhooks using Subscriptions. \n\nFor more information about Calls application and subscriptions, read the following [documentation](https://www.infobip.com/docs/voice-and-video/calls#applications-concepts). Subscriptions can be managed via [API](https://www.infobip.com/docs/api/platform/subscriptions-api) or on the [Portal](https://portal.infobip.com/dev/subscriptions). The objective of this documentation is to list and document the content of all possible Calls API events you can configure via subscriptions.\n",
"x-type":"submodule",
"x-displayName":"Calls Events"
},
{
"name":"application-webhooks",
"description":"",
"x-type":"section",
"x-displayName":"Webhooks"
},
{
"name":"bulks",
"description":"The bulks API methods allow you to create multiple calls with a single request and managed the scheduled bulks. Calls that will be generated with the bulk methods support the same options as when creating singular calls, such as automated machine detection, recording and support of multiple endpoint types (phone, webRTC, SIP or Viber). Bulk calls do support additional parameters such as:\n\n* scheduling: when to start the call generation, and which are calling time windows for these calls to be generated\n* validity period: how long should Infobip try to generate these calls. This is a particularly interesting parameter to consider when defining calling time windows\n* call rate: the number of calls you should start during the specified time unit (such as 15 calls per minute or 60 calls per hour)\n\nMultiple bulks, each targeting multiple destinations with their own schedule and validity, can be bundled in a single request.\n\nBulks can be paused, resumed, canceled or rescheduled. Each new call within a bulk will result in the same stream of event status update as individually created calls (call_started, call_pre_established, call_ringing,…), giving your application full visibility and control about how each individual call needs to be handled.\n",
"x-type":"submodule",
"x-displayName":"Bulks"
},
{
"name":"bulk-call-management",
"description":"",
"x-type":"section",
"x-displayName":"Bulk Calls Management"
},
{
"name":"bulk-call-operations",
"description":"",
"x-type":"section",
"x-displayName":"Bulk Calls Operations"
},
{
"name":"calls-markup-language",
"description":"Calls Markup Language (CML) is a simple JSON-based language that enables you to define the flow of your voice application in a human readable format.",
"x-type":"module",
"x-displayName":"Calls Markup Language"
},
{
"name":"calls-markup-language-create",
"description":"",
"x-type":"section",
"x-displayName":"Calls Markup Language"
},
{
"name":"markup-language-instructions",
"description":"",
"x-type":"section",
"x-displayName":"Calls Markup Language Webhook"
},
{
"name":"markup-language-instructions-async",
"description":"",
"x-type":"section",
"x-displayName":"Calls Markup Language Webhook Async"
},
{
"name":"calls-markup-language-configuration",
"description":"",
"x-type":"section",
"x-displayName":"Calls Markup Language Configuration"
},
{
"name":"voice-message",
"description":"The Voice Message API initiate outbound calls to one or more destination numbers (landline or mobile). When the call has been answered, pre-recorded or text-to-speech converted audio file will be played to the recipient. Three flavors of voice messaging are available:\n\n* Single voice message: call one target number at a time, and play an audio file or text to speech\n* Multiple voice message: same as simple, but allows to define an array of messages, each with their own multiple target numbers\n* Advanced voice message: same as multiple, but\n * Can use Automated Machine Detection\n * Can define schedule for sending calls\n * Can define acceptable time windows for sending\n * Can capture 1 DTMF input from the callee(s), and report it via webhook, or or use DTMF input to forward the call to defined destination\n",
"x-type":"module",
"x-displayName":"Voice Message"
},
{
"name":"voice-message-sending-operations",
"description":"",
"x-type":"section",
"x-displayName":"Voice Message Sending Operations"
},
{
"name":"voice-message-scheduling-operations",
"description":"",
"x-type":"section",
"x-displayName":"Voice Message Scheduling Operations"
},
{
"name":"interactive-voice-response",
"description":"The IVR API enables the creation of inbound and outbound interactive call scenarios. For inbound calls, once your scenario is created you will need to link this scenario to the phone number you are renting on the Infobip platform using the [voice setup on number](#platform-connectivity/numbers/create-voice-setup-on-number) method.\n\nIVR scenarios can use the Record action to record a portion of the call. These recordings can be retrieved using the *Search Voice IVR Recorded Files* and *Download Voice IVR Recorded File*. Alternatively, IVR recorded audio can also be found using the [Search Recording](#channels/voice/search-recordings) method.\n",
"x-type":"module",
"x-displayName":"Interactive Voice Response"
},
{
"name":"manage-ivr-scenarios",
"description":"",
"x-type":"section",
"x-displayName":"Manage IVR Scenarios"
},
{
"name":"retrieve-recorded-files",
"description":"",
"x-type":"section",
"x-displayName":"Retrieve Recorded Files"
},
{
"name":"ivr-uploaded-files",
"description":"",
"x-type":"section",
"x-displayName":"Manage uploaded files"
},
{
"name":"click-to-call",
"description":"Click To Call",
"x-type":"module",
"x-displayName":"Click To Call"
},
{
"name":"voice-reports-and-logs",
# --- truncated at 32 KB (9710 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/infobip/refs/heads/main/openapi/infobip-platform-full-openapi.json