Add post to queue
Add a post to the business's posting Queue.
Use this instead of schedule when you want the post to go out at the next open slot in the business's posting schedule, rather than at a fixed time you pick. The post is appended to the end of the queue and publishes automatically when its turn comes up — the same behavior as the "Add to queue" button in the app. If the business has no queue yet, a default daily schedule is created for it. To queue several posts, use schedule_posts with the ids in order: separate calls sent at once can't keep an order.
A post that already carries a future date (created with scheduled_publish_time while NEW) keeps it: it is scheduled AT that date, comes back with scheduled_publish_time set and queue null.
A post whose caption names a day (copy_date, e.g. National Day) never goes into a slot after that day: it is scheduled ON the day instead (warning SCHEDULED_ON_COPY_DATE, quote its time), or, when that day's time has passed, refused with 409 COPY_DATE_BEFORE_NEXT_SLOT.
The post must not already be published. Otherwise, on success the post comes back with status = SCHEDULED, scheduled_publish_time = null, and a populated queue object showing its position in line and estimated publish time. Poll GET /api/businesses/{business_id}/posts/{post_id} or GET /api/businesses/{business_id}/queue to confirm.
Errors: 400 POST_ALREADY_PUBLISHED: The post is already live, so it can't be queued. Duplicate it and queue the copy. Carries published_at. 401 authentication_required: API key or token is missing, invalid, or revoked. 403 permission_denied: Your plan does not include API access, or this business is not in your org. 404 resource_not_found: No post with that ID exists, or it is not in this business. 409 CAPTION_HAS_PLACEHOLDER: The caption still has an unfilled [[placeholder]] (a fact only the owner knows). The post is NOT queued and is unchanged. Fill it in with update_post, then queue it again. 409 NO_CONNECTED_SOCIALS: No connected account can publish this post (none connected, all need a reconnect, or none can take this content). The post is NOT queued and is unchanged, and no queue is created. Follow recovery_hint (usually: call connect_social), then queue it again. 409 COPY_DATE_BEFORE_NEXT_SLOT: The caption names a day (copy_date), the next queue slot (next_slot_local) is after it, and that day's posting time has passed. The post is NOT queued and is unchanged. Ask the user: publish_post_now, schedule_post at a time on or before the day, or queue again with ignore_copy_date=true. 429 rate_limit_exceeded: You sent too many requests this minute.
On success, publish_readiness lists the platforms the post will publish to and any connected account that won't get it, with the reason.
Request
- Base URL: https://api.mymarky.ai
- URL: https://api.mymarky.ai/api/businesses/{business_id}/posts/{post_id}/queue
- Auth: HTTP bearer
Path parameters
A UUID identifier.
A UUID identifier.
Query parameters
Queue it even though the slot is after the day its caption names (COPY_DATE_BEFORE_NEXT_SLOT). Only when the user said so.
Headers
Opt into a dated API version. Omit to stay on the floor (2026-04-08) forever — unpinned clients never break. Pin to a newer date (e.g. 2026-08-06) to receive the newest response shapes. Unknown values fall back to the floor. See https://docs.mymarky.ai for the versioning model.
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.