Scheduling Instagram posts through the API
Instagram posts are scheduled through the API by holding each one in a queue and publishing it at the chosen time, since Meta's media_publish call takes no date. easyCoexistence's publish_instagram_post takes scheduled_at, an ISO 8601 time with a timezone from 1 minute to 90 days ahead, and its queue publishes the photo, carousel, Reel or Story then, within the limit of 100 API posts in 24 hours.
The only parameter media_publish takes besides the token, so a post goes live when that call is made.
How long a media container lasts unpublished, too short to create one days before a scheduled time.
API-published posts per account in a moving 24 hours, counted when each container is published.
Where the media must be at the time of the publishing attempt, since Meta fetches the file itself.
How does scheduling work through Instagram's API?
By holding the post until its time. Publishing takes two calls: POST /<IG_ID>/media creates a container from the media, and POST /<IG_ID>/media_publish with that container's ID puts the post live. Neither call takes a publish date or time, so a scheduled post is one an app keeps in its own queue and publishes at the chosen moment.
How do you schedule a post through MCP?
Ask for it in plain words. With the easyCoexistence connector added to Claude or ChatGPT and the Instagram account connected, a request such as "Schedule this carousel for Friday at 9am with this caption" is enough: the assistant calls publish_instagram_post with scheduled_at, an ISO 8601 date and time with a timezone, from 1 minute to 90 days ahead. easyCoexistence copies the media when the post is scheduled, holds the post in its queue and publishes it then. Photos, carousels of 2 to 10 items, Reels and Stories can be scheduled, with the media at a public HTTPS URL and images as JPEG.
What has to be true when the post goes out?
The same as for a post published straight away:
- The media is at a public URL Meta can fetch during the publishing attempt; easyCoexistence's queue serves its own copy, made when the post was scheduled.
- Images are JPEG: Instagram's API publishes no other image format, and extended JPEG formats such as MPO and JPS are refused.
- A video has finished processing: its container's
status_codemust read FINISHED beforemedia_publishsucceeds. - The account has room under its limit: 100 API-published posts in a moving 24 hours, with a carousel counting once.
Why can't the container be created in advance?
Because it expires. A media container that is not published within 24 hours reads EXPIRED and has to be created again, and an account can create 400 containers in a rolling 24 hours. A queue that holds posts for days or weeks keeps the media URL and caption, and creates the container close to the publishing time.
Do scheduled posts count toward the daily limit?
Yes, on the day they are published. Meta enforces the limit of 100 API-published posts in a moving 24 hours at the media_publish call, and recommends that apps letting people schedule posts in the future enforce it themselves as well. GET /<IG_ID>/content_publishing_limit reports quota_usage, the number of posts the account has published through the API in the last 24 hours.
Common mistakes
- Scheduling media from a link that does not open. easyCoexistence copies the file when the post is scheduled and refuses a web page, a missing file, the wrong type or one over 30 MB for an image or 1 GB for a video.
- Creating the container when the post is scheduled. Containers expire after 24 hours, so one made a week early is gone by the publishing time.
- Queueing PNG or HEIC images. Instagram's API publishes JPEG only, so convert them before scheduling.
- Scheduling more posts in a day than the limit allows. Meta refuses posts beyond 100 in a moving 24 hours when they publish; easyCoexistence tries again later and, if Meta still refuses, marks the post failed and emails the owner.
Instagram's API has no publish time of its own, so easyCoexistence keeps the queue: ask Claude, ChatGPT or your own AI agent to publish a photo, carousel, Reel or Story at a date and time, and easyCoexistence publishes it then through Meta's official API. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
What happens if a scheduled Instagram post fails?
If Meta refuses it over the daily limit, easyCoexistence tries again later; if Meta still refuses, or refuses it for any other reason, the post is marked failed and the owner is emailed.
Can I change a scheduled Instagram post?
Yes, until it goes out: update_scheduled_post changes the time or the caption, and cancel_scheduled_post removes it. To change the media, cancel the post and schedule it again.
Can Reels and Stories be scheduled?
Yes. Photos, carousels, Reels and Stories can all be scheduled, and each follows the same publishing rules as a post that goes out at once.
How far ahead can an Instagram post be scheduled?
From 1 minute to 90 days ahead with easyCoexistence, given in scheduled_at as an ISO 8601 date and time with a timezone.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on