Source
Publishing & calendar — found from sitemap — Publer
Checked for Publer on 1 Oct 2026
- Page
- https://publer.com/docs/posting/create-posts/publishing-methods/bulk-scheduling
- Checked
- 1 Oct 2026, 13:54 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:3dcdd48ad30a51e2587fe0e276eb835f574760df9fdb42db4e092bc9867d82b4
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Bulk scheduling max posts Report an error
“Efficiently schedule up to 500 posts across multiple accounts and networks in a single API request.”
-
Bulk scheduling API endpoint Report an error
“POST /api/v1/posts/schedule”
-
Bulk scheduling modes Report an error
“Choose between Schedule, Auto Schedule, or Recycle modes.”
-
Bulk scheduling content types Report an error
“Supports text, images, videos, and more.”
-
Bulk scheduling same accounts required Report an error
“Every object in bulk.posts must contain the same accounts array. The accounts[].id values (and their order) must be identical for every post. Only per-account fields such as scheduled_at may differ.”
-
Bulk scheduling fallback schedule Report an error
“Posts without a scheduled_at field use the account’s posting schedule.”
-
Bulk scheduling no recurring Report an error
“Recurring posts are not supported in bulk scheduling.”
-
Bulk scheduling per post options Report an error
“All other post options (media, watermarks, signature, location, etc.) supported per post type”
-
Bulk scheduling state values Report an error
“Scheduling mode: "scheduled" (manual schedule), "auto", or "recycle"”
-
Bulk scheduling required headers Report an error
“Authorization Yes Bearer-API YOUR_API_KEY Publer-Workspace-Id Yes Workspace ID for scheduling posts Content-Type Yes application/json”
-
Bulk scheduling async monitoring Report an error
“Send your payload to /posts/schedule and monitor job status for completion.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.