What is new in textbee

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.

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.

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.

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

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.