canonical: https://jentic.com/apis/zernio.com/zernio

# Zernio Social Media API

Zernio (formerly Late/getlate) unified social media API for scheduling posts, managing conversations, analytics, and webhook notifications across 14+ platforms. The API exposes 5 endpoints secured with bearer authentication.

## For AI agents

Programmatically schedule a post, connect social account via oauth. Covers 5 operations with bearer authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Schedule a post
- Connect social account via OAuth
- Get engagement analytics
- Configure webhook notifications
- List inbox conversations

## Use cases

### Communications Operations

Use the Zernio Social Media API to perform communications operations programmatically. The API provides 5 endpoints covering core functionality including schedule a post, connect social account via oauth, get engagement analytics.

Example prompt: Call POST /posts to schedule a post

### Automated Analytics Management

Automate analytics operations by combining multiple Zernio Social Media API endpoints. Agents can connect social account via oauth and then get engagement analytics in a single workflow.

Example prompt: Call GET `/connect/{platform}` to connect social account via oauth, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zernio Social Media API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'schedule a post', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/posts` | Schedule a post |
| GET | `/connect/{platform}` | Connect social account via OAuth |
| GET | `/analytics` | Get engagement analytics |
| POST | `/webhooks/settings` | Configure webhook notifications |
| GET | `/inbox/conversations` | List inbox conversations |

## Key resources

- **Analytics** — Operations related to Analytics
- **Connections** — Operations related to Connections
- **Inbox** — Operations related to Inbox
- **Posts** — Operations related to Posts
- **Webhooks** — Operations related to Webhooks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 47 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/zernio.com/zernio/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Zernio Social Media API by hand means carrying its bearer token on every request, coding post creation, platform connection, and inbox handling on zernio.com/api/v1 yourself. Through Jentic you install once, import Zernio Social Media from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Zernio carries the post content in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as creating a post or reading analytics. You leave out webhook settings unless the agent is meant to change them.
- **Credential handling:** Your Zernio token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'schedule a post' or 'read post analytics', and Jentic returns the matching Zernio Social Media operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Zernio Social Media API use?

The Zernio Social Media API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I schedule a post with the Zernio Social Media API?

Yes. Use the POST /posts endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Zernio Social Media API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I schedule a post through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'schedule a post'. Jentic returns the matching Zernio Social Media API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Zernio Social Media API have?

The Zernio Social Media API exposes 5 endpoints covering analytics, connections, inbox operations.

### Can I limit what my agent is allowed to do with the Zernio Social Media API?

Yes. Because you run Jentic One yourself, your own rules decide which Zernio operations and credentials the agent can use, so you can allow only what a task needs, such as scheduling posts with POST /posts or reading engagement analytics with GET /analytics. You can withhold the webhook settings operation (POST `/webhooks/settings`) unless the agent is meant to change delivery configuration, and leave out account connection at GET `/connect/{platform}` when it is not required. The stored bearer token is injected only for the calls you permit, so a scheduling agent cannot reach the inbox or reconfigure webhooks.