mirror of
https://github.com/NdoleStudio/httpsms.git
synced 2026-04-26 19:35:50 +03:00
[GH-ISSUE #104] Support bulk sending SMS #13
Labels
No labels
In Review
documentation
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/httpsms#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @baoc75 on GitHub (Feb 15, 2023).
Original GitHub issue: https://github.com/NdoleStudio/httpsms/issues/104
Allow users to send multiple messages to multiple phone numbers with a delay between each message.
@AchoArnold commented on GitHub (Feb 20, 2023):
Hello @baoc75
Could you elaborate more on your use case? Which type of delay should we set should it be configurable? Currently, if you send multiple messages with the API the messages will be spread out based on the configured messages/second throughput.
e.g Currently, If you send 100 messages in parallel and you have the configuration of 2 SMS / minute, the application will actually send 1 SMS every 30 seconds using the phone.
Does this solve the issue for you?
@baoc75 commented on GitHub (Feb 20, 2023):
Hi @AchoArnold, as the documentation don't have an endpoint where I can pass multiple phone numbers. So if I want to send to 100 numbers, I would have to initiate 100 requests. Please correct me if I am wrong.
Regarding the rate limit, thanks for your clarification, I can limit the number of messages right now.
By the way, the software is easy to use 😁
@AchoArnold commented on GitHub (Feb 20, 2023):
Yes you'll have to send 100 requests. I think even if we do multiple phone numbers via API, we still need to split the bulk messages to 100 individual messages before it is sent on the phone.
We can create an additional code to do this at the API level but at the mean time you can also do it on your end.
Out of curiosity, is there a specific issue with sending 100 requests instead of 1 request with 100 phone numbers?
@AchoArnold commented on GitHub (Mar 4, 2023):
Hello @baoc75 I implemented a bulk send API, check it out and tell me what you think https://api.httpsms.com/index.html#/Messages/post_messages_bulk_send
@baoc75 commented on GitHub (Mar 4, 2023):
Hello, @AchoArnold. I read your documents. It's exactly what I'm looking for.
About your question, my goal is to make as few HTTP requests as possible. Sending more HTTP requests consumes more bandwidth and resources, and increases the chance of failure.