Skip to content

by Startups.Studio

Post.schedule

POST /{namespace}/posts/{post}/schedule

Schedule puts a drafted Post on its Handle’s calendar for a set time.

Noun: Post
Mode: do
Event: Post.scheduled

You, to your agent

Schedule the latest post.

curl -X POST https://api.sb/ledgerlark.com/posts/post_1/schedule \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"at":"2026-10-22T12:00:00Z"}'

import { $ } from 'startup-builder'

const post = await $.Post.schedule({ post: 'post_1', at: '2026-10-22T12:00:00Z' })

npx startup-builder do Post.schedule --json '{"post":"post_1","at":"2026-10-22T12:00:00Z"}'

{
  "name": "do",
  "arguments": {
    "code": "return await $.Post.schedule({ post: 'post_1', at: '2026-10-22T12:00:00Z' })"
  }
}

Inputs

Input	Type	Required	Description
`post`	Post	required	The drafted Post.
`at`	`datetime`	required	When it goes out.

Outputs

Output	Type	Required	Description
`post`	Post	required	The scheduled Post.

Effects

Emits Post.scheduled.
Performed by the Content Lead.
Two-way: it runs at once, in the try, send and do modes.

Refuses when

Check	Error	Fix	Then call
The key is valid, but its scopes do not allow this operation.	`forbidden`	Use a key whose scopes cover the operation, or ask an owner of the namespace to grant them.	Post.schedule

When it waits

Gate	Default
Decision class	Low: two-way, nothing at stake
Delay window	None: it runs once review passes.
Limit	The call Limit of the Permission it runs under.
Over the Limit	It waits `pending` for an Approval from the Founder. Approved, it runs; refused, it ends `refused` with `limit-exceeded`; unanswered by its deadline, it ends `canceled`.

Post.publish

Previous Page

Post.update

Next Page