Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability for users to specify carrier #56

Open
typpo opened this issue Nov 27, 2015 · 2 comments
Open

Add ability for users to specify carrier #56

typpo opened this issue Nov 27, 2015 · 2 comments

Comments

@typpo
Copy link
Owner

typpo commented Nov 27, 2015

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.

@daluu
Copy link
Collaborator

daluu commented Nov 28, 2015

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.

A reference example to this suggestion can be seen at: http://www.watacrackaz.com/autosms/api.php. See the API endpoint for get carrier list.

I assume with this enhancment, specifying unknown/undefined (or unsupported) carrier results in some error message returned by the API.

@alexionescu
Copy link
Contributor

I'll take a look at this.

alexionescu added a commit to alexionescu/textbelt that referenced this issue Nov 28, 2015
typpo added a commit that referenced this issue Dec 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants