bird email seeding runs
Usage
Code example
bird email seeding runsDescription
Reads show retained run progress and can lag recent writes. Provider acceptance and delivery are separate milestones. Canceling a run leaves already granted copies and the original source under their existing sending lifecycle.
Reads return JSON; list is paginated.
Procedure
Stop future seed admissions
Stop one run while preserving already granted copies and the original source.
bird email seeding runs get— Read the intended run and its state. An explicit request to stop this run supplies authorization; clarify an ambiguous run before acting.bird email seeding runs cancel— Already granted copies may still send. Stopping does not recall mail, cancel the original email or broadcast, or promise a refund. Before the first call, choose and retain an explicit idempotency_key. Without an explicit key, command confirmation derives a key from the exact request; repeating that request can recover its proposal under the same OAuth grant and workspace, including after access-token refresh or a new chat. The derived key is not returned as a caller-owned recovery key. Use a new explicit key for a new intent. Keep the same key after a lost response. Command calls require browser confirmation; resume the saved confirmation and wait for its recorded result before reporting the stop. A replay is a saved snapshot. Report the stop separately from unknown or pending outcomes. Even on a stopped run, pending does not establish admission or cancellation; unknown can resolve later. not_sent includes multiple no-send causes, so it cannot count deliveries prevented by this stop. Next: bird email seeding runs get
Commands
Related resources
Continue with the documentation, guides and examples for this topic.