Skip to content

Instagram Scheduling API

The Instagram Scheduling API helps developers, SaaS teams, agencies, automation builders, and AI products place feed posts, carousels, and Instagram Reels into a future publishing queue for a chosen local moment, without operating that queue themselves.

Schedule an Instagram Image Post Request
POST {{API_BASE_URL}}/v1/posts
x-access-key: YOUR_API_KEY
Content-Type: application/json

{
    "content": "A short example update.",
    "platforms": [
     {
         "platform": "instagram",
         "accountId": "ig_456"
      }
    ],
    "mediaItems": [
      {
        "type": "image",
        "url": "https://cdn.example.com/collection.jpg"
      }
    ],
    "scheduledFor": "2026-09-10T09:00:00",
    "timezone": "America/Los_Angeles"
}
Illustrative request
Example line 1

POST {{API_BASE_URL}}/v1/posts

Illustrative request
Example line 2

x-access-key: YOUR_API_KEY

Illustrative request
Example line 3

Content-Type: application/json

A creation request carries scheduledFor and timezone, the response returns a postId marked scheduled, and the same API surface then supports listing, moving, or cancelling the queued item.

Add scheduling in three steps

A product, agency workflow, automation, or AI system can delegate queue ownership to this API instead of running its own timer and publisher. Setup follows three stages: obtain an API key, connect once for publishing, scheduling, analytics, comments, and messaging, and reuse connected accounts across major platforms rather than maintaining a separate integration for each network. Developer teams can call REST endpoints or typed SDKs, no-code builders can trigger the workflow from tools such as Zapier, Make, and n8n, and agent builders can expose the same operations through hosted MCP or tool-calling schemas where available.

Create a scheduled post with POST /v1/posts

Deferred delivery starts with POST /v1/posts, supplying the Instagram account, the media, and scheduledFor. Choosing scheduledFor instead of publishNow is what separates a queued post from an immediate one. The request example titled Schedule an Instagram Image Post Request gives the complete image-post payload, while Scheduled Instagram Post Response shows the 202 reply carrying status scheduled, the generated postId, and the resolved UTC moment. Keep that postId safe, because later queue operations address the item through it.

Timezone handling with scheduledFor and timezone

Express the desired moment as an ISO 8601 datetime in scheduledFor and name its zone in timezone, for example America/Los_Angeles, when the target is local audience time. The reply converts that local moment into UTC and returns it as scheduledFor, which makes verification straightforward. Omitting timezone changes the interpretation to UTC, so include the field whenever local timing matters. Compare the returned UTC value against the intended local moment before depending on the queue for a campaign launch.

Formats, mediaItems, and cross-posting

Single images, carousels, and Instagram Reels share one scheduled-post shape, subject to Instagram media rules for each format. Inside mediaItems, each entry supplies a type and a url; inside platforms, each entry supplies platform and accountId for the connected Instagram account. A campaign spanning weeks can be built by issuing one creation request per item, each with its own scheduledFor. Compatible material can also target Instagram alongside Facebook, TikTok, LinkedIn, Twitter/X, YouTube, Threads, Pinterest, Bluesky, or Google Business in a single request, with different content or settings per platform where needed. Before submitting a batch, confirm every mediaItems url loads and matches the intended format. Related scheduling pages cover Twitter/X, Facebook, LinkedIn, TikTok, YouTube, Threads, Pinterest, Bluesky, and Google Business.

Manage the queue: list, reschedule, and cancel

Queued work is visible through GET /v1/posts/scheduled, where limit, offset, and sort order support a calendar view or an upcoming-post list. Changing the delivery moment uses PATCH /v1/posts/scheduled/{postId}, and withdrawing the item before delivery uses DELETE /v1/posts/scheduled/{postId}, after which it returns to draft. The example titled List, Reschedule, and Cancel Scheduled Posts gathers those three calls together. After a change or withdrawal, fetch the list again and confirm the postId has left its previous slot.

POST /v1/posts Request Field Map
FieldLocationType / exampleRequirednessPurpose
contentRequest bodystring: "A first look at our new collection."Shown in examplePost text
platformsRequest bodyarray of objectsShown in exampleTarget platforms and accounts
platforms[].platformRequest bodystring: "instagram"Shown in exampleSelects Instagram as the target
platforms[].accountIdRequest bodystring: "ig_456"Shown in exampleIdentifies the connected Instagram account
mediaItemsRequest bodyarray of objectsShown in exampleMedia to publish
mediaItems[].typeRequest bodystring: "image"Shown in exampleMedia item type
mediaItems[].urlRequest bodystring URLShown in exampleLocation of the media item
scheduledForRequest bodyISO 8601 datetime: "2026-09-10T09:00:00"Required for scheduling; use instead of publishNowFuture publishing time
timezoneRequest bodyIANA timezone: "America/Los_Angeles"Optional; omitted means UTCLocal timezone for scheduledFor
publishNowRequest bodyAlternative to scheduledForAlternative fieldImmediate publishing instead of scheduling

