Send multiple different SMS messages in WINSMS
A documented WINSMS operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Send multiple different SMS messages
- POSTChanges data · sms
www.winsms.co.za/sms/outgoing/sendmulti
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which WINSMS operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other WINSMS operations
- Send SMS messagesPOST · changes data
- Delete scheduled SMS messages and refund creditsPOST · changes data
- Transfer credits between main and sub accountsPOST · changes data
- Get SMS delivery statusesPOST · changes data
- Get a list of incoming SMS messagesGET · reads data
- Get a list of scheduled SMS messagesGET · reads data
- Get a list of incoming short/long code messagesGET · reads data
- Get a list of incoming opt-out SMS messagesGET · reads data
Questions
- Can HumDay send multiple different sms messages in WINSMS?
- Yes. This operation is published in WINSMS's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my WINSMS data?
- Yes — this is a POST operation, so it changes something in WINSMS. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your WINSMS account.
Where this came from
Read from a published API description for WINSMS at www.winsms.co.za/api/restdocs/swagger.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.