Niches · Social media posting APIs
Schedule a batch of posts on a calendar
One company's docs show a full fit.
What counts as done
Every post is stored as scheduled at the stated instant with an explicit timezone, listable afterwards with its state.
Measured, for our own tests: each publishes within 5 minutes of its time. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: schedule these ten posts over the next two weeks
, plan and queue a month of content
, put this in the next free slot
, post this every Tuesday at 9
Does the job 1
The docs show it meets the test above, and nothing we read says otherwise.
Does the job, with a limit 14
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Ayrshare API + MCP C Neverminds Solution LLC | scheduleDate takes a UTC ISO time and returns status scheduled, history lists posts with state, but no publish-latency figure is given and errors at publish time arrive only by webhook or /history. source |
| Blotato E Blotato Inc. | scheduledTime is UTC ISO 8601 and echoed back, scheduled posts are listed and editable by id, but there is no timezone field and no publish-latency figure. source |
| Buffer API + MCP B Buffer, Inc. | customScheduled takes dueAt in ISO 8601 UTC, posts are listed by status and editable by id; no named timezone is taken and no publish-latency figure is given. source |
| bundle.social C BUNDLE SP. Z O.O. | postDate in UTC ISO with SCHEDULED, RETRYING, ERROR and REVIEW states listable and retryable; no named timezone is taken, and per-account daily caps and the YouTube organisation cap can fail a post at publish time. source |
| Zernio (formerly Late) API + MCP BB ZERNIO SOFTWARE SL | scheduledFor with an offset or an IANA timezone, listable states, editable by PUT; but TikTok posts beyond the daily cap are held and published later, so the 5-minute bar is not guaranteed. source |
| Metricool API + MCP F METRICOOL SOFTWARE, S.L. | publicationDate takes a dateTime and an IANA timezone, and posts are listed between dates, fetched and edited by id; publish latency and per-network outcome are not documented, and Free caps at 20 scheduled posts. source |
| Mixpost API + MCP C INOVECTOR DIGITAL S.R.L. | date and time are read in a given timezone and stored as UTC, posts are listable; an open issue reports the API rejecting valid future UTC dates as past and add-to-queue ignoring custom dates. source |
| OneUp API + MCP F OneUp, Inc. | Posts are listable by scheduled, published, failed and draft state and editable, but scheduled_date_time is YYYY-MM-DD HH:MM with no timezone field, so the account's timezone governs. source |
| Post Bridge API + MCP E Post Bridge | scheduled_at or use_queue, posts listed and patched by id, and per-account results; the schema gives no timezone rule beyond a date-time, and publish latency is not stated. source |
| Postiz API + MCP D Gitroom Limited | date is UTC ISO, posts are listed and can move between draft and queue; an open issue shows Cloud accepting a TikTok Direct Post and failing at publish time on the shared app's daily active-user cap. source |
| Publer API + MCP E Kalemi Code | scheduled_at takes ISO 8601 with Z or an offset, posts list by state including scheduled_reauth and failed, and reschedule echoes the time; no publish-latency figure, and a one-minute gap per account is required. source |
| Repostit F Repostit LLC | A Brief is scheduled at an exact future time with a timezone given in the request and all destinations share it; no tool schema shows the stored time being echoed or the publish latency. source |
| SocialCannon C Tiny Red Pixel Ltd | scheduledAt is ISO 8601 within a 30-day window, posts list by status with a cursor and the workspace has a configured timezone; no publish-latency figure, and accounts under restriction hold posts as awaiting_account. source |
| Upload-Post API + MCP D TONVI TECH SL | scheduled_date with an IANA timezone, scheduled posts listed and patched by job_id; but an open MCP issue shows youtubePublishAt dropped, leaving videos private instead of scheduled. source |
Doesn't do this job 4
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Sprout Social API C Sprout Social, Inc. | Posts can be created only as drafts, even with delivery details, so nothing is scheduled to publish without a person in Sprout. source |
| TwitterAPI.io MCP D Prism Digital, LLC | No scheduling; the MCP is read-only. source |
| X MCP C X Corp. | No scheduling tools; Articles can be drafted and published but not scheduled. source |
| Xpoz MCP E XPOZ | No scheduling or posting tools. source |
1 listings in the category were added after this reading and aren't marked yet.
What stops agents finishing
- a shared vendor app hits a network's daily cap at publish time, after the post was accepted
- the scheduling endpoint rejects valid future times
- a connection's token expires between scheduling and publishing
Around it
Before: llm.draft-copy, spreadsheets.read-rows. After: social-media.confirm-delivery, social-media.performance-report.
Where this comes from
Weight 11 of 100 in Social media posting APIs: 6 of 57 use-case tags; scheduling is in every vendor's pitch but accounts mostly report it through failures at publish time
The same as data: /api/v1/use-cases/social-media.schedule-calendar.json, or the MCP tool get_use_case with id social-media.schedule-calendar. Other jobs in this category: /api/v1/niches?category=social-media.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.