Inbox conversations now include ad-click attribution via a new metadata object in responses from GET /v1/inbox/conversations and GET /v1/inbox/conversations/{conversationId}.

This lets you identify when a conversation started from a click-to-message ad (vs organic) and store the associated ad identifiers/details.

New field:
• metadata (object, nullable) — only present for ad-originated conversations; absent for organic

Common keys you may see in metadata:
• WhatsApp CTWA: ctwa_clid, ctwa_source_id, ctwa_source_url, ctwa_headline, ctwa_source_type, ctwa_captured_at
• Meta CTM/CTD: meta_ad_id, meta_ad_title, meta_ad_source, meta_ad_type, meta_ad_ref, meta_ad_captured_at, meta_ad_photo_url, meta_ad_video_url, meta_ad_post_id, meta_ad_product_id, meta_ad_flow_id

View documentation

GET /v1/ads/lead-forms/{formId} now returns a fully detailed form object (enough to duplicate the form via POST /v1/ads/lead-forms).

Key fields include form.status (ACTIVE/ARCHIVED), questions, thank_you_page, and context_card.

Geo targeting search via GET /v1/ads/targeting/search now supports additional geoType values when dimension=geo: subcity, neighborhood, place, metro_area, geo_market (in addition to country, region, city, zip).

View documentation

Moving an account to another profile via PATCH /v1/accounts/{accountId} can now return 409 when the target profile already has an account on the same platform.

This enforces the rule that a profile can hold only one account per platform.

Handle the new response:
• 409 - target profile already has an account of the same platform (profile_platform_conflict)

View documentation

POST /v1/ads/create now supports additional Meta geo targeting controls.

You can target more precise location types and explicitly exclude locations when creating Meta ads.

New fields:
• places (Meta geoType place)
• neighborhoods (Meta geoType neighborhood)
• excludedLocations with countries, regions, cities, zips

POST /v1/ads/lead-forms adds richer Meta Instant Form configuration.

New fields:
• formType: MORE_VOLUME | HIGHER_INTENT | RICH_CREATIVE
• blockDisplayForNonTargetedViewer
• allowOrganicLeadGen
• questionPageCustomHeadline
• contextCard (title, content, style: LIST_STYLE | PARAGRAPH_STYLE, buttonText, coverPhoto)

GET /v1/ads/targeting/search geo search now supports geoType=all and returns coordinates.

Use dimension=geo with geoType=all to search across all geo types in one call, and read latitude / longitude from results (when available).

View documentation

Meta boosts via POST /v1/ads/boost now support raw Meta-native targeting with rawTargeting.

Use rawTargeting to pass a Meta targeting spec verbatim (snake_case like geo_locations, custom_audiences, excluded_custom_audiences, flexible_spec, targeting_automation) to target specific custom/lookalike audiences or clone targeting exactly.

Key rule: rawTargeting is mutually exclusive with targeting (sending both returns 422).

View documentation

Comment webhooks (comment.received) now include an optional comment.attachment object for Facebook graphic-only comments (sticker, GIF, photo).

This lets you detect and render comments that have no text content; note Meta URLs may be ephemeral, so fetch promptly.

Key fields:
• comment.attachment.type (required)
• comment.attachment.imageUrl
• comment.attachment.url

View documentation

WhatsApp phone number provisioning now supports creating a hosted KYC link via POST /v1/whatsapp/phone-numbers/kyc/share.

This generates a single-use, 7-day link your end customer can complete without a Zernio login; once submitted, the number provisions under your account (only for regulated/KYC countries).

Request fields:
• profileId (required)
• country (required, ISO-2; non-KYC countries return 400)
• branding (optional: companyName, logoUrl, brandColor)
• redirect_url (optional; on success appends kyc=submitted and country=<ISO-2>)

Response fields:
• url
• token
• expiresAt

To react when the form is completed, subscribe webhooks to the new event: whatsapp.number.kyc_submitted (available in POST/PUT /v1/webhooks/settings).

View documentation

POST /v1/whatsapp/phone-numbers/kyc now supports provisioning multiple same-country numbers in a single KYC submission via quantity.

Set quantity (default 1, min 1, max 5) to request several numbers; the same verification covers all of them and each number is billed only when it activates (best-effort if some orders fail).

Response now includes numbers (array) with all provisioned numbers. phoneNumber remains and represents the first/primary number for backward compatibility.

status remains: kyc_submitted | kyc_reused | kyc_already_submitted

View documentation

Instagram posts now support AI-generated media self-disclosure via isAiGenerated in platformSpecificData.

When isAiGenerated is true, Instagram labels the post as containing AI-generated media (this is for media, not AI-written captions).

Set:
• isAiGenerated (boolean, default false)

Applies to feed posts, Reels, Stories, and carousels.

View documentation

Instagram Trial Reels are now identifiable per platform target in post responses.

When an Instagram reel is created as a Trial (via platformSpecificData.trialParams), the corresponding PlatformTarget may include:
• isTrialReel (boolean) — present and true only for trial reels
• trialGraduationStrategy — MANUAL | SS_PERFORMANCE (present only when isTrialReel is true)

Use these fields to segment trial reels in analytics; note this reflects creation-time intent (Instagram doesn’t expose a readable trial flag).

View documentation

