Azmarq Python SDK
Official Python client for the Azmarq API. Python 3.9 or newer. No third-party dependencies.
pip install azmarqomni
The install name is azmarqomni. The import is still azmarq:
Create an API key in the Azmarq console under Developer → API Key, then:
import os
from azmarq import Azmarq
client = Azmarq(api_key=os.environ["AZMARQ_API_KEY"])
response = client.send(
channel="sms",
from_="SENDER",
to="9800000001", # +91, 91, or 10-digit local
text="Hello from Azmarq",
)
print(response["messageId"])
The same send(channel=...) works for WhatsApp and RCS. Channel-specific helpers (client.sms, client.whatsapp, client.rcs) are still there.
Azmarq() with no arguments reads AZMARQ_API_KEY.
type is TRANS, PROMO, or OTP. Set unicode=1 for non-GSM text and flash=1 for a flash SMS. Pass several numbers as a list; they are sent as a comma-separated MSISDN list.
client.sms.send_template(
sender="AOCAPI",
to="919800000001",
template_id="1507165650000000000",
custom=["Ada", "ORD-1001"],
)
started = client.verify.generate(config_id="your-config-id", to="919800000001")
client.verify.validate(verify_id=started["data"], otp="123456")
client.whatsapp.send_template(
from_="+919800000000",
to="+919800000001",
template_name="order_update",
components={"body": {"params": ["Ada", "ORD-1001"]}},
)
client.rcs.send(
number="+919800000001",
template_name="plane_text",
bot_id="YOUR_BOT_ID",
type="TRANS",
)
Failures raise AuthenticationError, InvalidRequestError, APIError, or ConnectionError, all subclasses of AzmarqError.
For a payload the helpers do not model (carousel, catalog, flow), post the documented JSON yourself:
client.whatsapp.send({
"from": "+919800000000",
"to": "+919800000001",
"type": "template",
"templateName": "carousel_template",
"components": {},
})
Full reference: https://developers.azmarq.com
Metadata
Release files for azmarqomni 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| azmarqomni-0.2.0.tar.gz | 14.2 kB | Without provenance | Details for azmarqomni-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| azmarqomni-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for azmarqomni-0.2.0-py3-none-any.whl |
Total release size: 30.2 kB
Release files / azmarqomni-0.2.0.tar.gz
| Download URL | azmarqomni-0.2.0.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ed285a5c1e0c7699343710e4b214210f0a90923462bec9552df6087e3142f56
|
|
BLAKE2b-256 checksum How to use checksums |
ce258cc1faee116566b03e79dce3e4e7e2e2817420270d431e7866aae2f6d339
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.4
|
Release files / azmarqomni-0.2.0-py3-none-any.whl
| Download URL | azmarqomni-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e00f94d97ab12f74d815adb1d7b42997dd6a8ac3e6d8ae9f6125fcd8e3e6580
|
|
BLAKE2b-256 checksum How to use checksums |
bbc35d0d17cbc793ef1dedd59203f0b7798d5275752a48b48b1e7be92abbc3d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.4
|
Security for azmarqomni 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.