Read outbound email usage
Requires customers:read. Messages sent to your users’ inboxes this calendar month, per environment, with the plan’s monthly allowance.
Both environments, unlike the active-contact meter — and the difference is deliberate. A test contact is not a customer and is never billed; a test email is delivered by the same provider to the same inbox at the same price, so it is counted. Each environment has its own allowance, so a script in test can never spend live’s month.
Every message declares what it is worth, and the class is what decides its right to the last quota when an environment runs out:
security— reports a change to, or a risk on, an existing account (a sign-in from a new address, a linked provider, a password found in a breach). Never withheld.credential— carries the way in or back in: address verification, magic link, one-time code, password reset, waitlist admission. Never withheld — withholding one would refuse an authentication, and no authentication method is ever gated here.courtesy— confirms something the recipient already knows: the welcome note, the waitlist confirmation, the “you already have an account” reply. This is the only class an environment past its allowance stops sending, and nothing downstream waits on one.
Owners are warned by email at 80% and 100% of the allowance, once per threshold per month. limit is null on a plan with no ceiling.
Autorizações
A staff session token, uk_st_…. Minted by sign-up, sign-in or the two-factor exchange.
Cabeçalhos
The organization the caller is acting on — the org_… code that appears in the panel URL. It identifies; the membership JOIN is what authorizes, so a forged code reads nothing. Absent, the session's default organization answers.