Publishing
POST /v1/posts- Task
- Publish now, schedule, or save a draft, with per-platform overrides.
- Input
- Content, media URLs, target accountIds, scheduledFor and timezone.
- Output
- A post id, then per-target status events such as published or failed.
Spotlight by TrackerToolsNot affiliated with ZernioDisclosure
Zernio is a unified API for social publishing, messaging and ads. Developers, SaaS teams, agencies and AI-agent builders connect accounts once, then schedule posts, answer DMs and comments, run phone numbers and manage campaigns with one request shape, and get status back by webhook. Use it through REST, official SDKs, a hosted MCP server or a CLI.
Takes you to Zernio’s site. Its pricing page lists the first two connected accounts as free, no card required. Reference: Zernio docs.
POST /v1/posts content: "Launch day" mediaItems: [launch-reel.mp4] platforms: instagram · x · youtube scheduledFor: 2027-01-15T14:30 timezone: Europe/Madrid
posts_create instead.Zernio’s docs describe one API covering publishing, inboxes, calls and ads. Here is what goes in and what comes back for each area. Feature depth differs by platform, so each area links to the docs that define it.
ad.status_changed events.message.received.Social media publishing & scheduling API
Docs: use the upload in a post within 7 days, or the create call returns 400.
Request a presigned URL, upload the file, and pass the returned URL in mediaItems. Zernio accepts image, video, GIF and document types. Write the copy yourself or with your own tools; Zernio delivers it.
Each account owner authorizes Zernio once through a connect URL. Your app lists connected accounts and targets them by id. For platforms that need media, like Instagram or YouTube, a text-only post is not an option.
Send scheduledFor with a timezone, publish now, or save a draft. The response gives you a post id and the post enters the scheduled state.
Subscribe to webhooks instead of polling. Per-target events tell you which platform published and which failed; post.partial means some succeeded and some did not. Show the error, fix it, retry.
Publishing is documented for the platforms below. Inbox and analytics coverage varies, so we link the docs matrix rather than tick boxes we could not confirm per platform.
| Platform | Publish | Comments / DM | Analytics | Note |
|---|---|---|---|---|
| ✓ Documented | Check docs | Check docs | Needs image or video | |
| ✓ Documented | Check docs | Check docs | Video required | |
| ✓ Documented | Check docs | Check docs | Video required | |
| ✓ Documented | Check docs | Check docs | X API costs passed through at X’s rates |
Also documented for publishing: LinkedIn, Facebook, Threads, Bluesky, Pinterest. Zernio’s docs say POST /v1/posts reaches 16 platforms; see the full list.
Upload once, target accounts by id, schedule, and read per-target status from webhooks. That is the publishing loop you just scrolled through.
Explore Zernio for publishingAdvertising API
Zernio lists Meta, LinkedIn, Pinterest, TikTok, Google, X, Reddit, Microsoft and OpenAI ads. The API sends your settings; each network still reviews ads and decides delivery. Zernio does not choose budgets or promise results.
Metrics come from the ad network through Zernio. Which fields exist depends on the network.
Messaging API · WhatsApp, DMs, SMS
Inbound messages reach your backend as events; your app or agent decides the reply and sends it through the same API. Each channel below is a separate conversation; we don’t assume threads sync across channels.
Buy or port in a phone number, then turn on calls, SMS and WhatsApp on it. Number availability and fees vary by country; see the official number pricing.
Telegram, Discord, Slack, iMessage, RCS, plus comments and reviews on social accounts. Check each platform page for what is supported.
Inbound messages and ad status changes reach your backend as events. Your app or agent decides what to do; Zernio carries the reply or the change.
Explore ZernioAPI · MCP · CLI
REST and SDK calls use an API key as a bearer token. The hosted MCP server uses OAuth in clients that support it; autonomous agents with nobody at a browser send an API key instead.
import Zernio from '@zernio/node';
const zernio = new Zernio(); // reads ZERNIO_API_KEY
const { data } = await zernio.posts.createPost({
body: {
content: 'Launch day.',
mediaItems: [{ url: 'https://cdn.example.com/launch.jpg' }],
platforms: [
{ platform: 'linkedin', accountId: 'YOUR_ACCOUNT_ID' },
],
scheduledFor: '2027-01-15T14:30:00',
timezone: 'Europe/Madrid',
},
});
console.log(data.post._id);
curl https://zernio.com/api/v1/accounts \ -H "Authorization: Bearer $ZERNIO_API_KEY"
Documentation-checked example
Syntax matched to Zernio’s published examples; not run against a live account. Placeholders only, no real keys.
claude mcp add --transport http zernio https://mcp.zernio.com/mcp claude /mcp
The client opens a Zernio sign-in. No key to paste. You can revoke the client from your dashboard.
The assistant calls accounts_list, then posts_create. Without publish_now, the tool schedules the post (60 minutes ahead by default).
Zernio’s docs describe a CLI that lets you log in and schedule a post from the terminal with one command. We have not reproduced the commands here because we didn’t verify them; use the official reference.
Open CLI docs →| REST API / SDK | Hosted MCP server | |
|---|---|---|
| Who calls it | Code you write and deploy | An AI assistant or agent (Claude, ChatGPT, Codex, Cursor and other MCP clients) |
| Auth | API key as a bearer token | OAuth sign-in where the client supports it; API key for autonomous agents |
| Good for | Product features, background jobs, multi-tenant apps | Tasks you ask for in chat, agent workflows, quick checks |
| Setup | Install an SDK or call HTTPS directly | Nothing to install; add the server URL |
Source: Zernio MCP docs.
Pick the REST API for product code or the hosted MCP server for assistants. Signing up opens the dashboard where API keys and account connections are managed.
Build with ZernioSmaller areas than the three above, but useful when your workflow already lives there.
post.failed, which teams often route to a Slack or email alert.Workflow: one profile per client, each client authorizes their accounts, your tool schedules and reports across them.
Why: per-account pricing scales with clients instead of seats.
Workflow: add a “post to social” or inbox feature for your own users, and route webhooks back to the right customer by accountId.
Why: one integration instead of one per platform.
Workflow: your model or video tool produces the content; the agent uses MCP or the API to schedule it and check status.
Why: the hosted MCP server needs no install.
Start with the REST API or an SDK: create a profile per customer, send them a connect URL, then schedule posts and route webhooks back by accountId. See the API example.
No plans or seats. Summarised from zernio.com/pricing. Prices can change; confirm on Zernio before you buy.
Monthly rate per account, by tier
| Accounts 1–2 | Free |
|---|---|
| Accounts 3–10 | $6 |
| Accounts 11–100 | $3 |
| Accounts 101+ | $1 |
Zernio’s example: 10 accounts = 2 free + 8 × $6 = $48/month. First 2 accounts need no credit card.
A number’s rental fee isn’t the total cost of the calls and messages on it.
Custom terms, offered past 2,000 accounts. Adds SAML SSO, SCIM, MFA, audit logs, RBAC and a shared Slack channel with engineering.
Enterprise details on zernio.comZernio’s Trust Center lists GDPR and offers its SOC 2 Type II report on request with a work email. The DPA and subprocessor list are public.
Trust Center →Two connected accounts are free to start; from the third, accounts bill per tier, and messages, ads, numbers and calls are metered as listed above.
Get started with ZernioAn API for publishing posts, running inboxes, placing calls and managing ads across the platforms it connects to, with SDKs, a hosted MCP server and a CLI on top. Your app or agent sends requests; Zernio talks to each platform and reports status back.
The REST API and SDKs are for code you write, authenticated with an API key. The MCP server at mcp.zernio.com exposes the same endpoints as tools for assistants like Claude, ChatGPT, Codex or Cursor; clients with OAuth sign in through the browser, autonomous agents send an API key.
Zernio’s docs list 38 platforms overall, and say one post request publishes to 16 of them. Support for DMs, comments, analytics and ads differs per platform; each platform page in the docs lists its endpoints and events.
Each account owner authorizes Zernio through a connect URL. The platform’s own rules on account type, content, media and ads still apply, and Zernio can’t bypass platform review or guarantee reach.
You get events per target: post.platform.failed for the platform that failed and post.partial or post.failed for the whole post. Fix the cause, such as the media or a disconnected account, then use the retry endpoint.
Two accounts are free, then $6, $3 or $1 per account per month depending on tier. Messages past the free allowance, ads, X API usage, numbers and calls are billed as usage. See pricing.
Developers adding social, messaging or ads features to a product, agencies running many client accounts, and teams building AI agents or content tools that need to deliver what they make.
Sign up free, create an API key, and follow the quickstart: create a profile, connect an account, schedule a post. If you work in an AI assistant, add the MCP server instead.
Per Zernio’s pricing page, the first two connected accounts are free with no card, so you can schedule a real post and watch the webhooks come back. Reference: Zernio docs.
We read Zernio’s public site, docs, MCP docs, pricing page and Trust Center. We have not run Zernio against a live account: code samples are matched to the docs, and the demos on this page are illustrations with sample data.
Pricing, platform coverage and features change. Treat Zernio’s pages as the source of truth.