generated: '2026-07-25' method: derived source: openapi/infobip-2fa-openapi.json, openapi/infobip-account-management-openapi.json, openapi/infobip-ai-assistants-openapi.json, openapi/infobip-answers-openapi.json, openapi/infobip-apple-mfb-openapi.json, openapi/infobip-application-entity-openapi.json, openapi/infobip-billing-usage-api-openapi.json, openapi/infobip-biometrics-openapi.json, openapi/infobip-blocklist-openapi.json, openapi/infobip-camara-openapi.json, openapi/infobip-catalogs-api-openapi.json, openapi/infobip-common-assets-openapi.json ... summary: types: - apiKey - http - oauth2 api_key_in: - header oauth2_flows: - clientCredentials schemes: - name: APIKeyHeader type: apiKey in: header parameter: Authorization description: |- This is the most secure authorization type and the one with the most flexibility. API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases sources: - openapi/infobip-2fa-openapi.json - openapi/infobip-account-management-openapi.json - openapi/infobip-ai-assistants-openapi.json - openapi/infobip-answers-openapi.json - openapi/infobip-apple-mfb-openapi.json - openapi/infobip-application-entity-openapi.json - openapi/infobip-billing-usage-api-openapi.json - openapi/infobip-biometrics-openapi.json - openapi/infobip-blocklist-openapi.json - openapi/infobip-camara-openapi.json - openapi/infobip-catalogs-api-openapi.json - openapi/infobip-common-assets-openapi.json - openapi/infobip-conversations-openapi.json - openapi/infobip-email-openapi.json - openapi/infobip-instagram-openapi.json - openapi/infobip-kakao-openapi.json - openapi/infobip-knowledge-base-openapi.json - openapi/infobip-line-openapi.json - openapi/infobip-live-chat-openapi.json - openapi/infobip-messages-api-openapi.json - openapi/infobip-messenger-openapi.json - openapi/infobip-metrics-api-openapi.json - openapi/infobip-mms-openapi.json - openapi/infobip-mobile-app-messaging-openapi.json - openapi/infobip-mobile-identity-openapi.json - openapi/infobip-moments-openapi.json - openapi/infobip-number-activation-state-openapi.json - openapi/infobip-number-lookup-openapi.json - openapi/infobip-numbers-openapi.json - openapi/infobip-omni-failover-openapi.json - openapi/infobip-open-channel-openapi.json - openapi/infobip-openapi-openapi.json - openapi/infobip-people-openapi.json - openapi/infobip-platform-full-openapi.json - openapi/infobip-rcs-openapi.json - openapi/infobip-resources-openapi.json - openapi/infobip-sending-strategy-openapi.json - openapi/infobip-signals-openapi.json - openapi/infobip-sms-openapi.json - openapi/infobip-subscriptions-api-openapi.json - openapi/infobip-tiktok-openapi.json - openapi/infobip-viber-openapi.json - openapi/infobip-vocalize-openapi.json - openapi/infobip-voice-openapi.json - openapi/infobip-webrtc-calls-openapi.json - openapi/infobip-whatsapp-openapi.json - openapi/infobip-zalo-openapi.json - name: Basic type: http scheme: basic description: "Basic authorization type can be used in situations when the API key is not available.\ \ For example, API methods for generating API keys should be authenticated\nwith the Basic\ \ type.\n\nIn this case, the credentials included in the Authorization header should be\ \ a Base64 encoded username and password combination. More formally, basic\nauthentication\ \ header can be constructed in three steps:\n\n* Username " sources: - openapi/infobip-2fa-openapi.json - openapi/infobip-account-management-openapi.json - openapi/infobip-ai-assistants-openapi.json - openapi/infobip-answers-openapi.json - openapi/infobip-apple-mfb-openapi.json - openapi/infobip-application-entity-openapi.json - openapi/infobip-billing-usage-api-openapi.json - openapi/infobip-biometrics-openapi.json - openapi/infobip-blocklist-openapi.json - openapi/infobip-camara-openapi.json - openapi/infobip-catalogs-api-openapi.json - openapi/infobip-common-assets-openapi.json - openapi/infobip-conversations-openapi.json - openapi/infobip-email-openapi.json - openapi/infobip-instagram-openapi.json - openapi/infobip-kakao-openapi.json - openapi/infobip-knowledge-base-openapi.json - openapi/infobip-line-openapi.json - openapi/infobip-live-chat-openapi.json - openapi/infobip-messages-api-openapi.json - openapi/infobip-messenger-openapi.json - openapi/infobip-metrics-api-openapi.json - openapi/infobip-mms-openapi.json - openapi/infobip-mobile-app-messaging-openapi.json - openapi/infobip-mobile-identity-openapi.json - openapi/infobip-moments-openapi.json - openapi/infobip-number-activation-state-openapi.json - openapi/infobip-number-lookup-openapi.json - openapi/infobip-numbers-openapi.json - openapi/infobip-omni-failover-openapi.json - openapi/infobip-open-channel-openapi.json - openapi/infobip-openapi-openapi.json - openapi/infobip-people-openapi.json - openapi/infobip-platform-full-openapi.json - openapi/infobip-rcs-openapi.json - openapi/infobip-resources-openapi.json - openapi/infobip-sending-strategy-openapi.json - openapi/infobip-signals-openapi.json - openapi/infobip-sms-openapi.json - openapi/infobip-subscriptions-api-openapi.json - openapi/infobip-tiktok-openapi.json - openapi/infobip-viber-openapi.json - openapi/infobip-vocalize-openapi.json - openapi/infobip-voice-openapi.json - openapi/infobip-webrtc-calls-openapi.json - openapi/infobip-whatsapp-openapi.json - openapi/infobip-zalo-openapi.json - name: OAuth2 type: oauth2 flows: - flow: clientCredentials tokenUrl: https://api.infobip.com/auth/1/oauth2/token scopes: 0 description: |- Similarly to the IBSSO Token authentication you can use OAuth 2.0 bearer token with Infobip serving both as resource and authorization server. You can obtain the access token using the client credentials grant from `auth/1/oauth2/token` endpoint. It will provide you with your access token, and its expiration period. You can use the token to authorize your API calls until it expires. You can find o sources: - openapi/infobip-2fa-openapi.json - openapi/infobip-account-management-openapi.json - openapi/infobip-ai-assistants-openapi.json - openapi/infobip-answers-openapi.json - openapi/infobip-apple-mfb-openapi.json - openapi/infobip-application-entity-openapi.json - openapi/infobip-billing-usage-api-openapi.json - openapi/infobip-biometrics-openapi.json - openapi/infobip-blocklist-openapi.json - openapi/infobip-camara-openapi.json - openapi/infobip-catalogs-api-openapi.json - openapi/infobip-common-assets-openapi.json - openapi/infobip-conversations-openapi.json - openapi/infobip-email-openapi.json - openapi/infobip-instagram-openapi.json - openapi/infobip-kakao-openapi.json - openapi/infobip-knowledge-base-openapi.json - openapi/infobip-line-openapi.json - openapi/infobip-live-chat-openapi.json - openapi/infobip-messages-api-openapi.json - openapi/infobip-messenger-openapi.json - openapi/infobip-metrics-api-openapi.json - openapi/infobip-mms-openapi.json - openapi/infobip-mobile-app-messaging-openapi.json - openapi/infobip-mobile-identity-openapi.json - openapi/infobip-moments-openapi.json - openapi/infobip-number-activation-state-openapi.json - openapi/infobip-number-lookup-openapi.json - openapi/infobip-numbers-openapi.json - openapi/infobip-omni-failover-openapi.json - openapi/infobip-open-channel-openapi.json - openapi/infobip-openapi-openapi.json - openapi/infobip-people-openapi.json - openapi/infobip-platform-full-openapi.json - openapi/infobip-rcs-openapi.json - openapi/infobip-resources-openapi.json - openapi/infobip-sending-strategy-openapi.json - openapi/infobip-signals-openapi.json - openapi/infobip-sms-openapi.json - openapi/infobip-subscriptions-api-openapi.json - openapi/infobip-tiktok-openapi.json - openapi/infobip-viber-openapi.json - openapi/infobip-vocalize-openapi.json - openapi/infobip-voice-openapi.json - openapi/infobip-webrtc-calls-openapi.json - openapi/infobip-whatsapp-openapi.json - openapi/infobip-zalo-openapi.json