Skip to main content
POST
/
v1
/
tools
/
email
/
domains
/
{domain}
/
resume
curl -X POST \
  https://win.oneshotagent.com/v1/tools/email/domains/oneshotagents.com/resume \
  -H "X-Payment-Proof: <your_x402_signature>"

{ "domain": "oneshotagents.com", "pool_status": "active" }

​
Authentication

Requires x402-verified wallet identity (X-Payment-Proof header). Same auth surface as /email/quote.

​
Path Parameters

​
domain
string
required
The bare domain to resume. Must be owned by the caller and currently pool_status='paused'.

​
Behavior

Restores pool_status to active. Only paused domains can be resumed — this is a deliberate gate to prevent warmup bypass.
FromResult
paused→ active
warming404 — the warmup gate must graduate the domain (daily reconciler), not the caller
active404 — already active
removed404 — not in the pool
Returns 404 domain_not_found whenever the transition isn’t allowed.

​
Response

​
domain
string
The resumed domain.
​
pool_status
string
active.
curl -X POST \
  https://win.oneshotagent.com/v1/tools/email/domains/oneshotagents.com/resume \
  -H "X-Payment-Proof: <your_x402_signature>"

{ "domain": "oneshotagents.com", "pool_status": "active" }

​
Why is warming → active blocked?

The whole point of warmup is that a freshly-provisioned mailbox sends low volume into a network of cooperating mailboxes that mark it as important and rescue it from spam. ESPs (Gmail, Outlook) build domain reputation from those signals. If the caller could pause a warming domain and resume it straight to active, that warmup machinery is defeated and the domain joins rotation with no reputation history — landing every send in spam. Warming → active happens only via the daily lifecycle reconciler, which gates on warmup_score >= WARMUP_ACTIVE_THRESHOLD (default 75).