United States · +1 · billed in USD

Transactional email API for United States

Receipts, alerts and one-time codes by email to customers in United States, from a domain you verify once. Billed in USD on the same account and key as your SMS.

Email in United States: the rules

Numeric sender only10DLC registration required

10DLC registration is mandatory for application-to-person traffic on long codes. Alphanumeric sender IDs are not deliverable. Opt-out keywords must be honoured automatically and confirmed to the recipient.

Opt-out keywords honoured automatically: STOP, UNSUBSCRIBE, CANCEL, END, QUIT, STOPALL.

Endpoint, currency, data

Endpoint
us.woyra.io
Currency
USD
Dialling code
+1
Data region
global
Price
$0.30 per 1,000 emails, first 3,000 a month free

Global

Your first Email call from United States

curl -X POST https://us.woyra.io/v1/emails \
  -H "Authorization: Bearer $WOYRA_KEY" \
  -H 'Idempotency-Key: receipt-4821' \
  -H 'Content-Type: application/json' \
  -d '{
    "from": "receipts@yourdomain.com",
    "to": "abebe@example.com",
    "subject": "Your receipt for order 4821",
    "text": "Thank you. Your order is confirmed."
  }'

The same key works on every endpoint. Calling us.woyra.io applies United States's rules and, where residency requires it, keeps the data in the global region.

What sending email to United States involves

Numeric senders, 10DLC registration required · billed in USD · global data region

Email does not change at the border

Mail to United States is carried the way mail is carried everywhere: a domain you verify once, DKIM keys Woyra generates, bounces and complaints suppressed automatically. What the United States endpoint changes is the account around it — USD billing, and the global data region.

Where this data lives

Global The residency of a message is decided when it is accepted and travels with it, so it cannot be moved later by a query written somewhere else.

Prepaid, with a cap you set

An account on the United States endpoint is billed in US dollars today. Billing in USD is where this is going, and it is a real advantage when it arrives, but a converted price needs a published rate behind it and there is not one yet, so we quote one currency rather than invent a second. Funds are reserved at the published price when a message is accepted and settled when it is delivered; a message we never deliver is never charged for, and a hard spend cap you set is enforced rather than invoiced.

One key, both directions

The same key sends SMS and one-time codes to +1 numbers, and the same domain receives: add the MX record and every address on it is an inbox, with replies linked to the email they answer.

Questions about United States

Is email delivery different in United States?

No. Email is carried the same way everywhere; what changes is the account: USD billing and the global data region.

Where is the email address of a customer in United States stored?

Global

Can I send SMS and email to United States from one account?

Yes. One key covers email, SMS, verification and lookup, and a verification can use both channels in one request.

What does a United States phone number look like in the API?

E.164: a plus, the country code +1, then the subscriber number, as in +1712345678. Woyra strips spaces, hyphens, brackets and a leading 00, but it will not guess a missing country code, because the same digits belong to a different subscriber in every country.

Which endpoint should I call for United States?

us.woyra.io, though the same API key works on every endpoint Woyra runs. Which one you call decides the compliance rules applied, the currency you are billed in, and — where residency requires it — which data plane answers.

Also in United States