What is new in textbee

The signup form now suggests a correction when your email looks mistyped, for example gmail.con. The verification page shows the address your link was sent to. If it is wrong and you have not verified yet, you can change it there with your password and get a new link.

When a message fails, the dashboard, the API and webhooks now say what happened and how to fix it, the same way for every app version. The message history shows the reason on each failed row and marks messages that failed before they went out. The API adds errorName, a stable name to match on, deviceMessage with the phone's original text, and docsUrl when a docs page explains the fix.

The send form marks short codes and says that the phone may ask you to allow the message. It also names the exact problem with a recipient, for example a number that is too short or too long.

The dashboard now sends to short codes and to local numbers in the same country as the phone, not only to numbers with a country code. The API and SDKs already accepted them. A recipient that contains letters, such as a sender name, now returns a clear 400 error instead of a failed message, and Reply is off for sender names that cannot receive SMS.

Every webhook delivery now carries a timestamped signature in the X-Textbee-Signature header. Verify it against the raw body and reject requests signed more than 5 minutes ago, so a captured request cannot be replayed. Integrations that check X-Signature keep working. See textbee.dev/docs/webhooks#verify-the-signature.

Free accounts can have 5 webhook subscriptions, Pro accounts 10 and Scale accounts an unlimited number. The Webhooks page shows how many you use. Email [email protected] if you need more.

The textbee Trigger in n8n now creates its own webhook when you publish the workflow, so you add nothing in the textbee dashboard. The credential needs only your API key, and each workflow gets its own signing secret. After you upgrade the node, publish your trigger workflows again.

Install @textbee/n8n-nodes-textbee from Settings > Community Nodes in self-hosted n8n. The textbee node sends SMS, reads message history and works as a tool for the AI Agent. The textbee Trigger starts a workflow when your phone receives a text, or when a sent text is delivered or fails. It builds on the first version by Julius Haring. n8n Cloud gets the node after n8n verifies it.

The textbee server, dashboard and Android app are now open source under the GNU Affero General Public License v3.0. You can still self-host and use textbee commercially. If you modify it and offer it to others as a service, you publish your changes. Code from before 4 November 2026 stays under MIT. The SDKs and the MCP server stay MIT.

Each message now keeps an issue history: the failures it had, even after it goes out, and delivery reports that did not confirm delivery. The message details list them, and the API returns them as issueHistory. The failure box shows only on failed messages, a late report from the phone no longer moves a delivered message back to sent, and webhooks fire once per status change.

The textbee package is on PyPI. Run pip install textbee to send SMS, read message history, and verify webhooks from Python 3.9 or newer, with no other dependencies to install.

A send batch now shows what happened to its messages: completed, failed, partial_success or unknown, updated with each report from the phone. Each batch also counts its messages by state, so you can see how many are pending, dispatched, sent, delivered, failed or unknown.

The monthly message allowance now resets on the same day every month: your signup day on the Free plan, your plan start day on a paid plan. The billing page shows the exact reset date.

The dashboard now warns you as soon as the phone reports the SMS permission as off, before the first message fails. Devices show an SMS permission off badge, and a failed test send shows the fix steps in place.

Add mcp.textbee.dev as a custom connector in claude.ai, click Connect, and paste your API key. Claude can then send and read SMS on the web, in Claude Desktop, and in the Claude mobile apps.

Each message gets its own send time, so one slow message no longer holds up the rest. Messages also go out promptly while the phone is in battery saving.

A new screen in Settings checks permissions, notifications, battery usage, power saving, and the connection to textbee, and tells you what to change for each one. Phones that stop background apps get steps for that brand.

See sent messages, received messages, and app events in one place. Tap a message to follow it from the moment the phone got it to delivery, or export a diagnostics file for support that leaves out message text.

The app tells you when a newer version is available and opens the download page with one tap.

The @textbee/sdk package is on npm, with typed helpers for sending messages, reading history, and managing devices from any TypeScript or JavaScript project.

The SDK ships helpers for counting message segments, detecting encoding, and normalizing recipients, with no extra dependencies to install.

The @textbee/mcp package lets Claude, Cursor, and other MCP clients send SMS, read message history, and list devices through your own phone. Run it locally with npx.

Connect claude.ai and other remote MCP clients to mcp.textbee.dev with your API key. There is nothing to install.

Query messages from all of your registered phones in a single call, filtered by device, batch, or status.

The whole API is described in a machine readable spec, so you can generate a client for your language or import it straight into Postman or Insomnia.

Requests no longer need a device ID. Leave it out and textbee sends from your default device, which makes the first API call a one-liner.

Large batches go out in waves that match your device's send delay, and the send response includes an estimated completion time.

API keys are verified with an indexed lookup, cutting latency on every single request you make.

Each registered phone displays the Android version it is running, so you can spot the devices that need attention.

The bulk send flow shows how long a large batch takes to deliver, based on the send delay of the device you pick.

A Discord server for support, feature requests, and release announcements, linked from the app, the dashboard, and the site.

All emails now share one clean design. Usage alerts show your numbers in a clear block and explain that the monthly allowance counts a rolling month.

A new app shell with a persistent sidebar, a keyboard command palette, and a proper mobile navigation bar, plus a home page that opens on your real usage and recent activity.

One search box reaches devices, messages, and settings from any page.

