sending_settings
Read or set account-level limits on outbound campaign volume. action='get' returns { daily_email_send_cap, sent_today, remaining_today, timezone }; action='set' writes daily_email_send_cap. The cap is the maximum campaign EMAILS this account may send per calendar day in the account's own timezone. It is per ACCOUNT, not per campaign — eight campaigns sending "only 20 each" is still 160 emails from one domain, and reputation attaches to the domain. Use it to warm a new sending domain: start around 20/day and raise it weekly. SMS campaigns are never counted. When the cap is reached, remaining recipients stay QUEUED and send on following days — nothing fails, nothing is skipped, and drip step spacing still runs from each recipient's actual send time. null means uncapped; 0 means send no email today. PER DOMAIN: pass domain to cap one sending domain on its own budget. Reputation attaches to the domain, so with two domains in play a single account-wide number throttles the pair jointly and cannot stop the whole day's allowance landing on one of them — which is how a warming domain gets burned. BOTH APPLY: the account-wide cap is a total across every domain, and a domain's own cap sits inside it — an email sends only if it fits under both. A domain with no cap of its own is held by the account-wide cap alone, so single-domain accounts need not set any. action='get' returns domain_caps, each with its own sent_today and remaining_today. Use resend_manage(action='domains') to see which domains are verified.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | 'get' to read, 'set' to write. | |
| domain | No | For action='set'. Bare hostname, e.g. 'example.com'. Caps only mail sent from that domain, inside the account-wide cap. Omit to set the account-wide cap, which totals every domain and is the only cap on a domain without its own. | |
| daily_email_send_cap | No | For action='set'. Non-negative integer, or null to remove the cap entirely. |