Publishing

Publish organic content to a connected Facebook Page or Instagram professional account. All publishing endpoints need the whatsapp:send scope, and none is metered — Meta does not charge for organic publishing.

No account id goes in the path. The Page or Instagram account is resolved from your workspace: its only connected account, or the one marked default. Pass ?account= (a CallMissed id or Meta's page_id / ig_user_id) to publish as a specific account — see how an account is chosen.

Media you publish must be at a publicly reachable URL: Meta fetches the file from its own servers, so a signed or expiring link that Meta cannot read fails as a 422. The public image URL returned by the Post Studio is exactly this shape.

Facebook: publish a post

POST /api/v1/facebook/posts

A text post, a link post, or a scheduled version of either. Supply message, link, or both — a body with neither is a 422.

curl -X POST https://api.callmissed.com/api/v1/facebook/posts \
  -H "Authorization: Bearer cm_your_key" \
  -H "Content-Type: application/json" \
  -d '{ "message": "Winter service special is on now.", "link": "https://example.com/book" }'

{ "id": "102938475610293_890123456789012", "post_id": null, "video_id": null }

Facebook: publish a photo or multi-photo post

POST /api/v1/facebook/photos

Supply url for a single photo, or urls for a multi-photo post (2–30). A single-URL urls list falls through to the single-photo path.

The 30-URL cap is CallMissed's own bound (each URL is an upload call), not Meta's. The response carries both the photo id and the resulting feed post_id.

{ "id": "10160000000000000", "post_id": "102938475610293_890123456789012" }

Facebook: publish a reel

POST /api/v1/facebook/reels

Publish a video reel from a publicly reachable video_url.

Instagram: publish a post

POST /api/v1/instagram/posts

One endpoint for every Instagram post shape. The type field picks it:

Caption length (≤ 2,200) and carousel size (2–10) are validated before any upstream call, so a bad body fails fast without leaving orphaned containers. A reel cannot be a carousel child (use a video child instead). A story takes no caption.

# A 3-image carousel
curl -X POST https://api.callmissed.com/api/v1/instagram/posts \
  -H "Authorization: Bearer cm_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "carousel",
    "caption": "Three from this week'"'"'s firing.",
    "items": [
      { "image_url": "https://media.callmissed.com/a.jpg", "alt_text": "A speckled mug" },
      { "image_url": "https://media.callmissed.com/b.jpg" },
      { "image_url": "https://media.callmissed.com/c.jpg" }
    ]
  }'

The two-step finish for a slow Instagram post

Instagram publishing is a multi-step upstream flow: a container is created, Meta processes the media, then the container is published. This endpoint waits a short budget (about 27 seconds) for that to finish. If the media is still processing when the budget runs out, it returns the container_id with status IN_PROGRESS instead of hanging — do not re-post (that risks a duplicate). Finish it with the two routes below.

{ "media_id": "17895695668004550", "container_id": "17889455560051444", "status": "PUBLISHED" }

Check a container's status — GET /api/v1/instagram/posts/{container_id}

Poll this until the status is FINISHED, then publish. A container expires 24 hours after creation.

Publish a finished container — POST /api/v1/instagram/posts/{container_id}/publish

Publishes a container whose media has finished processing, returning the live media_id.

Both take the same optional ?account= hint. Use the same account you created the container with — a container belongs to the account that made it, so resolving to a different one fails upstream.

Instagram: check the publishing quota

GET /api/v1/instagram/publishing_limit

Instagram caps how many posts an account can publish in a rolling 24-hour window. Read the live quota rather than assuming a number (Meta's own docs quote different limits on different pages). A carousel counts as one post against the quota. Needs whatsapp:send, like the publishing calls it protects.

{ "quota_usage": 12, "config": { "quota_total": 100 } }

Scheduling windows at a glance

A Facebook 504 on publish is ambiguous — the post may or may not have gone live. Check the Page before retrying; the API never auto-retries a publish.

The legacy POST /api/v1/facebook/{page_uuid}/posts form of every endpoint on this page still works — see legacy paths.