✦ Partner API
How to schedule social media posts by API with a future ISO datetime
Quick answer
Schedule a multi-network post by sending MultiPost a server-side publish request with a valid future scheduledAt ISO 8601 value, supported content, and exact platform-and-handle targets. Check plan and quota first, preserve the user’s timezone in your UI, and store each per-target scheduled result and job ID.
How do you schedule one social post to several networks with a future ISO datetime?
Send a server-side Partner API publish request with a valid futurescheduledAt ISO 8601 value and one target per connected account. MultiPost prepares the media immediately, stores the job and returns a scheduled result for each accepted platform and handle.
Build the timestamp from the user's chosen local time and convert it to an unambiguous ISO value before submission. Keep the original timezone in your own UI so a human can understand what will happen without reverse engineering a UTC timestamp.
What is the fast way to enable API scheduling with MultiPost?
The fast path is to have the user connect their social accounts, create a personal API token in Settings and call/api/v1/me before scheduling. Only continue whencanPublish is true and the account has enough remaining quota for the selected targets.
Partner API publishing requires Pro or Agency. Use MultiPost plans and billing as the upgrade destination instead of attempting to bypass the server-side plan and quota checks.
What should the scheduled publish payload contain?
It should contain a supported type, shared caption, at least one valid target, the required media field and the future ISO datetime. Add the exact handle returned by /api/v1/accounts when a user has more than one account on the same platform.
A target may also carry its own caption. This lets the request preserve one factual source while adapting the opening or call to action for each network. The guide to adding social publishing without storing provider OAuth tokens covers the tenant boundary around the token.
How should your SaaS interpret the scheduling response?
Interpret every target result separately and persist its platform, handle, status and scheduled job ID. A request can accept valid targets while rejecting one whose date is outside the scheduling window, so the top-level result is not enough for a useful customer message.
Treat status: scheduled as queue acceptance, not proof of a public post. After the due time, use your operational record and the user's MultiPost notifications or publication history to investigate an exception.
How does MultiPost keep scheduled API publishing manageable?
MultiPost keeps the workflow manageable by owning media preparation, account resolution, provider token refresh and the due-time publish job. Your SaaS remains responsible for the customer's local-time choice, payload validation and clear per-target status reporting.
Frequently asked questions
Which field schedules a Partner API publish request?
Provide scheduledAt as a valid future ISO 8601 datetime in the publish request body.
Can each target have its own caption?
Yes. Include caption on an individual target to override the shared caption for that account.
Which plans can schedule through the API?
Partner API publishing and scheduling require Pro or Agency on the linked MultiPost account.
Does a scheduled response prove the post is already public?
No. It confirms queue acceptance; the network publish happens when the stored job becomes due.
✦ Start free
Give your scheduler one multi-network queue.
MultiPost prepares media, resolves connected accounts and runs the due publish behind one Partner API request.