Threads posts now support an explicit topic tag via platformSpecificData.topic_tag.

Use this to categorize posts for discoverability on Threads; when provided, it overrides auto-extraction from content hashtags.

Set topic_tag (string):
• 1–50 characters
• cannot contain . or &

View documentation

Zernio now supports WhatsApp Business 😎

Build full WhatsApp integrations in 2 minutes.

Messaging
• Send text, images, video, audio, documents, stickers, contacts, and locations
• Interactive messages with buttons, lists, and CTA URLs
• Reactions and read receipts
• 24-hour conversation window handled automatically: freeform messages when open, template messages when not

Campaigns & Broadcasts
• Create and schedule broadcast campaigns to contact lists
• Per-recipient variable substitution for personalized templates
• Drip sequences with configurable delays between steps
• Real-time delivery stats: sent, delivered, read, failed

Template Management
• Create custom templates or use Meta's pre-approved library templates
• Full CRUD: create, update, delete, list
• Support for header media (image, video, document), body variables, buttons, and footers

Contact Management
• Import, group, and manage contacts via API
• Bulk operations for large lists

Phone Numbers
• Purchase and provision numbers directly through the API ($2/mo)
• Pre-verified number pool (skip OTP entirely)
• Manage business profile, display name, and profile photo


Requires de Inbox add-on. No markup on Meta's per-conversation pricing.

Docs: docs.zernio.com/platforms/whatsapp

New endpoint: POST /v1/posts/{postId}/update-metadata to update metadata on an already-published post without re-uploading media.

Currently supported for YouTube videos only; the post must be published on the target platform and you must provide at least one updatable field.

Request body: platform (youtube) plus any of title, description, tags, categoryId, privacyStatus (public | private | unlisted).

View documentation

POST /v1/posts/{postId}/update-metadata now supports updating YouTube video metadata even if the video was uploaded outside Zernio.

Use one of two modes:
• Post-based: call with the real {postId} and platform
• Direct video ID: set {postId} to _ and include videoId + accountId + platform

Key params:
• platform: youtube
• videoId (direct mode)
• accountId (direct mode)

In direct mode, the 200 response may include videoId.

View documentation

📡 New API Endpoints

POST /v1/inbox/conversations/{id}/typing
→ Typing indicators (Facebook Messenger, Telegram)

DELETE /v1/inbox/conversations/{id}/messages/{msgId}
→ Delete messages (Telegram, X, Bluesky, Reddit)

POST/DELETE /v1/inbox/conversations/{id}/messages/{msgId}/reactions
→ Emoji reactions (Telegram, WhatsApp)

docs.zernio.com

YouTube posts now support adding a video to a playlist via playlistId in YouTubePlatformData.

Use the new playlist endpoints to discover playlist IDs and (optionally) store a client-side default for an account.

New endpoints:
• GET /v1/accounts/{accountId}/youtube-playlists → returns playlists[] and defaultPlaylistId
• PUT /v1/accounts/{accountId}/youtube-playlists with defaultPlaylistId (optional defaultPlaylistName)

New field:
• platformSpecificData.youtube.playlistId (string) — optional playlist to add the video to after upload

View documentation

YouTube metadata updates now support setting a custom thumbnail via POST /v1/posts/{postId}/update-metadata.

You can update the thumbnail without re-uploading, including for existing videos not published through Zernio (direct video ID mode).

Use thumbnailUrl (public image URL) with platform youtube. In direct mode also include videoId + accountId.

Key params: platform (youtube), thumbnailUrl, videoId, accountId

View documentation

YouTube metadata updates now support additional fields on POST /v1/posts/{postId}/update-metadata.

You can now set COPPA compliance, disclose AI/synthetic media, and add a video to a playlist without re-uploading.

New optional properties:
• madeForKids (boolean)
• containsSyntheticMedia (boolean)
• playlistId (string)

View documentation

4 new Inbox APIs just shipped

1. Contacts
Auto-created from every DM across all your connected accounts. Add tags, custom fields, bulk import.

POST /v1/contacts · POST /v1/contacts/bulk · GET /v1/contacts · GET /v1/contacts/:id · PATCH /v1/contacts/:id · DELETE /v1/contacts/:id

2. Broadcasts
Send one message to thousands of contacts. Segment by tag or custom field. Supports Instagram, Facebook, Telegram, WhatsApp, Twitter, Bluesky, Reddit. Schedule or send immediately. Real-time delivery + read tracking.

