What is watched
Amazon’s own thresholds are a 5% bounce rate and a 0.1% complaint rate over the account, so Sendbaze acts per organisation before the platform is at risk.
When sending is paused
POST /v1/emailsand/v1/smsreturn423 org_pausedwith the reason. Reads, the dashboard and test keys keep working.- The dashboard Overview shows why and lists the addresses that complained on the Suppressions page.
- To resume: remove those addresses from your external lists, make sure marketing email only goes to people who opted in, then email support@sendbaze.com for a review. A pause is not a penalty; it stops a bad list from doing lasting damage to your domain.
Habits that keep you in the inbox
- Verify a dedicated subdomain for automated mail and another for marketing.
- Publish DMARC and move from
p=nonetop=quarantineonce your legitimate senders are aligned. - Send both HTML and text parts, keep HTML simple, avoid link shorteners.
- Handle bounce and complaint webhooks so your own lists stay clean.
- Warm up gradually when you start: a few hundred a day, doubling while bounces stay low, rather than a large blast from a cold domain.
- Never buy lists. Purchased addresses produce the complaints and spam traps that pause organisations.
Warm-up
Receivers judge a new sender by its early behaviour, so Sendbaze ramps every new organisation on the shared pool:- The cap counts live emails per UTC day; test keys are not counted.
- A send over the cap is refused with
429 warmup_limit_reached, nothing is queued, and theRetry-Afterheader says how many seconds until the next UTC day. Queue the rest on your side and retry with the sameIdempotency-Key. - If the bounce rate is 2% or more, the cap holds for another day instead of doubling. Clean the list and it resumes.
GET /v1/usagereturnswarmupwith today’s cap, how many were sent and the reset time, and the dashboard Overview shows the same.warmupisnullonce warm-up is complete.- Migrating an established sender with a clean list? Email support@sendbaze.com and we will lift the cap after checking your history.