Communication/messaging
winsms.co.za
WINSMS sandbox and mock API
WinSMS RESTful API Writes persist, data moves on a schedule and every change can fire a signed webhook.
- Operations
- 11
- Collections
- -
- Event types
- -
example request
curl https://your-winsms-za.slurry.io/api/rest/v1/credits/balance \
-H "Authorization: Bearer slurry_sim_..."Your simulation gets its own hostname, key and IP allow-list. Built from API version 1.0.0.
What gets simulated
Collections, relationships and state machines are worked out from the spec when you start the simulation.
- State. Creates, updates and deletes persist and show up in later reads.
- Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
- Webhooks. Every change emits a signed, retried event.
- Failure. Per-endpoint errors, latency and chaos rules, on demand.
Operations
All 11.
- GET/credits/balance
- POST/credits/transfer
- GET/shortcode/incoming
- GET/sms/incoming
- GET/sms/incoming/optout
- POST/sms/outgoing/send
- POST/sms/outgoing/sendmulti
- POST/sms/outgoing/status
- GET/sms/scheduled
- POST/sms/scheduled/delete
- GET/subaccounts