account_ids · video_url · captionInstagram Reels for AI agents
Your agent plans the Reels. Postdom holds the schedule.
Postdom schedules finished videos for connected professional accounts at exact UTC times. Publication, failure, and available measurements return as machine-readable evidence.
Meta limits API publishing to professional accounts. A human completes authorization and keeps control of policy, approvals, exceptions, and pause.
publish_atnot a Postdom wire statepublic_url: string | nullAccount eligibility
Start with the right account.
The API path begins with Meta's professional-account boundary and a human authorization handoff. The agent receives account state, never a password.
- 01
Professional account
Meta's API publishing path is for eligible professional accounts. Personal-account support is not claimed.
- 02
Human authorization
A human completes the provider authorization screen. The agent never receives the Instagram password.
- 03
Connected account
Postdom records the destination and current connection state inside the workspace.
- 04
Exact account ID
The agent reads list_accounts and uses the returned identifier instead of inventing a target.
Current provider requirements can change. Confirm the connected account state and current destination reference before execution.
Provider lifecycle
A container is not a Reel.
Meta creates and processes a media container before final publication. Postdom does not label an earlier request or acceptance as published.
Read the provider boundary- 01Underlying Meta mechanic
Container created
Meta receives the finished media as a Reel publishing container.
container creation - 02Underlying Meta mechanic
Media processed
Container readiness is provider work, not proof that the Reel is live.
container processing
sent → published | failedPostdom exposes the destination outcome, not Meta's internal container stages. public_url is nullable even on a terminal response.
Schedule safety
The caller can sleep.
Postdom keeps the UTC schedule after the agent disconnects. A slot that starts more than 15 minutes late stops instead of publishing late.
See durable scheduling2026-09-03T09:00:00Zsent → published | failedAfter provider handoff, the destination returns an exact wire outcome.
missed_scheduleHuman chooses publish now, reschedule, or cancel
Reels evidence
Use the signal Instagram provides.
The modeled availability map separates exposed fields from unverified or merely derivable ones. A missing value never becomes a zero by convenience.
availableavailableavailableavailableavailableunverifiedestimableestimableestimableNative boundary
Instagram keeps its native tools.
Postdom supplies the configured Reel type and AI disclosure. It does not promise every in-app creative, tagging, audio, or feed-placement control.
Current adapter: contentType = reel · isAiGenerated = true
- Reel content type
- AI-generated disclosure
- Finished video and caption
- Immediate or exact UTC execution
- Music, effects, or stickers
- Product or collaborator tags
- An Instagram visibility input
- Share-to-feed behavior
- Every current provider limit
Operating models
Choose who operates the workflow.
The difference is not whether each option can reach Instagram. It is who owns timing, authority, provider state, and the evidence handback.
HumanNative creative and account controls
No Postdom agent contract or evidence handback
HumanVisual calendar and team workflow
Designed around a person operating the dashboard
DeveloperDirect provider primitives
You own authorization, durable timing, container state, and normalization
AI agentDurable schedule, human authority, outcomes, and evidence
Does not replace Instagram's native creative surface
For AI agents
Follow the connected contract.
Read workspace state and live schemas before planning. Use exact account IDs, UTC times, video URLs, plan IDs, and returned states without renaming them.
Never guess account eligibility, platform settings, a timezone, provider success, or a missing measurement.- 01
get_workspace_statusRead setup, policy, brief, and connection gates.
- 02
connect_account · list_accountsStart the human authorization handoff when needed, then use the exact connected Instagram account ID.
- 03
get_brief · get_digestRead current brand guidance and the latest completed week before planning.
- 04
submit_plan · get_planUse plan review when the account's authority requires it.
- 05
publish_videoSubmit one finished video URL, the account ID, caption, intent, and optional UTC time.
- 06
get_publish · get_performanceRead final destination state and evidence without inventing missing values.
Instagram Reels FAQ
Reels questions
Can an AI agent publish Instagram Reels automatically?01
Yes, after an eligible professional account is connected and the human-set authority permits the request. Postdom holds an exact UTC schedule and returns the final destination outcome to the agent.
Which Instagram accounts can use API publishing?02
Meta's API publishing path is for eligible professional accounts. A human completes provider authorization, and Postdom does not claim support for personal accounts.
When is an Instagram Reel actually published?03
A created or processing media container is not a published Reel. Postdom treats the final provider-confirmed destination outcome as publication evidence.
What happens when a scheduled Reel cannot start on time?04
A run that starts more than 15 minutes after its slot becomes missed_schedule instead of publishing late. A human then chooses publish now, reschedule, or cancel.
Can Postdom add Instagram music, effects, stickers, or collaborator tags?05
Those native controls are not part of Postdom's current promise. Use Instagram's own creative surface when a Reel depends on music, effects, stickers, product tags, or collaborator tags.
Does Postdom control whether a Reel appears in the Instagram feed?06
Postdom's configured Instagram adapter supplies Reel content type and AI disclosure but no visibility field. Do not infer share-to-feed behavior from the publish request.
Which Instagram Reels measurements can an agent read?07
The current model marks views, likes, comments, shares, and watch time available. Saves remain unverified; average watch, completion, and follower change are estimable, not guaranteed values.
How does an agent schedule a Reel with Postdom?08
The agent reads workspace status and account IDs, follows the required authority path, supplies finished media and an optional RFC 3339 UTC publish_at value, then reads the post and performance evidence.
Instagram Reels reference
The facts behind the workflow above, each with its source and the date it was checked.
- Does Instagram have an API?
The Reels publishing path, and what each access level allows.
- Instagram Reels caption limits
The documented caption length for the publishing API.
- Instagram Reels metrics availability
Which insights fields Postdom can return, and which stay null.
- Instagram Reels size and dimensions
Every dimension fact with its classification and source.
Schedule the week
Let the agent plan. Keep every Reel accountable.
Connect an eligible account, choose the authority boundary, and give the schedule a durable path to publication evidence.