No SDK. No dashboard. Just HTTP.
This is not a wrapper. These are direct API execution flows.
Most SMS APIs hide routing, pricing and delivery behind abstractions.
This repository does not.
It exposes the full execution surface using direct API requests.
What this is
A collection of Python scripts that interact directly with messaging infrastructure.
Each script solves a real backend task:
- send a message
- estimate cost before sending
- inspect routes and pricing
- compare multiple routes
- track delivery via
bx_message_id - send messages from CSV data
Clone and run
git clone https://github.com/bridgexapi-dev/bridgexapi-direct-api-python-examples
cd bridgexapi-direct-api-python-examples
pip install -r requirements.txt
copy .env.example .env
Run a simple send:
python send-one-message/send_one.py
Examples included
Send a message
python send-one-message/send_one.py
Estimate cost before sending
python estimate-before-send/estimate.py
Inspect routes and pricing
python route-pricing/routes.py
Compare routes
python route-comparison/compare_routes.py
Track delivery status
python delivery-lookup/get_dlr.py
Send from CSV
python send-from-csv/send_from_csv.py
What this exposes
- explicit route selection (
route_id) - pricing before submission
- delivery tracking per message
- real response structures
- no abstraction layer
Why this matters
Most messaging APIs:
- hide routing decisions
- hide pricing logic
- hide delivery behavior
This approach keeps everything visible and controllable from your backend.
Run it.
Check your phone.
See what actually lands.
GitHub:
https://github.com/bridgexapi-dev/bridgexapi-direct-api-python-examples
Top comments (0)