XreplyAIDevelopers
API ReferencePublishing

Get the next open posting slot

Requires scope: `posts:read`. Returns the earliest open schedule slot for the post's (or supplied) accounts.

GET
/posts/{post_id}/publishes/next_slot

Authorization

ApiKey
AuthorizationBearer <token>

A personal API key created in the dashboard (Starter, Pro, and Team plans).

In: header

Path Parameters

post_id*integer

Query Parameters

social_account_id?integer
social_account_ids?array<integer>

Response Body

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/posts/0/publishes/next_slot"
{  "scheduled_at": "2026-07-14T15:00:00Z"}

Publish a post POST

Requires scope: `publish:write`. Publishes an existing post. Without `scheduled_at` or `use_next_slot` the post is sent immediately. Pass `scheduled_at` to schedule it, or `use_next_slot: true` to queue it into the next open posting-schedule slot. Target accounts default to those already attached to the post; override with `social_account_id(s)`.

Upload media (Facebook, Instagram, Pinterest, TikTok, Threads, Discord, Slack, Telegram, Tumblr, X, Mastodon, Bluesky) POST

Requires scope: `publish:write`. Uploads base64-encoded media to storage and returns an `r2_key` to reference from a post's `post_contents` metadata. `platform` selects the size/type limits. For X, Mastodon, and Bluesky the image is minted into the platform's native handle at publish time under each targeted account, so the same `r2_key` works correctly even when a post targets more than one account on that platform.