Technical FAQ

iMessage setup, international numbers, bounces, limits, and sender rules.
Want the basics first? Go back to the General FAQ.

Send an email to +country-code-and-number@your-subdomain.i.text.email. Replace your-subdomain with your account’s subdomain. Use the full phone number with + and country code, without spaces or punctuation.

For example, +447700900123@your-subdomain.i.text.email illustrates a U.K. number. The recipient must have iMessage enabled for that number. SMS and MMS support U.S. and Canadian numbers only.

To keep your existing email addresses, add recipients to Settings → iMessage Numbers. Those numbers will use iMessage. Removing a saved number restores normal routing; an address ending in .i.text.email still requests iMessage.

iMessage is not limited by your Maximum SMS Segments setting. Email attachments are included as links rather than native iMessage attachments. See the iMessage overview.

If your email bounced, it bounced for a reason. The bounce message will indicate what went wrong. You may have exceeded your account’s limits, your message may not have been approved by our content screening, or there may be another delivery issue. Read the details of the bounce. If you believe a content rejection was a mistake, request a review.

If you have a free account, you can send 10 total text messages, including SMS and iMessage. After 10, you need a paid plan to continue sending. MMS requires a paid plan.

Yes. You can put multiple your-number@your-subdomain.text.email addresses in the To, Cc, or Bcc line, and each of them will still receive an individual text message.

Yes. You can change it from your account’s settings page, but once you change it, any emails sent to your old subdomain will bounce and not convert to a text message.

In your email provider's forwarding settings, add your text.email address, such as number@sub-domain.text.email, as the forwarding destination. Replace number with the recipient's phone number and sub-domain with your account's subdomain. Your provider will usually send a verification email to that address and ask you to click a link to confirm forwarding.

If the confirmation link is missing from the text message or gets cut off, you can find it in the original email:

  1. Log in to text.email and open History.
  2. Find the log entry for the forwarding verification email sent by your email provider. Look for its sender or confirmation subject.
  3. Click Show email to open the full source email. Find the confirmation link in the Plain text or HTML view, then open it to confirm forwarding.

text.email has special handling for Gmail forwarding confirmation links to make this process smoother. With other providers, you may need to retrieve the link from the source email in History using the steps above. Once confirmed, return to your email provider's settings to finish enabling forwarding or choose which emails to forward.

SMS and MMS support U.S. and Canadian numbers only. iMessage supports iMessage-enabled numbers worldwide. For an international number, use the iMessage address format with + and country code. See the setup instructions.

With text.email, a subdomain is a word that is assigned to you when you create an account. If your subdomain is yoga, then you will send emails to your-number@yoga.text.email, for example. This is how we assign messages to the right account. Every user with text.email has a unique subdomain.

Sending without a subdomain is meant for testing only, just to show prospective users that the service works. You’re only allowed to send a few messages to your-number@text.email (without a subdomain), before your messages begin bouncing.

By default, all “from” addresses are allowed to send to your @your-subdomain.text.email address. You don’t need to configure anything. Only if you want to lock down who can send should you go to Settings and use the Authorized Senders section.

Add individual email addresses, entire domains, or both. Authorizing a domain allows every address at that domain and its subdomains. Once you add an entry, only emails whose visible “From” address matches an authorized address or domain will generate a text message; other emails are rejected. Remove all entries to allow all senders again.

See our Authorized Senders guide for setup instructions and testing tips.

We use the plain-text part of your email whenever it’s available. If your email doesn’t include a plain-text body but does include an HTML body, we’ll fall back to the HTML and convert it into readable text.