New endpoint GET /v1/ads/campaigns/{campaignId}/analytics returns campaign-level analytics in one call (summary metrics, daily[] timeline, and optional Meta demographic breakdowns).

Use query params fromDate, toDate (defaults to last 90 days; max 730 days) and optional platform to disambiguate IDs. For Meta-only breakdowns, pass breakdowns as a comma-separated list: age, gender, country, publisher_platform, device_platform, region, platform_position, impression_device, video_asset, image_asset, body_asset, title_asset.

GET /v1/ads/tree now supports daily trends in the same response: set timeIncrement=1 to add daily[] metrics series, and control where it appears with dailyLevel = campaign (default) | adset | ad.

View documentation

New endpoint GET /v1/inbox/mentions is available to list mentions of your connected organization accounts delivered via platform webhooks.

Currently supports LinkedIn organization mentions and requires the Inbox addon.

Key query params:
• accountId (filter by social account ID)
• profileId (filter by profile ID)
• sortOrder (asc | desc, default desc)
• limit (1–100, default 25)
• cursor (pagination)

Response includes data items with id, platform (linkedin), content, permalink, authorUrn, organizationalEntity, publishedAt, plus pagination (hasMore, cursor).

View documentation

WhatsApp Business Profile now supports managing business usernames via new endpoints.

You can fetch the current username + approval state, claim/transfer a username, release it, and retrieve available suggestions.

New endpoints:
• GET /v1/whatsapp/business-profile/username (accountId query) → returns username (nullable) and status (approved/reserved/none)
• POST /v1/whatsapp/business-profile/username body: accountId, username, optional transferAction (none/force_transfer)
• DELETE /v1/whatsapp/business-profile/username body: accountId
• GET /v1/whatsapp/business-profile/username/suggestions (accountId query) → returns suggestions[]

On username claim failures, expect error codes like whatsapp_username_unavailable, whatsapp_username_ineligible, or whatsapp_username_transfer_required.

View documentation

New endpoint POST /v1/posts/sync-external lets you sync/verify external (non-Zernio) posts on demand, so a just-published post can be retrieved within seconds instead of waiting for the background sync.

Use it to confirm a user-submitted post exists by sending accountId plus either url or postId.

Request body:
• accountId (required)
• url (optional)
• postId (optional)

Response:
• synced.postsFound, synced.postsSynced, synced.skipped
• If url/postId provided: found + post (or null)
• If no locator provided: posts (recent external posts)

Returned posts use ExternalPostSummary (includes platform, platformPostId, platformPostUrl, publishedAt, and basic analytics like likes/comments).

View documentation

WhatsApp document sends via URL now support setting the displayed filename using attachmentName on POST /v1/inbox/conversations/{conversationId}/messages.

This lets you control the recipient-visible file name for attachmentUrl document messages (otherwise WhatsApp derives it from the URL and may show “Untitled”).

Use:
• attachmentType: file
• attachmentUrl: (public URL)
• attachmentName: e.g. Report.pdf

Applies to WhatsApp only; ignored for image/video/audio and for multipart binary uploads.

View documentation

POST /v1/invite/tokens now supports inviting users with the new admin role via role.

Use role=admin to grant team-management permissions (invite/remove members, change roles and access) without billing, ownership transfer, or account deletion permissions.

role enum is now: admin, member, billing_admin, viewer.

Note: readOnly (deprecated) can’t be combined with role=billing_admin or role=admin.

View documentation

Workflow send_message nodes now allow omitting interactive.type; it will be inferred from the interactive payload shape.

This makes interactive message configs simpler, but payloads with neither type nor an inferable shape are now rejected.

Applies to send_message.config with messageType = interactive (WhatsApp-only).

View documentation

GET /v1/connect/pending-data now supports Pinterest board selection in headless OAuth flows.

For Pinterest (in addition to LinkedIn orgs and Snapchat profiles), the OAuth redirect returns pendingDataToken and you can fetch the full selection payload via token.

Use token (query) from the redirect, and read selectionType (enum: organizations, pages, boards, locations, profiles) to determine which selection array to consume (e.g. boards for Pinterest).

View documentation

WhatsApp KYC form spec now returns an optional audience per requirement in GET /v1/whatsapp/phone-numbers/kyc.

This lets you show/collect only the fields that apply to the end-user type (business vs individual) and avoid submitting both sets of requirements.

New field: fields[].audience = business | individual | null (applies to both).

View documentation

Webhook post events now include the connected social account per platform target via post.platforms[].accountId.

This lets you route/attribute webhook deliveries by the specific SocialAccount used for each platform publish (useful when a single post spans multiple accounts).

New field:
• WebhookPayloadPost.post.platforms[].accountId
• WebhookPayloadPostPlatform.post.platforms[].accountId (on post.platform.published / post.platform.failed; see also the top-level account block there)

View documentation

Webhook payloads now include account.accountId (same value as account.id) as a canonical field for filtering/routing events.

This makes it easier to consistently filter all webhook events by a single field (e.g. route staging vs production by account) while keeping account.id for backward compatibility.

New field:
• account.accountId

Added to these webhook payloads:
• comment.received
• lead.received
• review.new
• review.updated
• post.external.created, post.external.updated, post.external.deleted
• inbox webhook payloads via InboxWebhookAccount

View documentation