Core Concepts
Scheduling
Schedule content at least 5 minutes ahead, and change it until 5 minutes before it goes live.
Send scheduledFor as an ISO 8601 datetime with a time zone, like 2026-12-01T15:00:00Z or 2026-12-01T10:00:00-05:00. It must be at least 5 minutes from now. Our team handles publishing, so content goes live on or shortly after that time.
Lead Time
- Scheduling: a
scheduledForless than 5 minutes away returns400, and the message names the earliest time allowed, so you can retry with it. - Changing: you can edit, reschedule or cancel content until it is 5 minutes from going live. After that, the API returns
409 conflict. - canChange: every post and comment carries
canChange, which says whether you can still change it right now.
{
"error": {
"code": "conflict",
"message": "This content goes live in under 5 minutes and can no longer be changed"
}
}Statuses
| Status | Meaning |
|---|---|
draft | Saved without a date yet |
pending_approval | Written by our team and waiting for your approval. Its ID is a UUID |
approved | You approved it. It shows as scheduled once our team puts it on the calendar |
scheduled | On the calendar and waiting to go live |
posted | Live on Reddit. url, upvotes and commentCount are filled in |
failed | Could not be published, or was removed. failureReason says why |
cancelled | Cancelled before it went live |
Content Waiting for Approval
Content our team writes for you arrives as pending_approval. Approve it to put it on the schedule, or leave a review note to ask for changes. Content waiting for approval cannot be cancelled through the API; leave a note or ask your account manager.