POST /v1/broadcasts · POST /v1/broadcasts/:id/send · POST /v1/broadcasts/:id/schedule · POST /v1/broadcasts/:id/cancel · POST /v1/broadcasts/:id/recipients

3. Sequences
Drip campaigns for social DMs. Set delays between steps (hours, days). Auto-exit on reply or unsubscribe.

POST /v1/sequences · POST /v1/sequences/:id/activate · POST /v1/sequences/:id/pause · POST /v1/sequences/:id/enroll · GET /v1/sequences/:id/enrollments

4. Comment Automations
Set a keyword on any Instagram or Facebook post. When someone comments it, they get a DM instantly. Add an optional public reply too.

POST /v1/comment-automations · GET /v1/comment-automations/:id/logs

All official platform APIs. Requires the Inbox add-on.

https://docs.zernio.com/

YouTube analytics now supports audience demographics via GET /v1/analytics/youtube/demographics.

Fetch demographic insights for a YouTube channel broken down by age/gender (percentages) and country (view counts). Requires the Analytics add-on and YouTube Analytics scope.

Key params:
• accountId (required)
• breakdown = age, gender, country (comma-separated; defaults to all)
• startDate, endDate

WhatsApp now supports Flows (create/manage/publish and send interactive flow messages).

Manage flows:
• GET /v1/whatsapp/flows (accountId)
• POST /v1/whatsapp/flows (accountId, name, categories, optional cloneFlowId)
• GET /v1/whatsapp/flows/{flowId} (accountId, optional fields)
• PATCH /v1/whatsapp/flows/{flowId} (accountId, name/categories; DRAFT only)
• DELETE /v1/whatsapp/flows/{flowId} (accountId; DRAFT only)

Flow JSON asset:
• GET /v1/whatsapp/flows/{flowId}/json (accountId)
• PUT /v1/whatsapp/flows/{flowId}/json (accountId, flow_json; DRAFT only)

Lifecycle:
• POST /v1/whatsapp/flows/{flowId}/publish (accountId; irreversible)
• POST /v1/whatsapp/flows/{flowId}/deprecate (accountId; irreversible)

Send a flow message:
• POST /v1/whatsapp/flows/send with accountId, to, flow_id, flow_cta, body
• Optional flow_action = navigate | data_exchange, flow_token, flow_action_payload, draft

View documentation

New Google Business Profile analytics endpoints are available.

Fetch daily performance metrics (impressions, clicks, calls, directions, etc.) via GET /v1/analytics/googlebusiness/performance. Requires accountId and the Analytics add-on; data may be delayed 2–3 days; up to 18 months history.

Key params:
• accountId (required)
• metrics (comma-separated; defaults to all): BUSINESS_IMPRESSIONS_DESKTOP_MAPS, BUSINESS_IMPRESSIONS_DESKTOP_SEARCH, BUSINESS_IMPRESSIONS_MOBILE_MAPS, BUSINESS_IMPRESSIONS_MOBILE_SEARCH, BUSINESS_CONVERSATIONS, BUSINESS_DIRECTION_REQUESTS, CALL_CLICKS, WEBSITE_CLICKS, BUSINESS_BOOKINGS, BUSINESS_FOOD_ORDERS, BUSINESS_FOOD_MENU_CLICKS
• startDate, endDate (YYYY-MM-DD)

Fetch monthly search keywords via GET /v1/analytics/googlebusiness/search-keywords. Requires accountId and the Analytics add-on; up to 18 months history.

Key params:
• accountId (required)
• startMonth, endMonth (YYYY-MM)

Note: keywords below Google’s minimum impression threshold are excluded.

View documentation

You can now edit a published X (Twitter) post via POST /v1/posts/{postId}/edit.

This updates the post on X and stores edit history in Zernio. X constraints apply (Premium required, 1-hour edit window, max 5 edits, text-only).

Request body:
• platform: twitter
• content: new text

Response includes:
• id (new tweet ID after edit)
• url

You can now start/send X DMs via POST /v1/inbox/conversations.

If a thread already exists, the message is appended. If the recipient doesn’t accept DMs, you’ll get 422 with code=DM_NOT_ALLOWED (or bypass the pre-check with skipDmCheck).

Key fields:
• accountId
• participantId or participantUsername
• message (or attachment via multipart/form-data)
• skipDmCheck

Also added:
• Root-level facebookSettings on POST /v1/posts and PUT /v1/posts/{postId} (e.g. facebookSettings.draft=true to create an unpublished draft in Facebook Publishing Tools)
• TwitterPlatformData.longVideo=true to enable long video uploads (requires X Premium; may require allowlisting).

