Get Started with Infobip API

View the Infobip OpenAPI specification or learn more about our OpenAPI to get the specification that fits your needs.

Free trial

Infobip APIs are free to explore, but to use them, you will need an Infobip account. When you sign up, you automatically begin a free trial, allowing you to test our services and explore all available features. You will also get access to your API key and Base URL, which are required to start using Infobip APIs.

For detailed instructions on how to make the most of your free trial, visit our free trial guide

Base URL

Your Infobip account comes with a unique Base URL that must be included in every API request. This URL ensures that your requests are routed correctly.

You can find your Base URL at the top of this page when logged into your Infobip account. It will also be pre-filled in the API endpoint examples throughout the documentation.

Example Base URL (Do not use it in your code)

Base URL: example.infobip.comBase URL used in the Send SMS message endpoint: https://example.infobip.com/sms/3/messages

Note

The Base URL is not a secret. While someone else using your base URL won't harm your account, using an incorrect base URL can result in service degradation or failure.

Learn more about Base URLs

Authentication

Infobip supports several authentication methods, with the API key being the recommended approach for most use cases.

When you sign up for an Infobip account, you will receive an API key. You can view and copy it for 2 days on the Infobip web interface homepage, so be sure to store it securely. If needed, you can always create a new one on the API keys page

To authenticate your requests, include this API key in the Authorization header of your API calls.

API key authentication header example

Authorization: App 003026bbc133714df1834b8638bb496e-8f4b3c9a-e931-478d-a994-28a725159ab9

Authorization with API scopes

API scopes provide an additional layer of security and control, defining which API calls you are allowed to make. When you create an Infobip account, you receive an API key that has all the necessary scopes for you to start making API requests immediately.

Scopes necessary for using an endpoint are listed on the endpoint-level of Infobip API documentation.

For more control, you can create API keys and assign specific scopes over API or the web interface. Learn more about managing API scopes

If you are using basic authentication, scopes can also be assigned to users based on their roles. Learn more about user roles and API scopes

Error and response status codes

When using our API, you'll encounter HTTP and API status codes, as well as error codes:

HTTP status codes (e.g., 200 OK, 404 Not Found) are standard for every HTTP request.
API status codes (e.g. PENDING_ACCEPTED) provide more details on the status of your API request and can be found in the response of sent messages, delivery reports, or message logs.
Error codes (e.g. NO_ERROR) can be returned as part of the message response or a delivery report. They provide additional information about issues with your requests (e.g., invalid parameters or internal errors).

Troubleshooting

For a complete list of all API status codes and error codes, along with the troubleshooting steps, visit the Response status and error codes documentation

Rate limits and throttling

Our message sending APIs have no upper limit, and we can handle traffic peaks from the world's largest enterprises. However, bottlenecks can occur due to limitations of certain external channel providers (e.g., telecom networks) that sit between Infobip and message recipients. Check the product's channel documentation for more details

For non-message sending APIs, requests are throttled if usage exceeds expected levels. If this happens, you'll receive an HTTP status code 429 - Too Many Requests. This usually means that the API endpoint is being used in a way that was not designed to be used. In these situations, we recommend to explore other endpoints which may be more suitable for your use case, or to contact us

SDKs and client libraries

Infobip provides official API client libraries and SDKs in multiple programming languages. View the full list on our SDKs page

We follow Semantic Versioning (2.0.0), ensuring minor updates are backward-compatible. Major releases may introduce breaking changes, so make sure to always review the changelog before upgrading.

All SDKs are open-source on GitHub, built using the OpenAPI specification. While we don't accept pull requests, we encourage issue reporting.

Code examples

Each API endpoint includes use case-based code examples (e.g., sending a scheduled SMS, sending an SMS in a specific language).

Examples are available in:

Multiple programming languages
cURL commands
JSON/XML request payloads

They are auto-generated from the OpenAPI specification using Postman and can be copied directly into your project.

Webhooks

Webhooks let you receive real-time notifications about events like message delivery statuses or incoming messages. Instead of polling our servers, you can configure a webhook endpoint to receive updates via HTTP POST requests in JSON format.

Configure webhooks using the Subscription Management API

Best practices

We focus on consistency to ensure a smooth developer experience. For example, code examples in our documentation are not URL encoded for readability. If your system or programming language requires URL encoding for query parameters, you'll need to encode them yourself. Most libraries and programming languages handle this automatically.

For more tips on avoiding common issues, supported date formats, request/response body types, and other best practices, refer to our Integration best practices