Email customers to update their payment method
Ask a set of customers to replace the payment method on their subscription before the next renewal runs, for the Subscription Billing day drawer.
Pre-emptive, and distinct from the dunning pipeline’s mail: this one goes out while the renewal is still scheduled, so it does not say anything has failed.
Every token is answered. A token is sent when the mail was queued and recorded, skipped when the customer must not be mailed — with the reason — or failed when no subscription of that token belongs to the caller, or the mail could not be queued. A batch carries at most 500 tokens once duplicates are collapsed; a larger one is refused whole.
A customer asked within the quiet period is skipped rather than asked again, so repeating the request mails nobody twice. Each send writes a durable record, which is what the skip is read from.
Authorizations
Bearer token authentication
Body
Who to ask, and which renewal the ask is about.
Subscription tokens. Duplicates are collapsed before the batch runs, and the deduplicated count is what the maximum is applied to.
1 - 500 elementsThe renewal date being worked, as YYYY-MM-DD. Recorded against each send
so the drawer can count them per day — an operator working the 14th on the
12th is asking about the 14th, not about the day they pressed send.
"2026-09-14"
Response
Every token answered as sent, skipped, or failed
One entry per token sent, across three lists.