Developer tools

Moving from Twilio

Swap a Twilio send for BlueBot’s and text from your own number instead of a rented one.

What you can do

Swap a Twilio send for BlueBot’s by sending the fields to and text in place of To and Body.
Send from your own number, so there’s no From to set and no number to rent.
Get replies as signed message.received webhooks in place of Twilio’s inbound webhook.
Replace status callbacks with webhooks for delivery and read states that carry your own metadata.

API
Your own code calls BlueBot’s REST API and listens to its signed webhooks.
API in the docs

Recipes

Set one up as written, or change it to fit how you work. The docs have the same recipes step by step.

01With the API

Starts when

Your code sends a text

Replace the call to Twilio’s Messages API with POST /v1/messages.
Send the fields to and text where you sent To and Body, and drop From, since BlueBot sends from your own number.
Add an Idempotency-Key so a retried request never sends twice.

The text it sends

Your appointment is confirmed for tomorrow at 10 AM. Reply here with any questions.

From your own number

02With the API

Starts when

A text comes in (BlueBot’s message.received webhook)

Add your endpoint in BlueBot as a webhook for message.received.
Read the sender and the words from the JSON body, where Twilio sent From and Body as form fields.
Check the webhook-signature header with your whsec_ secret in place of X-Twilio-Signature.

03With the API

Starts when

A text you sent changes state

Put your own IDs in metadata when you send.
Subscribe to message.delivered, message.read and message.failed, each of which carries that metadata.
Read the hold on a queued text to see why it’s waiting, such as quiet hours.

You need a card to start the trial. After 7 days it’s $17.99 a month plus any tax, and you can cancel from your billing page at any time.