View documentation

Facebook now supports posting an optional first comment for Reels as well as feed posts.

Use platformSpecificData.facebook.firstComment to add a comment immediately after publishing (not supported for contentType=story). Skipped when draft is true.

Applies when contentType is reel (or omitted for feed posts).

View documentation

We just released the official Zernio adapter for Vercel's Chat SDK

https://docs.zernio.com/resources/integrations/chat-sdk

Webhooks now support message sent events via message.sent.

Use this to get notified when a message is sent via the API, including message + conversation context.

Subscribe by adding message.sent to Webhook.events.

You can also filter/view deliveries in logs with GET /v1/webhooks/logs using event=message.sent.

Payload schema: WebhookPayloadMessageSent (includes message, conversation, account, timestamp).

View documentation

Discord is now supported as a platform in several endpoints and response schemas.

You can now use platform=discord to connect accounts, validate content, and filter account health.

Updated enums:
• GET /v1/connect/{platform}: {platform} includes discord
• POST /v1/tools/validate/post: platforms[].platform includes discord
• GET /v1/accounts/health: query platform includes discord
• Schemas: SocialAccount.platform, PostLog.platform, ConnectionLog.platform include discord

View documentation

Meta ads now return additional campaign/ad set details in ad reporting responses.

You can use these fields to display objective/optimization/bidding context and conversion event setup alongside metrics.

New fields:
• On Ad: platformObjective, optimizationGoal, bidStrategy, promotedObject
• On AdTreeCampaign and AdCampaign: platformObjective, optimizationGoal (can be string or string[]), bidStrategy, promotedObject
• On AdTreeAdSet: optimizationGoal, bidStrategy, promotedObject

promotedObject may include custom_event_type, pixel_id, page_id (and on Ad also application_id, product_set_id). Fields are null when not applicable and are only present for Meta ads.

View documentation

Campaign-level optimizationGoal is now always a string in ads campaign responses.

If ad sets have different optimization goals, the API now returns a comma-separated string instead of an array.

Applies to:
• GET /v1/ads/campaigns (AdCampaign.optimizationGoal)
• GET /v1/ads/tree (AdTreeCampaign.optimizationGoal)

Example: "OFFSITE_CONVERSIONS, VALUE, LEAD_GENERATION"

View documentation

New Ads Conversions API endpoints are available: POST /v1/ads/conversions and GET /v1/accounts/{accountId}/conversion-destinations.

You can now relay conversion events to Meta or Google Ads; platform is inferred from accountId. List valid destinations first, then send a batch of events.

Use GET /v1/accounts/{accountId}/conversion-destinations to get destinations[].id (use as destinationId) and destinations[].status (active/inactive). For Google, destinations[].type is present (event type locked to the conversion action).

Send events via POST /v1/ads/conversions with accountId, destinationId, events[] (each requires eventName, eventTime, eventId, user). Optional: testCode (Meta only) and batch-level consent (adUserData/adPersonalization: GRANTED/DENIED, Google only).

Response includes platform (metaads/googleads), eventsReceived, eventsFailed, failures[], and traceId. Requires the Ads add-on.

View documentation

Discord support has been added: you can now manage Discord account settings, list available guild channels, and post to Discord with Discord-specific options.

Manage Discord connection settings:
• GET /v1/accounts/{accountId}/discord-settings (read current channel/guild + webhook identity)
• PATCH /v1/accounts/{accountId}/discord-settings (update webhookUsername/webhookAvatarUrl and/or switch channelId)
• GET /v1/accounts/{accountId}/discord-channels (discover channels: type = 0/5/15)

Post to Discord via POST /v1/posts using platformSpecificData = DiscordPlatformData:
• Required: channelId
• Optional: embeds, poll, crosspost, forumThreadName, forumAppliedTags, threadFromMessage, tts, webhookUsername, webhookAvatarUrl

Analytics responses now include platformPostId per platform in GET /v1/analytics.

Ads goals have been expanded in POST /v1/ads/boost and POST /v1/ads/create: goal now supports engagement, traffic, awareness, video_views, lead_generation, conversions, app_promotion (availability varies by platform).

View documentation

Webhook comment.received payloads may now include null for Zernio internal post IDs when the post was not published through Zernio.

Handle missing internal IDs by relying on the platform IDs instead.

Fields that can now be null:
• comment.postId
• post.id

Use comment.platformPostId / post.platformPostId as the stable identifiers in these cases.

View documentation