Textbelt API
Textbelt API
Tool
textbelt_send_an_sms
Send an SMS using HTTP POST. Note: No Urls in text message. Max 800 characters
Pricing
Per call
$0.05
Model
flat
Pay only for what you use. No subscriptions.
Inputs
replyWebhookUrl
stringmessage *
stringphone *
stringsender
stringwebhookData
stringTry It
API
MCP Config
Input Parameters
U.S. phone numbers only: Textbelt lets you receive replies to SMS you've sent. Replies are sent by webhook, meaning you will have to set up an HTTP or HTTPS route on your website that will process inbound SMS.This will send an SMS. If the recipient responds, Textbelt will send an HTTP POST request to the specified endpoint (in this case, https://my.site/api/handleSmsReply). The webhook payload is application/json encoded. Your server must interpret it like any other HTTP POST request with a JSON payload. The JSON payload contains the following: textId: The ID of the original text that began the conversation. fromNumber: The phone number of the user that sent the reply (you can use this, for example, to send them a response depending on their reply). text: The content of their reply. Here's an example payload: { "textId": "123456", "fromNumber": "+1555123456", "text": "Here is my reply" }
The content of your SMS.
A phone number. If you're in the U.S. or Canada, you can just send a normal 10-digit phone number with area code. Outside the U.S., it is best to send the phone number in E.164 format with your country code.
Optionally, the name of the business/organization you represent. This field is for regulatory purposes and is not visible to the end user in most countries. If not set, sender will default to your account-wide sender name.
Endpoint supports a webhookData field. This data is passed as data in the webhook request. There is a maximum length of 100 characters in the webhookData field.