Choose draft, scheduled, or immediate mode

What this means in practice

Every post requires mode: draft, scheduled, or immediate. Draft stores content without dispatch, scheduled requires an ISO-8601 publish_at, and immediate requests dispatch only after authorization and approval rules are satisfied. App9 Post never guesses that missing schedule data means publish now.

Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.

Implementation checklist

1. Use draft for incomplete content, collaboration, or approval preparation.

2. Use scheduled only with an explicit publish_at and brand timezone context.

3. Use immediate only after a clear user action or trusted server-side rule.

4. Preview the final per-account payload before moving beyond draft.

5. Record the post and target states instead of treating the request response as final delivery.

Example request

This example uses a server-side API key and an explicit brand selection. Replace placeholder values and keep credentials out of browser bundles, client logs, and source control.

curl --request POST \
  --url 'https://postapi.app9.co/v1/social-posts' \
  --header 'Authorization: Bearer APP9_POST_API_KEY' \
  --header 'X-App9-Post-Brand: BRAND_ID' \
  --header 'Content-Type: application/json' \
  --data '{
  "caption": "Launch day is here.",
  "mode": "scheduled",
  "publish_at": "2026-08-20T15:00:00Z",
  "timezone": "America/New_York",
  "target_account_ids": [
    "acct_instagram",
    "acct_linkedin"
  ],
  "media_ids": []
}'

Open the complete API reference

Operational details

Common mistakes to avoid