Technical 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.
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.
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:
- Log in to text.email and open History.
- Find the log entry for the forwarding verification email sent by your email provider. Look for its sender or confirmation subject.
- 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.
+ and country code.
See the setup instructions.
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.
your-number@text.email (without a subdomain), before your messages begin bouncing.
@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.
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
- 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.
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.
- 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.
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.
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.
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:
tois the recipient's phone number with country code, andtextis the message. Omitfrom_emailwhen using an API key. - Message types:
typecan besms,mms, orimessage; it defaults tosms. 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
mediaobject. - 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-Keyheader 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
202means 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.