Textbelt Clients Send free SMS text messages without registration and CAPTCHA
"Textbelt Clients" is built against the free & cool textbelt.com API, this extension allows you to send SMS text messages for free, without requiring any registration nor entering CAPTCHA codes.


  1. Where can I get more info about how to install Textbelt Clients?

    Please check https://github.com/daluu/textbelt-clients/wiki/Textbelt-clients,-installation-and-download

  2. What is Textbelt?

    Built against the free & cool textbelt.com API, this extension allows you to send SMS text messages for free, without requiring any registration nor entering CAPTCHA codes. There is some limits on the number of messages you can send in a day and within a short period of time. See textbelt.com for details on limitations.

    SMS support limited to carriers noted at textbelt.com.

    Unfortunately, this service doesn't offer option to supply a reply number or address for recipient to reply to. But you can put that inside the SMS message if needed.

    I built this extension since the service provider is only an API (for developers). Well, here's an extension for the everyday folks to use it, no scripting/programming needed.

    Source code for the extension will be available at https://github.com/daluu/textbelt-clients

    You can try to get support at the Github site link above. Bear in mind some of your support issues may be specific to the Textbelt API rather than the extension, so then I may not be able to help you in that case, contact the API developer at textbelt.com instead.

  3. Why is (carrier name) not supported?

    The current supported list of carriers can be found at http://www.textbelt.com.

    The way the service works for sending SMS text messages is by routing the message by email. It goes to the carrier's mail server and gets translated to an SMS message that then routes to the phone. For this to work, the carrier needs to offer an email-to-SMS gateway for us to send the message through via an email like phone-number@carrier.com.

    Think of it this way, basically, you pay (as part of your phone service plan) to send SMS to recipient from your phone. The plan provider receives your SMS to recipient's phone number and does a lookup via some directory/algorithm, etc. to find out which phone carrier the recipient is on based on the phone number and then passes it to the SMS gateway of the recipient's carrier. Unfortunately, I believe that lookup process isn't really available for free, hence free services like Textbelt probably resort to alternate options. For example, you can find a carrier's email-to-SMS gateway so that you can send SMS to recipient from your email account, see http://en.wikipedia.org/wiki/List_of_SMS_gateways or http://martinfitzpatrick.name/list-of-email-to-sms-gateways. You just need to know the gateway (meaning you need to know the carrier). So of course there's a catch when things are free (i.e. just a little more work to send a message).

  4. Why do I get status message that my message was sent but recipient never receives the message?

    See the previous question on Why is (carrier name) not supported? Could be an issue/bug with the carrier, limited/partial support. Or you are sending to a carrier/service that is not supported. The Textbelt API/service can not check whether the destination carrier is supported or not to let you know as a status response.

    Some noted examples of sending messages that will never be received but look like success based on status message:

  5. Why are there limits to sending SMS messages?

    To prevent spammers, bots, and automation etc. to easily send out spam messages to many people (abuse prevention). The current limits are 75 messages per day per IP address, 3 texts per 3 minutes to a given phone number, all according to http://www.textbelt.com.

  6. Why do I get a message like "Exceeded quota for this phone number"?

    The API/service provider imparts a limit on the use of the service to prevent potential abuse (spam, denial of service attacks, etc.) If you are receiving that message, you are likely overusing the service, or someone in your network/home is, or your IP address has been spoofed somehow by someone else and they're using the service.

    You can contact the service provider to request for a limit increase, you'll probably have to give the developer your IP address information for that.

  7. Why is there no option to provide a sender/return phone number or email address?

    Ask the (API) service provider for the reasoning behind that. You can however, add your contact info as part of the SMS text message as a workaround.

    The clients I build are limited/restricted to the API functionality offered by the SMS service provider that I'm using for these clients.

  8. What if I don't like these clients?

    You are welcome to try others that exist. There are not many that are free and w/o registration or restrictions. One other you could try is AutoSMS

Matched Content


Please keep reviews clean, avoid the use of improper language and do not post any personal information.
  • <a> Defines an anchor.

    Example: <a href="http://add0n.com">a sample link</a>

  • <pre><code> Syntax Highlighting (Supported languages: Bash, JSON, HTML, JavaScript, and CSS).

    Example: <pre><code class="javascript">var foo = 'bar';</code></pre>

  • <strong> Defines bold text
  • <blockquote> Defines a long quotation
  • <caption> Defines a table caption
  • <cite> Defines a citation
  • <em> Defines italic text
  • <p> Defines a paragraph
  • <span> Defines a section in a document
  • <s> Defines strikethrough text
  • <strike> Defines strikethrough text
  • <u> Defines underlined text
  • <br> Defines a single line break; can be used alone and don't need an ending tag

What's new in this version

Change Logs:
    Last 10 commits on GitHub
    Hover over a node to see more details

    Need help?

    If you have questions about the extension, or ideas on how to improve it, please post them on the  support site. Don't forget to search through the bug reports first as most likely your question/bug report has already been reported or there is a workaround posted for it.

    Open IssuesIssuesForks

    Recent Blog Posts on add0n.com