Bulk sending is now a four step flow that parses your CSV or recipient list, flags invalid numbers, and previews the batch before anything goes out.

The compose box shows how many SMS segments a message will use as you write it, so the cost of a send is never a surprise.

Find any sent or received message by its text, its recipient, or its sender.

Every webhook endpoint gets its own signing secret, so you can rotate one without breaking the others.

Profile, security, billing, and support moved under a single settings area, with a rebuilt billing page.

The gateway app was rewritten from the ground up with a new interface: a clearer dashboard, upfront permission warnings, usage bars, and dedicated message and settings screens.

First run walks you through pairing your phone and granting the permissions the gateway needs, one step at a time.

A higher volume tier above Pro, with a larger message allowance and room for more registered devices.

Upgrading or downgrading adjusts your existing subscription instead of starting a fresh checkout, and cancelling keeps your paid plan until the period ends.

Register several endpoints per account and have every event delivered to all of them, instead of being limited to one.

Remove a phone you no longer use, end to end, without contacting support.

A failed payment now raises an unmissable alert with a direct link into the billing portal to fix the card.

The app asks for a smaller set of permissions and no longer requests anything it does not need to run the gateway.

Set a pause between outgoing messages so your carrier or handset does not throttle a large batch, with automatic retries and clearer reasons when a message fails.

Failed deliveries retry over a longer window, and endpoints that keep failing are disabled automatically so a dead URL does not back up your queue.

Reach a human from inside the product instead of switching to email.

The dashboard tells you when a registered phone is running an old version of the gateway app.

A set of free utilities for everyday SMS work, including segment and character counting and phone number formatting.

Try the API from your browser and see the exact request and response, without writing a line of code.

Name your phones something meaningful instead of reading raw model strings, shown everywhere the device appears.

Choose which SIM sends the message on dual SIM phones, directly from the send form.

Rules in the app decide which incoming messages get forwarded, so you can ignore noise from senders you do not care about.

Registered phones check in on a schedule, so the dashboard can show whether a device is genuinely online rather than just registered.

Choose which SIM slot sends a message as part of the send request.

Ask for a message to go out after a delay instead of the moment the request lands.

Support requests and account deletion requests are shielded from automated abuse.

Accounts can be given limits above the standard plans when a project needs more headroom than a tier provides.

Get an email as you approach your plan limit, so sending never stops without warning.

Every webhook attempt is listed with its payload, response status, and failure reason, so you can debug an integration instead of guessing at it.

Webhooks fire on outgoing message events too, not only on messages you receive.

Read your current consumption and remaining allowance programmatically.

The free plan allowance went up, so smaller projects can run without paying anything.

Each message reports back as sent, delivered, or failed, with the reason attached when something goes wrong.

Fetch the current status of a single message or an entire batch from the API.

A rebuilt interface with a new logo and brand colors, plus crash reporting so problems surface and get fixed faster.

The app runs as a persistent foreground service and restarts itself after the phone reboots, so Android stops quietly killing it in the background.

A cleaner layout across devices, messages, and settings.

Incoming messages and delivery statuses queue up while the phone has no connection and sync as soon as it is back.

Bulk recipient lists accept far bigger files in a single request.

Send a support request from inside the product instead of hunting for an email address.

Request deletion of your account and its data directly from the dashboard.

Open an incoming message and reply to it without leaving the dashboard.

Browse everything you have sent, paginated and refreshing on its own.

Queue messages to go out later instead of the instant the request arrives.

Step by step onboarding docs and worked examples for the setups people build most often.

Pricing tiers with hosted checkout, so you can move past the free allowance and manage your subscription from the dashboard.

New accounts confirm their email address, which cuts abuse and keeps important notices deliverable.

Send the same message to a long list of recipients in one go, from a dedicated bulk send screen or straight from the API.

Subscribe an HTTPS endpoint and have received messages pushed to your server with a verifiable signature, instead of polling for them.

A full dark theme across the dashboard and the site.

Update your details and change your password yourself, no support ticket required.

Published container images and a compose file, so you can self-host the entire gateway on your own infrastructure.

The public API moved to a consistent naming scheme, with the previous paths kept working so nothing broke.

Label your keys so you know what each one is for, and revoke or remove the ones you have finished with.

Incoming messages show the right local time, and recipient and message validation got stricter.

Messages arriving on your phone are forwarded to the API, turning textbee into a two-way gateway rather than a send-only one.

A dedicated inbox listing every message your devices have taken in.

Target many recipients in a single request and track them together as one batch.

Authenticate with an x-api-key header instead of a query string, so keys stop leaking into server logs.

Grab a device ID straight from the dashboard while wiring up your API calls.

Dual SIM phones can send from whichever SIM you pick.

Per device counters and account totals showing how much you have actually sent.

Recover a forgotten password by email on your own.

Request throttling that keeps the gateway responsive for everyone using it.

A major overhaul of the gateway app, alongside a rewritten landing page.

A web dashboard for sending a message and seeing your registered devices, without touching the API.

One click sign in alongside email and password.

Pair a phone by scanning a QR code from the dashboard, which issues an API key for it on the spot.

Authenticate your requests with a key tied to your account.

The first working version. Your Android phone registers with the API, receives a push, and sends the SMS from your own number. Long messages split automatically.