Post Queue

The post queue lets you line up content and have Octopost publish it automatically throughout the day. Instead of scheduling each post for a specific time, you add posts to the queue and Octopost spaces them out during your active hours.

How It Works#

1. Add posts to the queue by setting queueStatus: "queued" when creating a post
2. Octopost publishes them automatically during your configured active hours, spaced at your chosen interval
3. Posts publish in the order they were added (oldest first)

The queue respects your timezone and active hours. If you set 9 AM - 8 PM Eastern with a 4-hour interval, posts will go out around 9 AM, 1 PM, 5 PM, and so on.

Queue vs Scheduling#

Use the queue for evergreen content you want published regularly. Use scheduling for announcements, launches, or anything time-sensitive.

Adding Posts to the Queue#

# Add directly to queue (publishes automatically)
curl -X POST https://octopost.ink/api/posts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "This will be published during active hours",
    "platforms": ["twitter", "bluesky"],
    "queueStatus": "queued"
  }'

Approval Workflow#

For posts that need review before publishing, use "queueStatus": "pending":

# Add to queue, needs approval first
curl -X POST https://octopost.ink/api/posts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Review this before it goes live",
    "platforms": ["twitter", "linkedin"],
    "queueStatus": "pending"
  }'

Pending posts won't publish until a person approves them. Octopost emails the account owner (and any approvers) one-tap Approve / Reject / Edit links, and they show on the Posts page. Once approved, they join the queue in their original position. An API key can't approve a post it made; see Approvals for who can approve, auto-approve rules and approver seats.

Removing from Queue#

# Remove a post from the queue (becomes a draft)
curl -X DELETE https://octopost.ink/api/posts/:id/queue \
  -H "Authorization: Bearer YOUR_API_KEY"

Queue Settings#

Configure how the queue behaves:

# Get current settings
curl https://octopost.ink/api/queue-settings \
  -H "Authorization: Bearer YOUR_API_KEY"

# Update settings
curl -X PUT https://octopost.ink/api/queue-settings \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true,
    "intervalHours": 4,
    "startHour": 9,
    "endHour": 20,
    "timezone": "America/New_York"
  }'

Settings Reference#

Evergreen Posts#

Mark a published post evergreen and the queue posts it again when it runs empty, so your accounts stay active between new posts.

• In an empty queue slot, Octopost picks the evergreen post that has rested longest and posts a copy of it.
• The same post goes out at most once every 30 days.
• It is skipped while the same text is on (or going to) the same network within those 30 days. X refuses posts that repeat one of your recent posts word for word, so this keeps evergreen posts from failing there.
• Posts with one of your blocked terms are never re-posted automatically.
• It only runs while the queue is on. You can mark a draft or scheduled post now; it becomes eligible once it has been published.

Turn it on with the Evergreen switch on the post, the MCP tool set_evergreen, or the API:

# Mark evergreen (DELETE to turn it off)
curl -X POST https://octopost.ink/api/posts/POST_ID/evergreen \
  -H "Authorization: Bearer op_..."

Tips#

• Start with a 4-hour interval and adjust based on engagement
• Mix platforms in your queue. Some posts work better on certain platforms
• Use pending status for posts with links or mentions that need a final check
• The queue pauses overnight based on your active hours. No 3 AM posts unless you want them
• You can still schedule individual posts for specific times alongside the queue