Field map derived from the captured image-post example and FAQ contract; types beyond the example are not asserted.

POST /v1/posts 202 Response Field Map
FieldLocationType / examplePurpose
successResponse bodyboolean: trueIndicates the scheduling request succeeded
statusResponse bodystring: "scheduled"Confirms the post is queued, not published
postIdResponse bodystring: "post_xyz789"Identifier for later PATCH, DELETE, and lookup
scheduledForResponse bodyUTC datetime: "2026-09-10T16:00:00.000Z"Resolved UTC publishing time
platforms[].platformResponse bodystring: "instagram"Per-platform result
platforms[].successResponse bodyboolean: truePer-platform scheduling result

Response shape from the captured 202 example.

Scheduled Queue Management Operations
OperationMethod and pathParameters / bodyEffect
List scheduled postsGET /v1/posts/scheduledlimit, offset, sort orderReturns a paginated list of scheduled content
Reschedule scheduled postPATCH /v1/posts/scheduled/{postId}postId path parameter; new date or timeMoves the queued post to a new time
Cancel scheduled postDELETE /v1/posts/scheduled/{postId}postId path parameterCancels before publication; cancelled post is moved back to draft

Paths preserved exactly from the captured FAQ contract; request-body fields for PATCH beyond rescheduling time are not specified in the evidence.

Validation and Retry Failure Matrix
Failure caseWhen it is detectedWhat happensCheck to perform
Invalid or unsupported Instagram mediaAt schedule time, when the post is createdPlatform and media are validated instead of waiting until delivery timeFix mediaItems and resubmit; do not leave invalid media in the queue
Instagram temporarily unavailable at delivery timeAt the scheduled publishing timeTemporary publishing failures are retried automaticallyConfirm the postId status after the scheduled time; no separate retry queue is needed
Wrong local timeImmediately, by comparing request and responsescheduledFor is resolved from timezone, or treated as UTC if timezone is omittedCompare the returned UTC scheduledFor with the intended local time

Behavior statements are from the captured FAQ; no executed test evidence was supplied.

Frequently asked questions

How do I schedule an Instagram post through the API?

Send a request to POST /v1/posts naming the Instagram account and its media, and choose scheduledFor for deferred delivery rather than publishNow for immediate delivery. Adding an IANA timezone interprets that moment in local terms; leaving it out means the value is read as UTC.

What Instagram content can I schedule with the Instagram Scheduling API?

Feed posts, carousels, and Instagram Reels are the formats described for this flow. Media and any platform-specific options follow the rules already defined for those formats.

Do I need an Instagram Business account to schedule posts?

A professional Business or Creator account is needed for feed posts and Reels. Connection happens through Instagram Login, and linking to a Facebook Page is not part of that requirement.

Do I need my own Meta developer app or App Review?

No separate Meta developer app or App Review is required on your side. Authentication and the Meta connection are handled through the hosted connection flow.

Can I edit and reschedule or cancel an Instagram post?

Both operations are available before delivery. PATCH /v1/posts/scheduled/{postId} changes the date or time, while DELETE /v1/posts/scheduled/{postId} cancels the queued item and returns it to draft.

Can I list all upcoming Instagram posts?

Yes. GET /v1/posts/scheduled returns scheduled content page by page. The limit, offset, and sort order parameters let you assemble a calendar or a list of upcoming items.

What happens if my Instagram media is invalid?

Checks run when the post is created, not at delivery. Unsupported formats or bad media are therefore flagged early, rather than discovered after the item has waited in the queue.

What happens if Instagram is temporarily unavailable when the post is due?

Brief delivery problems are retried by the scheduling infrastructure itself. You do not need to build a second retry queue around the due time.

Who is the Instagram Scheduling API for?

Developers, SaaS teams, agencies, automation builders, and AI products that need programmatic scheduling are the intended users.

Scheduled Instagram Post Response
202

{
    "success": true,
    "status": "scheduled",
    "postId": "post_xyz789",
    "scheduledFor": "2026-09-10T16:00:00.000Z",
    "platforms": [
      {
        "platform": "instagram",
        "success": true
      }
    ]
}
List, Reschedule, and Cancel Scheduled Posts
GET {{API_BASE_URL}}/v1/posts/scheduled?limit=20&offset=0
PATCH {{API_BASE_URL}}/v1/posts/scheduled/post_xyz789
DELETE {{API_BASE_URL}}/v1/posts/scheduled/post_xyz789