API authentication
All API requests need to be authenticated through the Authorization header. The Infobip API offers the following authentication methods:
- HTTP Basic authentication
- API keys
- IBSSO tokens
- OAuth 2.0
Select your preferred method to suit your current tech stack and security requirement level. Many of these methods are vulnerable to man-in-the-middle attacks, so it is recommended to combine them with other security mechanisms such as an encrypted connection or SSL.
Refer to the Errors section to troubleshoot potential issues, or alternatively reach out to the Infobip Support team for help.
Basic
Basic authentication works by sending a username and password in every API request. Typically, this method is used in situations when the API key is not available. For example, API methods generating API keys could be authenticated with Basic.
Basic Auth is the least recommended method as it is still simple to decode encrypted credentials back to their original values. Refer to the HTTP Authentication resource to see how to restrict access to your server with Basic authentication.
Here are some key facts about this method:
- Built into HTTP protocol itself
- Credentials should be encoded in a Base64 format (for example, with the RFC2045-MIME variant) and separated by a colon (:)
- Encoded credentials are added to the header after
Basic
Example - HTTP client
When using any of the Infobip API client libraries you don't have to manually encode the credentials. You only need to specify the username and password when creating an instance of a client object.
Example - API client library
When using any of the Infobip API client libraries you do not have to manually encode the credentials data like mentioned above. You only need to specify the username and password when creating an instance of a client object as shown in the example below.
API scopes on Basic Auth [#api-scopes-on-basic-auth-basic]
For information on API scopes associated with Basic Auth, refer to the dedicated User roles and API scopes section.
API key header
An API key is an access token that a client provides when making API calls. It is a simple way to secure access and thus the most popular authentication method used with REST APIs.The key can be sent in the query string or as a request header. You are automatically assigned an API Key once you create an account. Generate more keys and manage the existing ones through the Infobip API key management page.
Here are some key facts about this method:
- API keys can be generated by calling the dedicated API method
- Keys can be revoked at any time which is useful when separating the API access rights across multiple applications or use cases
- Infobip API keys have a predefined expiry date to eventually become invalid
Example - HTTP client
The examples below show how to specify the API Key authentication when using client libraries.
Example - API client library
The examples below show how to prepare an HTTP request using API Key authentication. Note this request is much simpler than using a basic authentication request.
API scopes on API keys [#api-scopes-on-api-keys-api-key-header]
For details on API scopes, see the dedicated API scopes section.
IBSSO token header
IBSSO tokens are session-based meaning tokens are valid for a short amount of time. That ultimately makes this method more secure, but also requires more maintenance to keep authentication valid.
Typically, this kind of authentication is used in single sign-on scenarios where multiple sign-ins which to be avoided across the system. It may be also useful in scenarios when sensitive data needs to be handled centrally without the need to distribute it across various enterprise systems.
Here are some key facts about this method:
- All API requests are authenticated with a session token
- By default, IBSSO tokens will expire after 60 minutes after which a new token must be created
- If you want to create a new token but the previous one has not expired yet, you will first need to destroy the session
- You can shorten the session's length with a dedicated API call
How to use IBSSO tokens [#how-to-use-ibsso-tokens-ibsso-token-header]
- Make a call to create a session endpoint and take the token from the response.
- Include
IBSSOand the token in the Authorization header for all subsequent calls:Authorization: IBSSO 2f9b4d31-2d0d-49a8-85f0-9b862bdca394 - Optionally, destroy the session to adjust the session's length to your needs. By default, the session will expire after 60 minutes.
HTTP request [#http-request-ibsso-token-header]
Obtain IBSSO token [#obtain-ibsso-token-ibsso-token-header]
Create a session by calling the Create session endpoint. The response will contain the token which can then be used in the HTTP header of the requests to other API endpoints such as Send SMS.
Example - HTTP client
The examples below show how to prepare the HTTP request. Note that this is almost identical to API Key authentication, but instead of App, you will use IBBSOin the header.
Example - API library
When using any of the Infobip API client libraries, you will need the same elements that you would for the API Key authentication, but instead of App, you will use IBBSO.
OAuth 2.0
This type of authentication is the most secure option and is almost industry standard. Similar to using IBSSO tokens, you will use an access token you get from separate endpoint.
Here are some key facts about this method:
- The access token returned in response will expire within the time limit provided in seconds in the same response.
- Infobip acts as both a resource and an authorization server.
- A new token has to be created once the token expires. There is no automatic token retrieval.
For more details, see the official OAuth 2.0 specification.
How to use OAuth 2.0 [#how-to-use-oauth-20-oauth-20]
- Make a call to get the access token and the expiration time from a separate endpoint.
- Include
Bearerand the token in the Authorization header for all subsequent calls until the token expires.Authorization: Bearer eyJraWQiOiI5d29rWGRoSSIsInR5cCI6IkpXVCIsImFsZyI6IkhTMjU2In0.eyJzdWIiOiJERDIwMjAiLCJpc3MiOiJpbmZvYmlwLmNvbSIsImV4cCI6MTYzMzAwNDQwNiwiaWF0IjoxNjMzMDAwODA2LCJqdGkiOiJiMmJmODgyMS01OTcxLTRiOTMtYWVmNy0zM2QwMDNkMjIxNjcifQ.KvIIOmCKJETiB6xKOqBxvZYnYOa8RAulYhChBEmI4Os
HTTP request [#http-request-oauth-20]
Obtain OAuth token [#obtain-oauth-token-oauth-20]
Similarly to IBSSO tokens, you have to first obtain a token before making any API calls.
Example - HTTP client
The examples below show how to prepare an HTTP client request with a header.
Example - API library
The examples below show how to prepare an HTTP request with headers.
Errors
Commonly you will get the 401 Unauthorised HTTP status code in response when there is a missing or invalid username or password.
Library exceptions [#library-exceptions-errors]
When using one of the libraries, make sure to handle API exceptions.