You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would make carriers happier and would reduce spam to other carriers. We can incentivize this by raising limits for people who specify their carrier.
In addition to the number and message parameters, the /text endpoint should accept a carrier parameter such as "verizon", "tmobile", or "att" that will route to the correct email instead of sending an email to all carriers.
The text was updated successfully, but these errors were encountered:
FYI, I would think as part of this enhancement, it would be nice to have an additional (formal?) API endpoint to specify the list of available (or "supported") carriers to which to send SMS (by email) to.
As it is today, a user has to be aware of the current carrier support by reading the docs on the TextBelt site/readme, or looking at the source code where the carrier gateways are specified. That's fine when user doesn't need to specify carrier, but when they do, having a way to know on demand (by API) which carriers are supported is nice.
This would make carriers happier and would reduce spam to other carriers. We can incentivize this by raising limits for people who specify their carrier.
In addition to the
number
andmessage
parameters, the/text
endpoint should accept acarrier
parameter such as "verizon", "tmobile", or "att" that will route to the correct email instead of sending an email to all carriers.The text was updated successfully, but these errors were encountered: