Zernio Features and How It Works | Unified API for Social Media Posts and DMs

Hi, I’m Hoda, a Zernio partner.

When you post the same content to multiple social networks, it’s easy to lose time on small tasks: format it for X, rewrite it for LinkedIn, then use yet another format for Instagram. For developers who want to add posting features to AI agents or SaaS products, differences in authentication and API specifications across platforms can become heavy work.

Zernio (formerly getlate.dev), introduced in this article, is a service that handles integrations with many services in one place. I previously introduced it as a social media posting API, but it has since expanded to advertising, messaging such as WhatsApp, SMS, and iMessage, and even calls. It is now a marketing infrastructure for apps and AI agents.

This article covers its basic features and how it works, what has expanded since its days as a social media posting API, and who it is best suited for.

What Is Zernio?

Zernio is an API service designed for developers and AI agents. It brings together the features needed for marketing and customer communication.

In addition to posting to Instagram, TikTok, X (Twitter), LinkedIn, Facebook, YouTube, and more, you can build ad creation and management, message sending and receiving, comment handling, analytics, and phone number and call features into your own apps and business workflows.

Normally, combining multiple social networks and communication services means dealing with each one’s API and authentication method. Zernio offers these integrations as a common set of APIs, which reduces the implementation and maintenance work for each service.

Here, “one API” does not mean sending every operation to a single URL. Think of it as a shared entry point, Zernio, from which you can use features such as posting, inbox, ads, and calls.

From a Social Media Posting API to Marketing Infrastructure

Zernio’s current direction is summed up by the tagline on its official site: “Marketing infrastructure for products and agents.” In plain terms, it is marketing infrastructure for products and AI agents.

It keeps the original use case of social media posting, while its scope has grown to include bringing in customers through ads, contacting customers, and handling their replies afterward.

Note that ads and DMs were already available before. The change is not that all of these appeared at once. Rather, the service can no longer be described as just social media posting, and its position as infrastructure supporting marketing as a whole has become clearer.

For example, you can make people aware of your service through posts, widen your reach with ads, and reply to inquiries by message. Zernio is an option for connecting these multiple touchpoints from your own app or AI agent.

How It Works

Basically, you create a Zernio account, connect the social networks, ad accounts, and other services you want to use, and then operate them through the API or MCP. For messaging and calls, you need a phone number or additional setup depending on the channel you use.

For social posting, you specify the content, media, and destinations and send the request, and Zernio handles posting to the connected networks. Because you can instruct posts to multiple platforms at once, you avoid implementing each posting API one by one.

The main components are as follows.

• Hosted OAuth: For supported social networks and other services, Zernio provides the authentication flow. This reduces the work of building your own developer apps and token refresh handling
• Common posting API: You can handle supported post formats, such as text, images, videos, and carousels, through a common API. You can also specify settings required by each destination
• Webhook notifications: You can receive events such as post results and incoming messages as notifications, which reduces the need to keep polling the API
• MCP server: When you connect an MCP-compatible client such as Claude or Cursor, you can instruct an AI assistant to post, analyze, and operate the inbox

However, requirements such as character limits, media formats, and permissions on each social network don’t go away. Don’t assume that image sizes, video formats, and post text are all optimized automatically. You need to prepare media and settings that match each destination’s requirements.

Zernio also offers features you can use from the screen, such as a drag-and-drop content calendar and a post editor. A distinctive point is that you can try it through the dashboard or MCP, not only by writing API code yourself.

Note: The screenshots show the interface at the time they were taken. The current layout and available features may differ.

Main Features

Zernio’s features can be organized as follows. Supported operations and conditions differ by platform, so it is important to check the combination you want to use.

Instant and Scheduled Posting to Social Networks

The core feature from the beginning is posting to social networks. You can post text, images, videos, and more immediately, or schedule posts for a specific date and time.

For supported destinations, you can also handle carousels and automatically posting a first comment. It remains a straightforward use case for media outlets that use multiple social networks, and for anyone who wants to build social media management tools for customers.

Automatically posting to multiple social networks from Google Sheets using Google Apps Script (GAS) is one example of using this posting feature.

Comment Handling and Unified Inbox

You can handle comments and DMs from supported platforms through a common inbox mechanism. You can build features for retrieving conversations and replying through the API into your own admin screens and business workflows.

A “comment-to-DM” automation, which sends a DM when a comment contains a specific keyword, is also available on supported channels.

However, not every social network supports the same operations. You need to check whether the operations you need, such as retrieving, replying, and deleting, are available on each destination.

Messaging with WhatsApp, SMS, iMessage, and More

In addition to social DMs, you can handle communication through WhatsApp, SMS, iMessage, and more. This goes beyond the scope of a social posting tool, and supports uses such as contacting customers from your app and processing the replies that come in.

The official documentation also describes sending and receiving iMessage, and provides a mechanism to gather conversations in the same unified inbox as WhatsApp, SMS, and social DMs.

On the other hand, this does not mean you can use the personal phone number you normally use for every purpose. Connection methods and conditions differ by channel. For example, for iMessage, the documentation describes a method that uses a dedicated sender.

