The short version
of everything we get asked.

An email address and a password. The account is live immediately: no confirmation link, no identity document, no company registration, no phone verification, no call.

As soon as the first top-up is confirmed on its network, typically a few minutes for Tron or Solana, ten to sixty minutes for Bitcoin depending on the fee you chose. The test key works immediately for integration without funds.

The test key lets you validate, price and integrate without spending anything. Real sends need a funded balance; the per-deposit minimum is small, so a modest first top-up is enough to send your first real messages.

228 destinations, listed on the coverage page with the rate and sender rule for each. Rates start at $0.0042 per message.

The panel works in any modern mobile browser: import a list, compose, schedule and read reports. Uploading large files is easier from a desktop.

Bitcoin, Monero, USDT, Ethereum, Litecoin, Solana and Tron. Each account gets its own deposit address per coin. Balance is shown in USD and debited per message.

After network confirmation: one confirmation for most networks, shown as pending until then. If a deposit stays pending longer than the network normally takes, check the status page, then write to support with the transaction id.

A small per-deposit minimum, set by the payment network and shown on the deposit screen for each coin. No deposit fee on our side; you pay only your network fee. USD conversion uses the market rate at confirmation time.

Never. An unused balance stays on the account indefinitely.

Unused balance can be refunded to a wallet in the coin it was deposited in, minus network fees, on request. Messages already accepted by a carrier are not refundable; rejected messages are never charged. Details in the refund policy.

A statement of top-ups and spend is available in the panel for any period, exportable as CSV or PDF. Add your own details to it; we do not need them.

CSV, TXT and XLSX up to 50 MB, or paste numbers directly. Numbers are normalised to E.164; every other column becomes a variable for personalisation.

Rows are removed when the number cannot be resolved (too short, too long, unknown prefix) or when it duplicates another row after normalisation. The import report lists each removed row with the reason. Removed rows are never billed.

Use any column name in braces: {first_name}, {order_id}. The preview cycles through real rows and shows the longest rendered message and its segment count.

On the schedule step, choose a local start and end hour. The campaign opens in each destination when its clock reaches the start and pauses at the end. Quiet hours per country apply by default and can be edited.

Yes, instantly. Queued messages stop; messages already handed to carriers still deliver. Resume or cancel the remainder at any time.

Each destination has its own rate, listed on the pricing page. A mixed list is priced row by row and the cost preview shows the split before you send.

Queued: accepted and priced. Sent: handed to the carrier, billed. Delivered: the handset confirmed receipt. Failed: the carrier could not deliver; the reason is attached. Expired: not delivered within 48 hours. Rejected: refused before sending, never billed.

Their country does not deliver alphanumeric senders, or requires them to be registered first. The rule is shown on each country page and the report tells you, per message, which sender was used. The sender ID guide explains the three rules.

Open a request from the sender settings. Support prepares the file and submits it where the destination accepts foreign senders. Traffic keeps flowing from a shared numeric sender until approval.

Some handsets are off, some numbers are dead, some carriers filter. The failure breakdown in the report says which reason dominates; a rising unknown-number share means the list needs cleaning.

90 days per message, searchable and exportable. Campaign summaries are kept indefinitely.

Panel, Developers, Create key. Choose the scopes (send, read) and optionally an IP allowlist. The key is shown once. A test key exists on every account.

50 requests per second per key for single sends. The batch endpoint accepts 1,000 messages per API request. Over the limit you receive 429 with a Retry-After header.

Because you sent the same Idempotency-Key. That is the intended behaviour: same key and payload within 24 hours returns the original response. Details in the API reference.

Check that the endpoint is HTTPS with a valid certificate, answers any 2xx within 5 seconds, and that the event types are subscribed. Undelivered attempts and the response we saw are listed per endpoint in the panel; replay from there once fixed.

Compute HMAC-SHA256 over the timestamp, a dot and the raw body with the endpoint secret, and compare with the v1 value in X-Meteor-Signature. Code in three languages is on the webhooks page.

Your email address, your messages and their delivery data for 90 days, and the deposit transactions. Nothing about your identity, because we never asked for it. The privacy policy has the full list.

Anything illegal in the destination, phishing, impersonation of banks, carriers or public services, unsolicited bulk to harvested numbers, and marketing sent as transactional. The acceptable use policy is short and enforced; violations close routes and can close the account.

Use a unique password, enable two-factor authentication in settings, create one API key per system with the smallest scope, and set IP allowlists on keys that run from fixed servers.

Yes. Invite team members with roles: viewer, sender, admin. Each has their own login and two-factor; API keys are per account, not per user.

Request a refund of any remaining balance, then close from settings. Message data is deleted at the end of the 90 days retention period unless you ask for earlier deletion.