Registry /
communication / infobip-api-python-client
Install & Compatibility
Where this runs
tested against v6.0.0 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
65MB installed
● package 65MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
ApiClient
✓ from infobip_api_client import ApiClient
✗ from infobip_api_client.api_client import ApiClient
Configuration
✓ from infobip_api_client import Configuration
✗ from infobip_api_client.api_client import Configuration
SmsApi
✓ from infobip_api_client import SmsApi
✗ from infobip_api_client.api.sms_api import SmsApi
Send SMS via Infobip. Account-specific base URL is mandatory.
from infobip_api_client.api.sms_api import SmsApi
from infobip_api_client.api_client import ApiClient, Configuration
from infobip_api_client.models import (
SmsAdvancedTextualRequest,
SmsDestination,
SmsTextualMessage
)
# Get base_url from: app.infobip.com → API Keys
configuration = Configuration(
host='https://XXXXX.api.infobip.com',
api_key={'APIKeyHeader': 'App YOUR_API_KEY'}
)
with ApiClient(configuration) as api_client:
sms_api = SmsApi(api_client)
request = SmsAdvancedTextualRequest(
messages=[
SmsTextualMessage(
destinations=[SmsDestination(to='+14155551234')],
from_='InfoSMS',
text='Hello from Infobip!'
)
]
)
response = sms_api.send_sms_message(
sms_advanced_textual_request=request
)
print(response.messages[0].message_id)
Debug
Known issues
breakingEvery major version of infobip-api-python-client contains breaking changes. The library is auto-generated from OpenAPI spec — model names, method signatures, and endpoint paths change between versions. Code written for v3 will not work on v5 or v6.fixPin the version in requirements.txt. Read the CHANGELOG before upgrading: https://github.com/infobip/infobip-api-python-client/releases
affects: all major versions
breakingAccount-specific base URL is required. Using a generic URL like https://api.infobip.com causes authentication failures. Each Infobip account has a unique subdomain assigned at account creation.fixFind your base URL at app.infobip.com under API Keys or the API Resource Hub. Format: https://XXXXX.api.infobip.com
affects: all
breakingSMS API endpoint changed: /sms/3/messages (V3) replaced /sms/2/text/advanced (V2) in v5.x. Email API /email/4/messages (V4) replaced /email/3/send (V3). Old endpoint paths and corresponding SDK methods are removed.fixUpdate to the v3 SMS methods (send_sms_message) and v4 email methods. Check the CHANGELOG for exact method name changes.
affects: >= 5.0
breakingPython 3.8 support dropped in v6.0. Minimum is now Python 3.9.fixPin infobip-api-python-client<6.0 for Python 3.8 environments.
affects: >= 6.0
breakingHTTPS enforcement added in v6.0. Passing http:// as the host URL now raises ValueError at configuration time.fixAlways use https:// in the host URL. Remove any http:// base URLs from configuration.
affects: >= 6.0
gotchaTwo separate packages exist: infobip-api-python-client (official, auto-generated, breaking changes each major) and infobip-api-python-sdk (community, different API style, last updated 2023). They have different import patterns and are not interchangeable.fixUse infobip-api-python-client for the latest official API coverage. The community SDK (infobip-api-python-sdk) is unmaintained and missing recent endpoints.
affects: all
breakinginfobip-api-python-client v6.0.0+ requires Pydantic v2.x. An 'ImportError: cannot import name 'validate_call' from 'pydantic'' will occur if Pydantic v1.x is present in the environment.fixEnsure Pydantic v2.x (e.g., 'pydantic>=2') is installed. If Pydantic v1.x is present, it must be uninstalled first (e.g., 'pip uninstall pydantic' then 'pip install pydantic>=2') to resolve the conflict. Using a clean virtual environment is recommended.
affects: >= 6.0
breakingSome transitive dependencies of infobip-api-python-client (e.g., 'regex') require system build tools like 'gcc' to compile C extensions during installation. This commonly occurs in minimal environments like Alpine Linux, leading to a build failure.fixEnsure that your environment includes the necessary build tools. For Alpine Linux, install 'build-base' (e.g., 'apk add build-base'). For Debian/Ubuntu, install 'build-essential' (e.g., 'apt-get install build-essential').
affects: all
Upgrade
Version history
6.0.0latest on PyPI · released Jan 22, 2026
Audit
Dependencies
urllib3requiredRequired. Installed automatically.
python-dateutilrequiredRequired. Installed automatically.
pydanticrequiredRequired. Installed automatically.