If you build customer communication features into your app, it’s a good idea to check the destination country, available numbers, and message sending conditions before designing it.

Phone Number and Call Features

APIs for obtaining and managing phone numbers and for voice calls are also provided. These features let you build customer support that includes calls, not only text-based exchanges, into your app.

The official documentation describes mechanisms such as voice calls over the public telephone network, WhatsApp calls, and call history.

However, simply connecting Zernio does not give you a finished AI phone agent. If you want AI to hold the conversation, you need a design that includes a way to process the conversation and integration with external services.

Creating and Managing Ads

The Ads API lets you create and manage ad campaigns and retrieve results. APIs are available for multiple ad services, starting with Meta Ads.

Possible uses include promoting a regular post as an ad, and managing ad budgets and status from an app or AI agent.

Supported operations and required permissions differ by ad service. Also, being able to use the API is not the same as having your ads approved. You still need to check things such as the ad content and the state of your ad account.

Analyzing Post and Performance Results

The Analytics API lets you retrieve metrics for posts and accounts on supported social networks. You can build engagement and follower trends into your own dashboards and reports.

Available metrics differ by social network, so you won’t necessarily get the same numbers on every platform.

Being able to pull data through the API is a major feature, but you shouldn’t assume that you can only see raw data. Separating what you want to check in the standard screens from what you want to aggregate and display yourself makes it easier to sort out what you need to build.

Working with AI Assistants Through MCP

When you connect Zernio’s MCP server, you can instruct a supported AI assistant in natural language. The official documentation describes how to connect Claude, ChatGPT, Codex, Cursor, and others.

A convenient point is that you can ask the AI to check connected accounts, create posts, retrieve analytics data, and more, without writing API requests by hand each time.

However, giving instructions to AI does not remove the need for all connection settings. In addition to the initial account connection and permission settings, you need to decide which operations to leave to the AI.

For example, you could divide roles so that another AI assistant writes the post text, and only content a person has reviewed is delivered through Zernio. For actions such as changing ad budgets or sending messages to customers, it is easier to run things with a confirmation step before execution.

What Can You Use It For?

Because its features are broad, it helps to start by choosing one thing you want to achieve. Here are some example setups.

These are examples of setups that include Zernio. They don’t mean everything is finished just by signing up, but because you implement less for each connected service, you can spend more time on the screens and business workflows your own service needs.

Who Is It For?

Zernio suits the following people and teams.

• SaaS developers who want to build social posting or analytics features into their own products
• Developers who want to handle customer messaging and replies from their own apps
• Agencies that want to build a system that brings together social media, ads, and inquiry handling for multiple clients
• People who want to operate the execution side of social media or customer support from tools like Claude or Cursor
• Teams that want to spend their time developing their own screens and business workflows rather than service-by-service API integrations

Conversely, in the following cases, an operations tool that already has the features you need may be a better fit.

• People who want to use a finished social media management screen with as little initial setup and integration as possible
• People looking for a content creation environment centered on image editing or text generation
• People who want an analytics tool that comes with the charts and reports they need as standard

That said, it isn’t true that “people who can’t write code can’t use it.” You can also start from the dashboard or MCP. Rather than judging by programming experience alone, it helps to think in terms of whether you want to use existing screens, or build it into your own app and workflows.

What to Check Before You Use It

Even a convenient common API doesn’t remove the specifications of each connected service. Before adopting it, it’s important to check not only the number of supported services, but also the features and conditions you will actually use.

• Support for the operations you need: Even for the same social network, the supported range differs for posting, DMs, comments, and analytics
• The country and phone number you use: For messaging and calls, conditions differ by country, number type, and channel
• Cost breakdown: Check not only the cost of connected accounts, but also usage-based fees for phone numbers, telecom, messaging, and ads, as well as the actual ad spend
• Handling failures: Decide who checks and whether to retry when authentication expires or sending fails

For details on pricing plans, see our Zernio pricing guide. Also check the official pricing page for the latest billing terms.

Reliability and Track Record

Zernio’s official site introduces companies that use it, and also publishes examples of it being built into social integrations and AI marketing tools. In the official case studies, you can see uses that combine not only posting but also inbox, ads, and analytics.

However, customer logos or a processing count at a single point in time can’t tell you how stable it will be for your own use case. If you are considering production use, we recommend testing posting, receiving, and error notifications on the platforms you need, and confirming that it fits your actual work.

You can check feature changes in the Changelog in the official documentation. If you build the API in and use it over the long term, it’s a good idea to keep an eye on these updates too.

Summary

Zernio has expanded from a service that handles the differences in authentication and posting APIs across social networks into marketing infrastructure for apps and AI agents, one that can build in ads, messaging, and calls.

Automatic posting to multiple social networks is still one of the easiest ways to use it. On top of that, you can now build contact through WhatsApp, SMS, and iMessage, reply handling in a unified inbox, and ad management into your own systems.

You can also use it from the dashboard or MCP, but I think its appeal is easiest to feel when you want to add the features you need to your own app or business workflow. Start with a small use case such as posting, then expand into customer communication as needed, and Zernio’s role will be easier to grasp.

For details on pricing plans, see our Zernio pricing guide.