When we convert HTML, we:
  • Remove <head>, <style>, <script>, and HTML comments
  • Try to remove “hidden preheader” content (best-effort)
  • Turn common formatting into readable text (line breaks, paragraphs, and bullets)
  • Preserve links in a compact way (for example: Reset password (https://...) when it fits)
  • Strip remaining tags, decode entities, and normalize whitespace
  • Try to cut off large quoted/forwarded sections
Your formatting template controls how the subject and body are combined. Length limits depend on the delivery type:
  • SMS: Longer content is split into segments, up to your Maximum SMS Segments setting. Content beyond that limit may be cut off.
  • MMS: The text portion supports up to 1,000 characters.
  • iMessage: Supports up to 16,000 characters in one message and is not limited by Maximum SMS Segments.

Yes — links and email addresses are allowed in text.email messages.

For SMS and MMS, messages that contain URLs (and sometimes email addresses) can take longer to deliver because our upstream SMS providers and carrier networks often run extra automated checks on messages that look like they include clickable content. That can introduce a short delay compared to a plain text-only message.

If speed matters most, keep the message simple (no links). If you need a link, it’s fine — just expect delivery to occasionally be a bit slower.

Yes. Paid accounts can send a supported image or audio attachment directly into the recipient’s text-message conversation as an MMS. In your account settings, choose how text.email handles MMS:
  • No: Send regular SMS messages and turn attachments into links.
  • Auto: Send an MMS when an email contains supported media; otherwise send a regular SMS. This is the recommended setting.
  • Yes: Send every message as an MMS, including text-only messages.
The supported media types are JPG/JPEG, PNG, and GIF images and WAV audio. Files must be under 225 KB; text.email may resize or compress images to make them fit.

Each MMS can contain one media attachment and up to 1,000 characters of text. If an email contains multiple eligible files, text.email selects the most significant one for the MMS; additional files are delivered as links. Unsupported formats such as PDF, MP3, and MOV are also delivered as links.

MMS is available to paid subscribers and costs an additional $0.10 per MMS. See the complete email-to-MMS guide for more details.

This can happen after we review your account activity. We sometimes move legitimate users to a different SMS provider as part of ongoing anti-spam and deliverability improvements.

When that happens, the “from” number recipients see may change, and future replies will go back through the new number. The service still works the same — it’s just backed by a more reliable routing/provider for better delivery.

When you test the service anonymously or your account hasn’t been fully provisioned and verified, we route those messages through a conservative delivery path (a lower-priority routing/provider) that helps protect carriers and reduce abuse. That path can sometimes introduce noticeable delays for test messages.

After we provision your account and verify you as a legitimate user, we typically move you to a higher-priority routing method where messages usually arrive instantly. If you still see large delays after verification, contact support with timestamps and example message IDs so we can investigate provider-level routing for your account.

Yes. The text.email API lets your apps and scripts send SMS, MMS, and iMessage alerts directly over HTTPS. If your app, device, or monitoring system already sends email, add your text.email address as a recipient to turn those emails into texts.

To get started, confirm your account's email address and create a key in Settings → API keys. Copy the key when it is shown; it is only revealed once. Send it in an Authorization: Bearer YOUR_API_KEY header when calling https://api.text.email/v1/messages. Keep the key on your server rather than in public browser code.

The endpoint accepts GET and POST requests, with query parameters, JSON, or form fields. For a typical integration, use POST with Content-Type: application/json and a body like this, replacing the example number with your recipient's phone number:

{
  "to": "+14155550123",
  "text": "Alert: the nightly backup failed.",
  "type": "sms"
}
  • Required fields: to is the recipient's phone number with country code, and text is the message. Omit from_email when using an API key.
  • Message types: type can be sms, mms, or imessage; it defaults to sms. SMS and MMS support U.S. and Canadian numbers; iMessage supports iMessage-enabled numbers worldwide.
  • Text and media: SMS and MMS accept up to 1,000 UTF-16 code units of text; iMessage accepts up to 16,000. Some emoji count as two code units. API iMessage requests are text-only. MMS can include a base64-encoded JPEG, PNG, or GIF image of up to 600,000 decoded bytes in the JSON media object.
  • Account limits: Your account's sending allowance, SMS segment limit, and content screening still apply. Authenticated API requests are limited to 60 new requests per account per minute.
  • Retries: Include a unique Idempotency-Key header for each intended message and reuse that key with the same message when retrying. This prevents a retry from sending the message again.
  • Responses: HTTP 202 means the message was accepted by a provider or queued for iMessage; it does not confirm delivery to the recipient's phone. API messages appear in your account's History.

See the API documentation for complete request examples, media fields, authentication options, and error handling.

Still stuck? Check the bounce reason first — it’s usually the fastest way to pinpoint what happened.