Zernio
Connect Zernio to schedule and publish posts across social networks, manage a unified inbox, and track analytics.
You paste one Zernio API key, a 67-character string made of the sk_ prefix plus 64 hex characters. Zernio shows the value once, at creation.
- Setup time
- 3 min
- Auth
- API credentials
- API base URL
- https://zernio.com/api/v1
- Rate limits
- Scales with your team's connected social accounts: 60 requests per minute on the free 0 to 2 account tier, 600 at 3 to 2,000 accounts and 1,200 above that. Analytics endpoints are additionally capped at 6, 10 and 20 requests per second respectively.
Before you begin
- A Zernio account. The free tier works and no credit card is needed
- A profile with at least one connected social account, otherwise the publishing and analytics tools have nothing to act on
- Access to your team's Settings area, which is where keys are created
Get your credentials
Sign in and connect a social account
Sign in at zernio.com, or click Sign up free if you do not have an account. Create a profile and connect at least one social account from the dashboard.
Open the API Keys page
Open Settings and click API Keys, or go straight to zernio.com/dashboard/api-keys.
API Keys
Keys authenticate REST and MCP requests for this team.
| Name | Key | Last used | Created | Status |
|---|---|---|---|---|
| Scheduler botServer-side | sk_1f4c****9ab2 | Mar 4, 2026 | Feb 11, 2026 | Active |
| Old n8n flowRetired | sk_88ba****02de | Jan 9, 2026 | Nov 2, 2025 | Revoked |
Existing keys only ever show a masked prefix.
Create a key for PopMCP
Click Create API Key and enter a Name such as PopMCP. Click Create API Key in the dialog to confirm.
API Keys
Zernio recommends one key per application so you can revoke it on its own.
Copy the key before closing the dialog
Copy the full sk_ value shown in the dialog, then click Done.
API Keys
67 characters: the sk_ prefix plus 64 hex characters.
Paste it into PopMCP
Open the Zernio connector in PopMCP, paste the value into the API key field, and save.
Connect in PopMCP
Open your workspace, choose Zernio in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | Zernio dashboard → Settings → API Keys → create a key (it looks like sk_ followed by 64 hex characters). Stored encrypted; used server-side only. The connection is locked to this key's account.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Zernio immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
The Zernio connector in PopMCP flips to Connected, and a read-only request such as "list my scheduled posts" returns rows from your Zernio account instead of a 401.
Troubleshooting
401 Unauthorized
Why: The key was truncated on paste, or it has been deleted in Zernio.
Fix: Check the value is exactly 67 characters and starts with sk_. If in doubt, create a fresh key on the API Keys page and paste that. PopMCP sends it as an Authorization: Bearer header, server-side only.
You closed the dialog before copying the key
Why: Zernio only stores a SHA-256 hash, so an existing key cannot be revealed.
Fix: Delete the key from the API Keys list and create a replacement.
429 Too Many Requests
Why: Free teams with 0 to 2 connected social accounts are capped at 60 requests per minute, and analytics endpoints at 6 requests per second.
Fix: Slow the calls down, or connect more social accounts. The ceiling rises to 600 per minute at 3 or more accounts, and 1,200 above 2,000.
Publishing tools return no accounts
Why: No social accounts are connected to the Zernio team the key belongs to.
Fix: Connect at least one network in the Zernio dashboard. The same key then works without regenerating.