WordPress Dinstar SMS Integration System
Budget: $250 – $750 USD
I already run a WordPress site where municipalities log in to draft their text alerts. Now I need the back-end engine that will actually move those messages from WordPress through playSMS and out via a Dinstar GSM gateway.
The core of the job is the integration with Dinstar and playSMS. You will expose a clean REST API (Python with Flask or FastAPI on Linux) that my WordPress plugin can call, pass the message payload to playSMS, and relay it to the gateway. From the same API I also want delivery reports and status updates pushed back to WordPress, preferably through webhooks so the site can show live progress bars for each campaign.
Day-to-day workflow I envision
• Municipal clerk logs in on WordPress and writes a message.
• Message is queued for my approval, scheduled, and pushed to playSMS only after I green-light it.
• Once sent, delivery logs and status for every number become visible in the WordPress dashboard.
Group management is equally important. Incoming texts containing predefined keywords must automatically slot the sender’s number into the correct town, street, or custom list so future alerts reach the right people without manual effort.
Deliverables
1. Python/Flask (or FastAPI) service that:
– Authenticates WordPress requests, queues messages, calls playSMS, and hands off to the Dinstar gateway.
– Receives DLRs and writes them back to WordPress via webhook or REST endpoint.
2. WordPress plugin or hooks covering:
– Message compose screen, schedule picker, and admin approval flow.
– Real-time status and searchable logs.
3. Group engine that parses inbound SMS, matches keywords, and updates recipient lists.
4. Basic admin panel (web UI is fine) for message queues, groups, and system health.
5. Documentation covering setup, API endpoints, and how to add new keywords or towns.
If you have prior hands-on experience with playSMS, Dinstar, or any GSM gateway, let me know—those projects will speak louder than a résumé.
The core of the job is the integration with Dinstar and playSMS. You will expose a clean REST API (Python with Flask or FastAPI on Linux) that my WordPress plugin can call, pass the message payload to playSMS, and relay it to the gateway. From the same API I also want delivery reports and status updates pushed back to WordPress, preferably through webhooks so the site can show live progress bars for each campaign.
Day-to-day workflow I envision
• Municipal clerk logs in on WordPress and writes a message.
• Message is queued for my approval, scheduled, and pushed to playSMS only after I green-light it.
• Once sent, delivery logs and status for every number become visible in the WordPress dashboard.
Group management is equally important. Incoming texts containing predefined keywords must automatically slot the sender’s number into the correct town, street, or custom list so future alerts reach the right people without manual effort.
Deliverables
1. Python/Flask (or FastAPI) service that:
– Authenticates WordPress requests, queues messages, calls playSMS, and hands off to the Dinstar gateway.
– Receives DLRs and writes them back to WordPress via webhook or REST endpoint.
2. WordPress plugin or hooks covering:
– Message compose screen, schedule picker, and admin approval flow.
– Real-time status and searchable logs.
3. Group engine that parses inbound SMS, matches keywords, and updates recipient lists.
4. Basic admin panel (web UI is fine) for message queues, groups, and system health.
5. Documentation covering setup, API endpoints, and how to add new keywords or towns.
If you have prior hands-on experience with playSMS, Dinstar, or any GSM gateway, let me know—those projects will speak louder than a résumé.