apiProvider-backed
Schedule post
PUT /api/content/posts/{postId}/publish
Schedule a content post to publish at a future time. The cron worker will pick it up and publish to LinkedIn when scheduled_at is reached. Use this instead of publish-post when you want a confirmation window (e.g. schedule for 10 minutes from now so a human can sanity-check). To cancel a scheduled post before it publishes, the user does that in the UI.
Parameters
workspaceId
string
Optional workspace ID or slug. Required when this credential can access multiple workspaces and no workspace was configured on the client.
postIdrequired
string
The content post ID (must be in draft status).
scheduled_atrequired
string
ISO 8601 datetime in the future, e.g. 2026-04-23T18:30:00Z.
Example
REST requestbash
curl -X PUT "https://app.pipeline.help/api/content/posts/00000000-0000-4000-8000-000000000000/publish" \-H "Authorization: Bearer $PIPELINE_API_KEY" \-H "Content-Type: application/json" \-d '{"scheduled_at":"2026-08-18T14:00:00.000Z"}'
Response
The operation is available, but its typed response schema has not been published yet.
HTTP errors
- 401
- Missing or invalid API key.
- 403
- Authenticated but not permitted for the workspace or resource.
- 404
- The requested resource was not found.