Changelog

You can now create YouTube playlists via POST /v1/accounts/{accountId}/youtube-playlists.

This creates an empty playlist on the connected YouTube channel and returns the playlist object; use the returned playlist.id as platformSpecificData.playlistId when publishing a video.

Request body:
• title (required)
• description (optional)
• privacy: private | public | unlisted (default private)

Notes: requires YouTube OAuth scope youtube or youtube.force-ssl; costs 50 YouTube quota units; not idempotent (retrying can create duplicate playlists).

New endpoint GET /v1/ads/campaigns/{campaignId} returns a single Meta campaign live, so you no longer need to page GET /v1/ads/campaigns just to find one campaign.

Call it with campaignId (Meta platformCampaignId) and accountId. Optionally override the Graph projection with fields (passed through to Meta; unknown fields return Meta’s 400).

Key params:
• campaignId (path)
• accountId (query, required)
• fields (query, optional; e.g. id,name,status,daily_budget)

Note: if the resolved connection can’t see the campaign, Meta returns 400 (not 404).

Also: PUT /v1/ads/{adId} may now return 429 when Meta rate-limits writes to metered objects (notably ad creatives). Retry after ~30 seconds.

GET /v1/ads/lead-forms/{formId} now returns the full Meta form (including thankyoupage) and can be customized with a Meta Graph field selection.

Use fields (Meta only) to override the default projection so newly-added Meta fields are reachable without an API change (e.g. name,thankyoupage{title,body,buttontype,websiteurl}). Invalid selections are rejected with 400.

Meta lead forms are now strictly scoped to the Page managed by accountId: reading or archiving a form on any other Page returns 404.

Also applies to DELETE /v1/ads/lead-forms/{formId} (archive): you may now receive 404 when the form isn’t on the managed Page.

TikTok connect behavior changed on GET /v1/connect/{platform}: TikTok connections now go through the TikTok for Business app, and each profile supports one TikTok account.

Connecting TikTok on a profile that already has one will replace it; reconnecting the same account keeps history, but authorizing a different account can delete the previous account’s analytics/inbox/DM history.

Handle the new redirect error missingtiktokpermissions (user-fixable): the authorization omitted required permissions, so nothing changes and the existing connection keeps working. Re-run the flow and accept all permissions.

Key fields:
• Path: platform=tiktok
• Query: profileId, redirect_url, optional headless
• Redirect error enum now includes: missingtiktokpermissions

Google Ads behavior changed for campaign status + targeting.

Campaign status on Google now cascades on resume via PUT /v1/ads/campaigns/{campaignId}/status.
Setting status to active turns on the campaign and the ad groups/ads Zernio tracks under it in one mutate (Google’s most-restrictive switch wins). Setting paused still writes the campaign only.

Campaign targeting reads now return real device bid adjustments via GET /v1/ads/campaigns/{campaignId}/targeting.
devices[].bidModifier is now Google’s bid adjustment (null = none, 0 = device switched off), and the returned device list depends on channel (Search: MOBILE/DESKTOP/TABLET; Display also includes CONNECTED_TV).

Device targeting edits are stricter on Google via PUT /v1/ads/campaigns/{campaignId}/targeting.
When sending targeting.devices, any supported device you omit is switched off (written with bidModifier: 0). Sending a device the campaign channel doesn’t support, or switching every device off, now returns 422.

New endpoints let you inspect and re-subscribe a connected Facebook Page’s webhook field subscription (read live from Meta), so you can detect and fix cases where leadgen is missing and lead ads stop arriving.

Read current subscription:
• GET /v1/accounts/{accountId}/webhook-subscription
Returns appSubscribed, leadgen, subscribedFields, and warning (only when leadgen is missing).

Re-subscribe (re-sends full field set to Meta and reads back what was actually granted):
• POST /v1/accounts/{accountId}/webhook-subscription
Returns resubscribed, plus appSubscribed, leadgen, subscribedFields, and optional warning.

Both endpoints can return 409 when the connection has no selected Page; the POST can return 502 if Meta rejects the subscription.

Meta Promotion is no longer supported in the Ads API.

Meta validates promotion metadata on create, but discards it, so Zernio now rejects it to avoid false positives. Any request that sends a Promotion object will now fail.

Changes:
• POST /v1/ads/create: promotion is rejected (400) on all shapes
• POST /v1/ads/creatives: promotion is rejected (400)
• PUT /v1/ads/{adId}: creative.promotion is not supported; any object is rejected (400)
• GET /v1/ads/{adId}: removed query param refreshPromotion

Use creativeFeatures (values OPTIN | OPTOUT) for Advantage+ enhancements; set Promotions directly in Meta Ads Manager instead.

Analytics post items now include ad detection via isAd in AnalyticsListResponse.posts[].

Use this flag to exclude paid delivery from organic reporting when a post’s metrics include ads (e.g., LinkedIn dark posts, TikTok Spark/boosted promotions).

New field:
• isAd (boolean) — true when metrics include paid delivery; false otherwise (note: some TikTok uploaded-asset ads can’t be detected and may still report false).

TikTok posting behavior is now clarified for TikTok for Business accounts when using videoCoverImageUrl and videoMadeWithAi.

For TikTok for Business connections, videoCoverImageUrl is passed to TikTok as the cover directly (no stitching), and the URL must resolve on a TikTok-verified domain.

Also, videoMadeWithAi disclosure is supported on video posts only for TikTok for Business: setting videoMadeWithAi=true on a direct photo post will be rejected. Use draft=true to send the photo to Creator Inbox and set the disclosure in the TikTok app.

Key fields:
• videoCoverImageUrl
• videoMadeWithAi
• draft

PUT /v1/ads/{adId} now supports updating Google Ads creatives beyond Search: you can update Display responsive ads and Performance Max asset groups.

Google creative updates are now dispatched by the ad’s advertisingChannelType, and unsupported creative fields for a channel return 422.

Key request fields:
• Google Search + Display: headlines, descriptions, finalUrls
• Google Display (additional under creative): creative.longHeadline, creative.businessName, creative.imageUrl, creative.squareImageUrl
• Google Performance Max: assetGroup (schema GooglePmaxAssetGroupUpdate) with fields like finalUrl, headlines, descriptions, businessName, images.landscape/images.square/images.logo, youtubeVideoIds

Channel validation highlights:
• Display rejects pinned positions (no pinnedField)
• assetGroup returns 422 on non-Performance-Max ads; other Google-only creative fields return 422 when the channel can’t carry them

Google Ads ad updates now support editing campaign-level geo + language targeting via PUT /v1/ads/{adId}.

You can now replace the campaign’s targeting.locations (or top-level geo fields) and targeting.languages from the ad update call; each provided list replaces the full set, and omitted fields are left unchanged.

Key fields:
• targeting.locations: country-code array or { countries, regions, cities, zips, metros• targeting.languages: ["en", "de", "zh_CN", ...] (full replacement)

Behavior/validation:
• Empty locations now returns 400 (omit locations to leave targeting unchanged)
• customLocations (radius targeting) returns 422
• Don’t mix targeting.locations with top-level geo fields (countries/regions/cities/zips/metros): mixing returns 400`
• Location/language updates are applied atomically in one Google mutate (no half-applied sets); negative (excluded) locations are left untouched

LinkedIn B2B targeting facets can now be searched via GET /v1/ads/targeting/search using new dimension values.

This lets you resolve LinkedIn facet values to the exact URNs to pass into TargetingSpec, so you don’t need to assemble URNs manually.

Use dimension:
• industry → feeds TargetingSpec.industries
• jobFunction → feeds TargetingSpec.jobFunctions
• seniority → feeds TargetingSpec.seniorities
• companySize → feeds TargetingSpec.companySizes

Returned results[].id is the full URN (e.g. urn:li:industry:4, urn:li:function:8, urn:li:seniority:6, urn:li:staffCountRange:(51,200)).

comment.received webhook payloads now include Threads and no longer include X/Twitter.

You can now receive comment events for Threads posts. If you validate or route by platform, update your handling to match the new enum and note that X/Twitter does not fire this event.

Update comment.platform enum to:
• instagram, facebook, threads, youtube, linkedin, bluesky, reddit, tiktok

Meta campaign budget updates via PUT /v1/ads/campaigns/{campaignId} now check the live campaign budget mode before applying changes.

This prevents stale local ABO/CBO state from incorrectly blocking updates, and a successful update will also repair local mirrored budget fields.

Key behavior:
• If the live campaign is CBO, sending budget (with type = daily | lifetime) can succeed even if local data previously indicated ABO.
• A live ABO campaign still returns 409 for campaign-level budget edits (use the ad-set budget endpoint instead).

Meta placement asset customization on POST /v1/ads/create now supports per-placement copy overrides.

You can pin different headline, body, and description per placement rule while keeping linkUrl and callToAction shared.

Use:
• placementAssets.defaultImageUrl
• placementAssets.rules[].placements
• placementAssets.rules[].imageUrl
• placementAssets.rules[].headline
• placementAssets.rules[].body
• placementAssets.rules[].description

Also updated: validateOnly: true now supports validating placementAssets for all-image setups (video placement validation still requires uploads).

You can now purchase an exact phone number by passing phoneNumber to POST /v1/phone-numbers/purchase (and the deprecated alias POST /v1/whatsapp/phone-numbers/purchase).

Pick a number from GET /v1/phone-numbers/available, then buy that specific E.164 number instead of getting an auto-assigned one.

New request field:
• phoneNumber (E.164, e.g. +14155552671)

New purchase failure case:
• 409 with code = PHONENUMBERUNAVAILABLE (number no longer available / rejected at buy-time)

GET /v1/phone-numbers/available results now include:
• numbers[].locality
• numbers[].bestEffort (true if carrier returned a number outside your requested filters)

Note: regulated countries that return 202 status = kyc_required do not support buying an exact phoneNumber.

GET /v1/analytics now supports sorting by two new metrics: completionrate and profileviews.

This lets you rank posts by TikTok (TikTok for Business app) completion and profile traffic directly in analytics queries.

Use sortBy:
• completion_rate
• profile_views

The delta feed GET /v1/analytics/delta also includes these fields in metrics: completionRate, profileViews.

POST /v1/inbox/conversations now supports WhatsApp CAROUSEL template sends via templateCards.

This lets you override per-card variables, header media, and buttons when sending a carousel template (card body variables restart at {{1}} per card, so they can’t be represented in the flat templateParams list).

Use templateCards (max 10), each item:
• cardIndex (0–9)
• params (card body variable values)
• headerMedia: type = image | video | document + (link or id)
• buttons (max 2): subType = quick_reply | url

Invalid carousel card overrides now return 400 with code = INVALIDTEMPLATECARD_PARAM.

Meta Ads business login connection flow now supports an automatic Page picker when multiple Facebook Pages are granted.

If a business-login connect results in multiple Pages, GET /v1/connect/meta-ads/callback may redirect to the Page picker instead of completing immediately.

Facebook Page selection endpoints now support a new business-login grant token:
• GET /v1/connect/facebook/select-page can be called with selectionToken (instead of profileId + tempToken)
• POST /v1/connect/facebook/select-page now accepts { selectionToken, pageId } to complete the business-login Meta Ads connection

Notes:
• selectionToken is encrypted and expires in 10 minutes
• Business selection requires session/bearer auth for the initiating user; X-Connect-Token is not accepted for the business selectionToken flow

POST /v1/ads/campaigns and POST /v1/ads/create now default Meta buyingType to AUCTION.

If you omit buyingType, Zernio will treat it as AUCTION and explicitly send it on new Meta campaigns (including validateOnly requests).

Set buyingType to:
• AUCTION
• RESERVED (Reach & Frequency; requires rfPredictionId on /v1/ads/create)

You can now pin/unpin TikTok comments (TikTok for Business–connected accounts only).

Pinning lets you keep a top-level comment at the top of the post’s comment section.

New endpoints:
• POST /v1/inbox/comments/{postId}/{commentId}/pin with body accountId
• DELETE /v1/inbox/comments/{postId}/{commentId}/pin with query accountId

TikTok Inbox support was also expanded:
• GET /v1/inbox/comments/{postId} now supports TikTok (TikTok for Business). Use commentId (query) to page a comment’s full replies; each top-level comment may include up to 3 inline replies.
• POST /v1/inbox/comments/{postId}/{commentId}/hide and DELETE /v1/inbox/comments/{postId}/{commentId}/hide now support TikTok (TikTok for Business).

Behavior change to handle:
• POST /v1/posts/sync-external may now return 409 with code adsconnectionrequired when the account is inactive/needs reconnection (stop scheduled retries until reconnected).

Webhook schema update:
• WebhookPayloadComment.comment.platform now includes tiktok (TikTok events may include only author id, without username/picture/owner flag).

New Tools endpoint: GET /v1/tools/tiktok/download.

It lets you fetch a TikTok video download URL or list available formats (uses Tools API access + Tools rate limit).

Key params:
• url (required)
• action: download | formats (default download)
• formatId (optional; from formats response)

Notes:
• Provider-side blocks/gateway failures can return 503; unavailable video returns 404.

Also: several Analytics/Accounts/Inbox endpoints now explicitly return 502/503 for upstream/temporary failures (handle retry/backoff). LinkedIn like endpoints now return alreadyReacted/reactionType on 200, and may return 409 when a different reaction already exists.

Added 4 new endpoints:

GET /v1/ads/pixels - List TikTok ad pixels
GET /v1/ads/partnership-content - List partnership ad content
GET /v1/ads/partnership-permissions - List partnership permissions
POST /v1/ads/partnership-permissions - Set partnership permission

Meta Ads now supports Business Login (system-user tokens) as an opt-in flow.

Use it to connect/reconnect metaads without creating/requiring a posting parent account, and to select a granted Facebook Page for creatives/lead forms.

Start the flow via GET /v1/connect/{platform}/ads with:
• platform: facebook | instagram
• loginMode: business (default: classic)
• optional pageId: ^\d+$

Complete the OAuth redirect via the new callback endpoint:
• GET /v1/connect/meta-ads/callback with state (required) and code (or error)
• On success it redirects (307) with connected=metaads, profileId, accountId

Notable behavior/errors:
• Business login always returns an authUrl; returns 503 if not configured
• Reconnect grant mismatches can return 409
• GET /v1/ads/accounts adds Meta fields businessId and businessName
• Lead forms/leads endpoints now accept a metaads business-login accountId (uses system-user token)

Google Ads now supports Performance Max creation via POST /v1/ads/create, and you can list created asset groups via GET /v1/ads/campaigns/{campaignId}/asset-groups.

This lets you create a PAUSED PMax campaign + asset group atomically (with optional validateOnly), then read back the linked text/image/YouTube assets for a campaign.

Create PMax by setting:
• campaignType = pmax
• assetGroup (required)
• budgetType = daily | lifetime
• status = PAUSED (PMax rejects ACTIVE)

Key assetGroup fields:
• finalUrl
• headlines (3-15)
• longHeadline
• descriptions (2-5)
• businessName
• images.landscape, images.square, images.logo (logo required)
• youtubeVideoId (optional)

List asset groups:
• GET /v1/ads/campaigns/{campaignId}/asset-groups returns assetGroups, cachedAt, stale (may serve cached data when Google quota is exhausted).

New endpoint: POST /v1/ads/accounts creates a durable Meta ad account in the user’s business portfolio using their connected Meta Ads token.

Use it to self-serve ad account creation (note: the account starts without a payment method; the user must add payment/invoicing in Ads Manager before ads can deliver).

Required body fields: accountId, businessId, name, currency, timezoneId (Meta numeric timezone ID).

Optional fields include endAdvertiser, mediaAgency, partner (default NONE), plus invoicing options like invoice, invoiceGroupId, invoicingEmails, io, poNumber, fundingId.

Response 201 returns adAccountId (e.g. act_...), connectionUpdated, paymentMethodRequired, adsManagerUrl, nextSteps, warnings.

Important: this operation is not idempotent. After a timeout or 502 with details.creationStatus=unknown, check Ads Manager before retrying.

Phone number availability now indicates when an out-of-stock country/type can be pre-ordered.

If available is false but preOrderable is true, you can still proceed with KYC and the carrier will source the number after review (typically ~3 weeks; not guaranteed). Only document tiers (3/4) qualify.

New fields:
• GET /v1/phone-numbers/availability (+ deprecated alias /v1/whatsapp/phone-numbers/availability): preOrderable
• GET /v1/phone-numbers/countries: preOrderable and per-type types[].preOrderable, plus types[].fulfilment = instant | request (and types[].tier may be null for fulfilment: request)
• POST /v1/phone-numbers/kyc (+ deprecated alias /v1/whatsapp/phone-numbers/kyc): response adds preOrder (true when the submission placed a pre-order; pre-orders are 1 number and aren’t billed until active)

Note: POST /v1/phone-numbers/stock-watches is now mainly for true stock returns; if preOrderable is true, you can submit KYC instead of creating a watch.

WhatsApp messages can now include location pins in the message.received webhook via metadata.location.

This lets you read the shared coordinates directly from the webhook (the message text is only the preview like 📍 <name>).

New field:
• metadata.location with latitude, longitude, name, address

Also, message.sent webhook metadata now includes WhatsApp context so you can detect non-text sends without a GET:
• metadata.location
• metadata.contacts
(Existing fields like metadata.quotedMessageId and metadata.threadTs are unchanged.)

Google Ads now supports managing extension assets (sitelinks, callouts, structured snippets) at account, campaign, and ad-group levels, plus richer Google RSA reads/updates.

New asset endpoints:
• Campaign assets: GET /v1/ads/campaigns/{campaignId}/assets, PUT, DELETE
• Ad-group assets: GET /v1/ads/ad-sets/{adSetId}/assets, POST, PUT, DELETE
• Account assets:
- Callouts: GET /v1/ads/accounts/callouts, POST, PUT, DELETE
- Sitelinks: GET /v1/ads/accounts/sitelinks, POST, PUT, DELETE
- Structured snippets: GET /v1/ads/accounts/structured-snippets, POST, PUT, DELETE

Key request params:
• accountId (required) and optional customerId (required when the connection has multiple customers)

Notes:
• List endpoints may return cache metadata: cachedAt and stale
• Asset updates are in-place via updates[] (max 20) with assetResourceName; assets are shared, so edits affect all attachments
• Removes detach only (assets themselves can’t be deleted)

Google RSA changes:
• GET /v1/ads/{adId} may now include top-level cachedAt and stale for Google RSA enrichment
• PUT /v1/ads/{adId} now supports Google RSA text updates via top-level headlines, descriptions, finalUrls (each array replaces the full list; omit a field to keep it). Pinning uses pinnedField: HEADLINE1 | HEADLINE2 | HEADLINE3 and DESCRIPTION1 | DESCRIPTION_2.

TikTok Ads now supports ad comment moderation via new endpoints for replying, hiding/unhiding, and deleting comments.

This lets you moderate first-level TikTok ad comments directly from the Ads API (replies-to-replies are rejected; reply is not idempotent).

New endpoints:
• POST /v1/ads/{adId}/comments/{commentId}/reply with text
• POST /v1/ads/{adId}/comments/{commentId}/hide with hidden (true/false)
• DELETE /v1/ads/{adId}/comments/{commentId}

All three support TikTok comment lookup window params since/until (max 30 days; defaults to last 30 days).

Also updated: GET /v1/ads/{adId}/comments now supports TikTok (adds since/until; placement is Meta-only and returns 400 for TikTok). TikTok replies are returned as separate comments with parentId.

Meta Ads additions for app-promotion setup:
• GET /v1/ads/instagram-accounts (discover IG ad identities)
• GET /v1/ads/advertisable-applications
• GET /v1/ads/ios-fourteen-campaign-limits

Campaign creation update (Meta): POST /v1/ads/campaigns adds validateOnly, plus SKAdNetwork/app-promotion fields isSkadnetworkAttribution, promotedObject, and buyingType (AUCTION/RESERVED).

Meta ads now support explicit Promotions and Advantage+ creative enhancements across create/update flows, with a promotion readback status.

You can attach an offer via promotion and control enhancements via creativeFeatures. When promotion is used, responses include promotionStatus to indicate whether Meta returned promotion metadata.

Use:
• POST /v1/ads/create: promotion, creativeFeatures (also as defaults for creatives[]; per-item override supports promotion: null)
• POST /v1/ads/creatives: promotion, creativeFeatures (response adds promotion, promotionStatus)
• PUT /v1/ads/{adId}: creative.promotion, creative.creativeFeatures (send promotion: null to remove)

promotionStatus values: applied | not_returned | unavailable

Also:
• GET /v1/ads/{adId} adds refreshPromotion=true|false to read live Meta promotion metadata and include promotionStatus.
• POST /v1/ads/{adId}/duplicate now preserves Meta-returned creative settings (including promotion metadata and creativeFeatures) when a native copy requires a creative rebuild.

Meta messaging boosts via POST /v1/ads/boost now require an explicit messaging CTA; destinationType no longer auto-selects one.

This prevents accidental messaging-boost behavior when you only intended to set an ad-set destination, and makes CTA/destination handling more predictable.

Key changes:
• Messaging boosts must use goal=engagement with callToAction in WHATSAPPMESSAGE | MESSAGEPAGE | INSTAGRAM_MESSAGE
• destinationType is now independent for non-messaging CTAs; if you do use a messaging callToAction, any explicit destinationType must match
• whatsappPhoneNumber now requires callToAction=WHATSAPP_MESSAGE (not just destinationType=WHATSAPP)

Also: Ad.creative.whatsappPhoneNumber is now returned (when provided) so you can read back the explicit WhatsApp number used on Meta boosts/messaging ads.

Google Ads now supports shared negative keyword lists (create/list/get/update/delete), including attaching lists to campaigns and replacing the full keyword set.

Use:
• GET /v1/ads/accounts/negative-keyword-lists (cached ~10 min; may return stale=true)
• POST /v1/ads/accounts/negative-keyword-lists (not idempotent)
• GET /v1/ads/accounts/negative-keyword-lists/{listId}
• PUT /v1/ads/accounts/negative-keyword-lists/{listId} (rename)
• DELETE /v1/ads/accounts/negative-keyword-lists/{listId}
• PUT /v1/ads/accounts/negative-keyword-lists/{listId}/keywords (replace full set; keywords max 5000)
• GET /v1/ads/campaigns/{campaignId}/negative-keyword-lists
• PUT /v1/ads/campaigns/{campaignId}/negative-keyword-lists (replace associations; listIds max 20)

Key inputs:
• accountId (required on account-scoped routes)
• customerId (required when a connection has multiple customers)
• platform=google (other platforms return 501)
• Keyword matchType: broad | phrase | exact

Google campaign updates now support daily budget via PUT /v1/ads/campaigns/{campaignId}. Shared budgets return 409 unless allowSharedBudgetUpdate=true is explicitly provided.

Campaign analytics for Google now includes impression share ratios in analytics.summary (searchImpressionShare, searchBudgetLostImpressionShare, searchRankLostImpressionShare, searchTopImpressionShare, searchAbsoluteTopImpressionShare) plus analytics.impressionShareCache.{cachedAt,stale}; may return 429 if quota is exhausted without a cached result.

Meta boosts now support messaging boosts and WhatsApp number selection:
• POST /v1/ads/boost adds destinationType=INSTAGRAMDIRECT and whatsappPhoneNumber (E.164), and supports messaging CTAs (WHATSAPPMESSAGE | MESSAGEPAGE | INSTAGRAMMESSAGE) with goal=engagement.

Messaging/CTWA ad creation now supports reusing existing posts:
• POST /v1/ads/messaging and POST /v1/ads/ctwaexistingPostId or objectStoryId (mutually exclusive with fresh creative fields), plus optional whatsappPhoneNumber` for WhatsApp destination.

The bootstrap flow for GET /v1/analytics/delta has changed: take the cursor before loading your baseline.

To avoid missing changes during initial sync, first call GET /v1/analytics/delta with no cursor to capture nextCursor, then load the baseline via GET /v1/analytics, then resume the delta feed from that captured nextCursor.

Key behavior:
• Bootstrap: omit cursor → response has empty data + nextCursor
• Resume: pass cursor=<nextCursor> verbatim (opaque)
• Retention: cursors older than ~6 days return 400; recover by repeating the same bootstrap order

Google Ads now supports the attach flow on POST /v1/ads/create via adSetId.

You can add a new ad into an existing Google Ads ad group (inherits the ad group’s budget/targeting), instead of creating a new campaign/ad group.

Use:
• adSetId (Google AD GROUP id)
• campaignType: search | display (default display)

Notes:
• goal is still required even though budget/targeting are inherited
• In attach mode, budgetAmount/budgetType and bidding fields (bidStrategy, bidAmount, portfolioBidStrategyId) return 400
• For Search ad groups, set campaignType to search (otherwise it’s treated as Display and requires images.landscape + images.square + businessName)

GET /v1/ads/audiences/{audienceId} response renamed metaData to platformData.

This field still contains fresh data from the underlying ads platform API (when available), but clients must now read platformData instead of metaData.

Also clarified across audience endpoints that {audienceId} is the Zernio audience id (audiences[].id from GET /v1/ads/audiences), not the platform segment id. audiences[].id can be null when the audience wasn’t created through Zernio.

WhatsApp BYO numbers now support Meta re-verification via 2 new endpoints: POST /v1/accounts/{accountId}/whatsapp/request-code and POST /v1/accounts/{accountId}/whatsapp/verify-code.

Use this when Meta demotes a migrated/bring-your-own number to re-verification: request an OTP to the customer handset, then submit it to verify with Meta (and call POST /v1/accounts/{accountId}/whatsapp/register afterward to complete Cloud API activation).

Request a code with optional:
• method: SMS | VOICE
• language (Meta locale, e.g. en_US)

Verify with:
• code (6 digits; separators like 749-456 are accepted)

Note: request-code is rate-limited to 1 request per 10 minutes per account and may return 429 with Retry-After.

Reddit posting behavior has changed for forceSelf and nativeVideo in RedditPlatformData.

forceSelf now creates a text-only self post and skips native media uploads even if media is provided. For native video with body text, omit forceSelf and provide content plus a video mediaItem.

nativeVideo fallback behavior is now stricter when body text is present: if the post includes body text, upload failures or subreddit video restrictions will fail the post instead of falling back to a link. Automatic link fallback applies only when there is no body text.

WhatsApp connect now supports a hosted Embedded Signup flow to avoid double-selection when a Facebook login can access multiple WhatsApp numbers.

Start it with GET /v1/connect/whatsapp + signup=hosted (optional onboarding: api | business_app). The returned authUrl points to a Zernio-hosted page (no state in the response).

You can co-brand the hosted page using:
• brandName
• primaryColor (hex #RRGGBB)
• language: en | es

New endpoint: GET /v1/connect/whatsapp/sdk-config returns the Embedded Signup config (appId, configId, branding). Auth via API key or X-Connect-Token.

POST /v1/connect/whatsapp/embedded-signup now also supports the hosted flow:
• Auth via API key or X-Connect-Token
• Request adds redirectUrl and echoConnectToken
• Response adds account and optional redirectUrl

Hosted flow adds two WhatsApp error values you may see on redirect: connectioncancelled, sessionexpired.

PUT /v1/posts/{postId} can now return 409 when the requested scheduledFor collides with another post already occupying that slot in the same queue (code: queueslotconflict).

This lets clients distinguish queue slot conflicts from generic validation errors and handle rescheduling explicitly.

If you hit 409, you can:
• choose a different scheduledFor
• omit scheduledFor to let the queue pick the next open slot
• send queueId: null to schedule outside the queue

Meta generic templates now support setting the image aspect ratio on Facebook via imageAspectRatio.

This lets you control how Messenger renders carousel element images (default is horizontal). Note: Instagram does not support this setting and will return 400 if it’s included.

Use template.imageAspectRatio with:
• horizontal
• square

Applies to:
• POST /v1/inbox/conversations/{conversationId}/messages (generic template)
• CommentAutomationTemplate.imageAspectRatio

WhatsApp templates now support configuring a per-template delivery TTL via messagesendttl_seconds.

This lets you set a validity window for template messages (messages not delivered within the TTL are dropped) and read back the custom TTL when it’s set.

Set messagesendttl_seconds on:
• POST /v1/whatsapp/templates
• PATCH /v1/whatsapp/templates/{templateName}
• PATCH /v1/whatsapp/templates/id/{templateId}

Read messagesendttl_seconds from:
• GET /v1/whatsapp/templates
• GET /v1/whatsapp/templates/{templateName}
• GET /v1/whatsapp/templates/id/{templateId}

TTL ranges by category:
• AUTHENTICATION: 30–900
• UTILITY: 30–43200
• MARKETING: 43200–2592000

Use -1 to restore the category default (for AUTHENTICATION and UTILITY).

GET /v1/ads/library now supports searching Meta’s Ad Library without a connected account.

Meta searches run using Zernio’s developer access, so you can call the endpoint with platform=meta and omit accountId. LinkedIn searches still require a connected accountId.

Use:
• platform: meta | linkedin (required unless accountId is provided)
• accountId: required for LinkedIn; optional for Meta (passing a Meta account also selects Meta)

Meta-specific behavior changes:
• Requests may return 429 due to shared Meta quota (back off ~1 minute)
• New 503 when Meta Ad Library is unavailable on Zernio’s side (PLATFORM_DISABLED)

Also updated: 403 no longer includes Meta identity confirmation errors; it’s now “Ads access required” (legacy plans may need the Ads add-on).

Several Google Ads endpoints now serve cached data (with fallback when Google quota is exhausted), and responses include freshness metadata.

These reads may no longer be strictly live; when quota is exhausted, the API can return the last-good copy instead of failing.

New response fields:
• cachedAt (date-time | null) — when the data was fetched from Google
• stale (boolean) — true when quota was exhausted and the response is a cached fallback

Applies to:
• GET /v1/ads/search-terms
• GET /v1/ads/bid-strategies
• GET /v1/ads/campaigns/{campaignId}/bidding
• GET /v1/ads/campaigns/{campaignId}/negative-keywords
• GET /v1/ads/campaigns/{campaignId}/targeting
• GET /v1/ads/accounts/callouts
• GET /v1/ads/accounts (Google only)
• GET /v1/ads/conversions/actions

Also: PUT /v1/ads/campaigns/{campaignId}/targeting now returns the refreshed devices/locations/languages state read back from Google after the edit (and invalidates the cached GET copy).

Google Ads now supports portfolio bid strategies and live campaign bidding reads.

You can list/create/update shared (portfolio) bidding strategies and attach them to campaigns, plus fetch a campaign’s current bidding setup for pre-filling edit forms.

New endpoints:
• GET /v1/ads/bid-strategies (accountId, optional customerId, fromDate, toDate)
• POST /v1/ads/bid-strategies (accountId, name, type, optional targetCpa/targetRoas)
• PATCH /v1/ads/bid-strategies/{strategyId} (accountId, optional name, type, targetCpa, targetRoas)
• GET /v1/ads/campaigns/{campaignId}/bidding (accountId, platform=google, optional customerId)

Attach a portfolio strategy to Google campaigns using portfolioBidStrategyId on:
• POST /v1/ads/campaigns
• PUT /v1/ads/campaigns/{campaignId}
• POST /v1/ads/create

Portfolio strategy type values:
• TARGETCPA, TARGETROAS, MAXIMIZECONVERSIONS, MAXIMIZECONVERSION_VALUE

Also on Google ad updates, PUT /v1/ads/{adId} now supports device bid adjustments via targeting.devices with devices MOBILE, DESKTOP, TABLET, CONNECTED_TV (optional bidModifier 0.1–10).

Google Ads now supports editing more campaign and account assets via new endpoints.

You can now read/update campaign targeting (devices, locations, languages), create/list standalone ad groups, manage account-level callout extensions, and list/create conversion actions (with tag snippets).

Campaign targeting:
• GET /v1/ads/campaigns/{campaignId}/targeting (platform=google)
• PUT /v1/ads/campaigns/{campaignId}/targeting body: platform=google, targeting with any of devices/locations/languages (each provided field replaces existing)
• devices enum: MOBILE, DESKTOP, TABLET, CONNECTED_TV

Ad groups (ad sets):
• GET /v1/ads/ad-sets (filters: accountId, campaignId, platform)
• POST /v1/ads/ad-sets (Google-only) with optional Idempotency-Key

Account-level callouts (Google-only):
• GET /v1/ads/accounts/callouts
• POST /v1/ads/accounts/callouts (callouts: 1–25 chars, up to 20)
• DELETE /v1/ads/accounts/callouts (remove by assetId)

Conversion actions (Google-only):
• GET /v1/ads/conversions/actions (optional customerId, optional type)
• POST /v1/ads/conversions/actions create type=WEBPAGE and returns tagSnippets

Also updated:
• POST /v1/ads/create now supports Google campaign language targeting via languages (e.g. ["en","de"]; unknown codes return 400)
• GET /v1/ads/targeting/search adds dimension=language (Google-only) to resolve Google language_constant options

Google Ads Search keyword management is now available via new endpoints.

You can add keywords without replacing the existing set, pause/enable a keyword, remove a keyword, and manage campaign-level negative keywords separately from ad-group negatives.

Add keywords to an ad group with POST /v1/ads/keywords using:
• accountId
• adSetId
• keywords (string = BROAD, or { text, matchType } where matchType is exact/phrase/broad)
• negative (boolean) to add ad-group-level negatives

Pause/enable a keyword with PATCH /v1/ads/keywords/{keywordId}:
• status: active or paused (note: negative keywords can’t be paused/enabled)

Remove a keyword with DELETE /v1/ads/keywords/{keywordId}.

Campaign-level negative keywords:
• List: GET /v1/ads/campaigns/{campaignId}/negative-keywords
• Replace full set: PUT /v1/ads/campaigns/{campaignId}/negative-keywords with keywords (send an empty array to clear all)

Also updated: POST /v1/ads/create (Google Search) now accepts match types for keywords and negativeKeywords via KeywordEntry, and adds campaignNegativeKeywords for campaign-level negatives at create time.

GET /v1/ads/timeline now returns allConversions per day, and clarifies Google customer-level reporting when adAccountId is a Google customer id.

This lets you chart Google’s “all conversions” alongside conversions (tracked conversions), matching Google Ads’ metrics.all_conversions.

New field in each rows[] item:
• allConversions - all conversions (0 on platforms without this concept)

Google note:
• With adAccountId set to a Google customer id, the timeline represents customer-level performance (clicks, cost, impressions, conversions, allConversions per day).

New endpoint GET /v1/ads/library is available to search the public Ad Library for competitor/market research using your connected account token.

It supports both Meta and LinkedIn and returns ads in the platform’s raw shape under data, with pagination via paging.after (cursor; null when exhausted).

Required: accountId
Common query params: q, countries, since, until, limit, after
Meta-only: pageIds, adType (ALL/POLITICALANDISSUEADS/HOUSINGADS/EMPLOYMENTADS/FINANCIALPRODUCTSANDSERVICESADS), status (ACTIVE/INACTIVE/ALL), platforms, mediaType (ALL/IMAGE/MEME/VIDEO/NONE), languages, searchType (KEYWORDUNORDERED/KEYWORDEXACTPHRASE), fields
LinkedIn-only: advertiser (and limit max is 25)

Notes: Passing a platform-unsupported param returns 400 naming the param. Meta may return 403 metaidentityconfirmation_required until the Facebook user behind the connection confirms identity/location.

Also: POST /v1/inbox/comments/{postId}/{commentId}/private-reply now documents an additional Instagram failure case as a non-retryable 400 when Meta declines the private reply (subcode 2534066).

POST /v1/phone-numbers/stock-watches now supports watching stock by number type via numberType.

You can create a watch for a specific type in a country, or omit numberType to watch all types. Watches are now unique per country + numberType (up to 20 watches total).

Request body:
• country
• numberType (optional): local | mobile | national | toll_free

Response schema PhoneNumberStockWatch now includes required numberType (nullable; null means “all types”).

POST /v1/inbox/conversations/{conversationId}/messages now includes a documented 500 response when the upstream platform rejects or fails the send.

This clarifies that Zernio does not retry sends internally, and that retrying after a 500 can result in duplicate messages because upstream failures may be ambiguous.

Key response:
• 500 - platform rejected/failed the send; retry only if duplicates are acceptable (use Idempotency-Key to protect the “response lost after success” case, but it won’t guarantee safety after an upstream-accepted failure).

Meta ad sets now support minimum spend targets via platformSpecificData on PUT /v1/ads/ad-sets/{adSetId} and when creating Meta ads via POST /v1/ads/create.

This lets you reserve a share of a CBO (campaign-level) budget for a specific ad set using Meta’s dailyminspendtarget / lifetimeminspendtarget.

Set one of:
• platformSpecificData.dailyMinSpendTarget
• platformSpecificData.lifetimeMinSpendTarget

Notes:
• dailyMinSpendTarget and lifetimeMinSpendTarget are mutually exclusive (400)
• Requires campaign-level budget (CBO); on an ABO ad set this is rejected (PUT returns 409; create returns 400)
• Read back via GET /v1/ads/ad-sets/{adSetId}?fields=dailyminspendtarget (or lifetimeminspendtarget)

GET /v1/ads/tree: the ads array in AdTreeAdSet is now explicitly defined as the 100 highest-spending ads over the requested date range when an ad set has more than 100 ads.

This means the contents of AdTreeAdSet.ads can change based on fromDate/toDate; use adCount for the true total size of the ad set.

Key fields: AdTreeAdSet.ads, fromDate, toDate, adCount

WhatsApp Flows now supports managing the Flows endpoint encryption key via new endpoints.

You can check whether a business RSA public key is registered (and retrieve it) and register/replace the key used for endpoint-backed flows (flowaction: dataexchange).

New endpoints:
• GET /v1/whatsapp/flows/encryption-key (query accountId) returns publicKey, registered, signatureStatus (VALID | MISMATCH)
• POST /v1/whatsapp/flows/encryption-key body: accountId, businessPublicKey (PEM)

Note: only one key is active per phone number; replacing the key requires your flow endpoint to serve the matching private key or data_exchange flows will fail at runtime.

Meta ads created via POST /v1/ads/create now support Multiple Text Options (Advantage+ Flexible Format) using new top-level fields bodies, headlines, and optional descriptions.

This lets you send 1–5 variations of primary text/headlines (and optionally descriptions) and have Meta optimize delivery across them, without using full dynamicCreative.

Use:
• bodies (1–5)
• headlines (1–5)
• descriptions (0–5)

Requires imageUrl or video, plus linkUrl and callToAction. When set, top-level body and headline are used for preview text (objectstoryspec), and this mode is mutually exclusive with dynamicCreative, placementAssets, carouselCards, and creatives[].

Instagram publishing now supports paid partnership, sponsor tagging, comment toggling, and location tagging via new fields in platformSpecificData.

Use:
• isPaidPartnership (boolean) — adds the “Paid partnership” label (feed/Reels/carousels; Stories return 400). Requires Facebook Login connection.
• brandedContentSponsors (array, max 2) — tag sponsor brands by username (optional @) or numeric IG user ID; implies isPaidPartnership.
• commentsEnabled (boolean, default true) — when false, turns off comments after publish (best-effort; Stories ignored).
• locationId (string digits) — tags the post location using a Facebook Page ID with location data (feed/Reels/carousels; Stories rejected with 400).

Meta ads now support regional regulation identity mapping via regionalRegulationIdentities on POST /v1/ads/create and POST /v1/ads/boost.

When you include regionalRegulatedCategories (e.g. BRAZILREGULATION, SINGAPOREUNIVERSAL, TAIWANUNIVERSAL, THAILANDUNIVERSAL, AUSTRALIAFINSERV, INDIAFINSERV, TAIWAN_FINSERV), you can now pass the required Meta-verified beneficiary/payer entity IDs in regionalRegulationIdentities.

Set:
• regionalRegulatedCategories: [...]
• regionalRegulationIdentities: { universalbeneficiary: 123, universalpayer: 456, ... }

If omitted, Meta may use Ads Manager defaults when configured.

New endpoint GET /v1/analytics/delta returns a cursor-based feed of analytics snapshots that changed across all readable accounts.

This lets integrations stay in sync with far fewer calls than polling GET /v1/analytics per account; bootstrap once from GET /v1/analytics, then poll deltas.

Key params:
• cursor (opaque; omit to start “from now” and receive data: [] + nextCursor)
• limit (1–100, default 50; out-of-range = 400)
• platform (optional)
• profileId (default all)

Response fields:
• data (oldest-first changed snapshots)
• nextCursor (always present, even on empty pages)
• hasMore (if true, call again immediately)

New webhook event available for subscriptions: analytics.synced. It’s a trigger (no metrics/cursor); on receipt, call GET /v1/analytics/delta using your last stored nextCursor.

Instagram comment-to-DM private replies may now fail for non-followers when you include interactive elements.

Since late Aug 2026, Instagram can refuse buttons (and other attachments/cards) to commenters who don’t follow the account, returning a non-retryable 400 (Meta code 2, subcode 1545133). The failed call still consumes the comment’s single private reply.

If you need to reach non-followers, send plain text using message only, then add buttons after they reply. (quickReplies and buttons remain mutually exclusive.)

Meta ads now accept regional regulated categories on ad set creation/boosting.

Use this when targeting countries where Meta requires extra regulation flags (e.g. Singapore/Taiwan/Thailand/Australia/India). Without it, Meta may reject the ad set.

Send regionalRegulatedCategories (array of strings) on:
• POST /v1/ads/create
• POST /v1/ads/boost

Example values include SINGAPOREUNIVERSAL, TAIWANUNIVERSAL, THAILANDUNIVERSAL, AUSTRALIAFINSERV, INDIA_FINSERV.

Several Ads endpoints can now return 403 with code adsallowanceexceeded.

This happens when a team has no payment method on file and has reached the 500 free live ads limit; add a card to resume/continue.

You may see this on:
• PUT /v1/ads/campaigns/{campaignId}/status
• PUT /v1/ads/campaigns/{campaignId}
• POST /v1/ads/campaigns/bulk-status
• POST /v1/ads/campaigns/{campaignId}/duplicate
• POST /v1/ads/ad-sets/{adSetId}/duplicate
• POST /v1/ads/{adId}/duplicate
• PUT /v1/ads/ad-sets/{adSetId} and PUT /v1/ads/ad-sets/{adSetId}/status
• PUT /v1/ads/{adId} and PUT /v1/ads/{adId}/status
• PATCH /v1/ads/{adId}/tracking-tags
• POST /v1/ads/create
• POST /v1/ads/boost
• POST /v1/ads/messaging, POST /v1/ads/call, POST /v1/ads/ctwa
• POST /v1/ads/campaigns/{campaignId}/assets

If you have retry logic, treat 403 adsallowanceexceeded as non-retryable until billing is set up.

GET /v1/connect/pending-data pending OAuth tokens are now repeatable and expire 1 hour after issuance (previously one-time use, 10 minutes).

This makes headless OAuth selection flows more resilient (you can re-fetch the pending selection data until the user completes selection; completion deletes the pending record).

Use token (query) from pendingDataToken on the redirect. selectionType can be: organizations, pages, boards, locations, profiles.

Scope note: this pending-data flow now covers Google Business locations and Slack channels in addition to existing large selection lists.

GET /v1/ads now supports filtering by Meta ad set via adSetId.

This makes it easier to build adset-centric dashboards by listing only ads within a specific platform ad set.

Use adSetId (platform ad set id) alongside existing filters like campaignId.

PUT /v1/ads/{adId} now supports richer creative updates, especially for Meta.

Meta creative updates are now patch-style: send any subset of creative fields and omitted fields are preserved (including existing media), and you can also repoint an ad to an existing creative.

Key Meta-only options in creative:
• description (link description)
• videoId (reuse an already-uploaded video)
• existingCreativeId (repoint to a creative from GET /v1/ads/creatives; ignores other creative fields)

GET /v1/ads/targeting/search now supports Meta work demographics via dimension values workPosition, workEmployer, workIndustry.

These ids can be used in TargetingSpec as:
• workPositions
• workEmployers
• workIndustries

Also, TargetingSpec audience lists are now supported: audienceInclude and audienceExclude accept platform audience IDs (not supported on OpenAI Ads; returns 400).

WhatsApp template sends via POST /v1/inbox/conversations now validate templateParams more strictly for positional templates.

If you provide fewer values than the template’s required header + body + dynamic URL-button slots, the request is rejected with 400 (INVALIDTEMPLATEPARAMS) instead of sending a message with misaligned values.

Key fields:
• templateParams - must cover all required slots for positional templates
• templateButtonParams - can override a button’s value; overridden buttons may not need a value in templateParams unless later uncovered dynamic URL buttons follow

Creating or retrying posts can now return 403 with code=ACCOUNTNOTENABLEDFORPOSTING.

This happens when the target accountId is connected for ads only (i.e., enabled: false) and cannot be posted to. Connect the account as a posting account, refresh IDs via GET /v1/accounts, then retry.

Applies to:
• POST /v1/posts (403 code enum now includes ACCOUNTNOTENABLEDFORPOSTING)
• POST /v1/posts/{postId}/retry (403 may include ACCOUNTNOTENABLEDFORPOSTING, PROFILEOVERLIMIT, or insufficient_permissions)

Some endpoints now return additional billing/capability errors you may need to handle.

Posts listing may now fail with 403 when X analytics isn’t enabled for the account (code XANALYTICSNOT_ENABLED) on GET /v1/accounts/{accountId}/posts.

OpenAI Ads connect may now return 402 PaymentRequired on POST /v1/connect/openai-ads/credentials.

SMS sender ID creation now has explicit billing-related failures on POST /v1/sms/sender-ids:
• 402 (code payment_required) when no payment method is on file
• 409 (code billingsetupincomplete) when billing setup is incomplete

PostAnalytics.follows can now be null in GET /v1/analytics responses.

This affects Instagram where Meta doesn’t expose follows for Reels and non-Reels video; in those cases Zernio will return null instead of 0. Update your parsing/aggregation to handle follows: null (treat as “unknown/not available”, not zero).

WhatsApp templates now support working with a specific Meta template variant via its Meta template id.

New endpoints:
• GET /v1/whatsapp/templates/id/{templateId} (requires accountId)
• PATCH /v1/whatsapp/templates/id/{templateId} (body: accountId, components)
• DELETE /v1/whatsapp/templates/id/{templateId} (requires accountId)

Template listing and name-based operations are now language-aware (Meta stores templates per name + language):
• GET /v1/whatsapp/templates adds filters: name, language, status (APPROVED/REJECTED/PENDING/PAUSED/DISABLED/INAPPEAL/PENDINGDELETION)
• GET /v1/whatsapp/templates/{templateName} adds optional language; if multiple variants exist and no language is provided, it can return 409 ambiguous_template with details.languages
• PATCH /v1/whatsapp/templates/{templateName} now takes language in the request body (required when multiple variants exist); missing language can return 409 ambiguous_template

Delete behavior change:
• DELETE /v1/whatsapp/templates/{templateName} without language deletes all language variants; with language it deletes only that variant and returns scope = all_languages or language.

WhatsApp sends via POST /v1/inbox/conversations/{conversationId}/messages now document a per-recipient rate limit.

If you send bursts to the same recipient, WhatsApp may reject excess messages with Meta error code 131056 ("Too many messages sent to this recipient"). Pace sends to a single recipient to ~10/min; sends to other recipients are unaffected.

If you see 400 responses with platformError.code = 131056, throttle per recipient and retry later.

Phone number stock watches are now available via new endpoints: GET /v1/phone-numbers/stock-watches, POST /v1/phone-numbers/stock-watches, DELETE /v1/phone-numbers/stock-watches/{id}.

You can watch an out-of-stock country and get notified the first time deliverable numbers are available again (email + webhook). Watches are checked every 6h, consumed when they fire, and you can watch up to 20 countries.

Create a watch with country (ISO 3166-1 alpha-2). Responses: 201 created, 200 if it already existed, 409 if the country is currently in stock or the 20-country limit is reached.

Webhooks now support the new event phonenumber.stockavailable in events (for POST /v1/webhooks/settings and PUT /v1/webhooks/settings). Payload includes stock.country and stock.types[] with numberType (local/mobile/national/toll_free) and availableCount.

GET /v1/usage metering mode now supports spend attribution by profile/account, plus optional projection onto a single profile or account.

This lets you break down billed spend (USD) across profiles/accounts for a given window, or fetch the metering payload scoped to one group for chargeback/reporting.

New query params (metering mode):
• groupBy: profile | account (adds attribution)
• profileId: project results onto one profile (pair with range)
• accountId: project results onto one account (pair with range)

New response fields in UsageMetering:
• attribution (with groupBy, groups, unattributed, totals, restricted)
• scope (present with profileId/accountId)

Note: when profileId or accountId is set, peaks, callUsage, and tax return null (workspace-level only).

New endpoint: GET /v1/accounts/{accountId}/youtube-captions to fetch a YouTube video transcript (plain text plus timed cues), including auto-generated (asr) and uploaded (standard) tracks.

Supports cached reads to avoid repeated YouTube calls; response includes source = cache | youtube and fetchedAt. Use refresh=true only when captions changed (re-downloads from YouTube).

Key params:
• accountId (path)
• videoId (query, required)
• language (query, optional; BCP-47)
• format (query) = json | srt (default json)
• refresh (query, boolean)

Response highlights: trackKind = asr | standard, cues (when format=json), srt (when format=srt), and availableTracks for language selection.

New endpoint: DELETE /v1/ads/ad-sets/{adSetId} deletes an ad set on the platform and cancels its ads locally (it never deletes the campaign).

Provide the ad set ID via adSetId (path).

Response includes deleted and adCount (number of local Ad documents marked status: cancelled). Returns 501 if deletion isn’t supported on the target platform.

Instagram is now supported (limited release) for liking/unliking posts and comments via:
• POST /v1/inbox/posts/{postId}/like, DELETE /v1/inbox/posts/{postId}/like
• POST /v1/inbox/comments/{postId}/{commentId}/like, DELETE /v1/inbox/comments/{postId}/{commentId}/like

This enables engagement actions on Instagram feed media (posts/reels/carousels) and their comments/replies, but access is currently restricted by Meta permissions.

Instagram requirements/behavior:
• Requires permission instagrammanageengagement
• Only works for accounts connected via Facebook Login; Instagram Login returns 400 with code instagramlikesrequirefacebooklogin
• Accounts whose token predates the permission return 403 with code reconnect_required
• Limited release: non-allowed accounts return 403 with code PLATFORMBETARESTRICTED
• Burst limit: 50 like/unlike calls per 5s per Instagram account; exceeding can lock likes for 1 hour

Also note: these endpoints’ 403 may now indicate missing platform permission (not only Inbox add-on).

PlatformTarget.platformSpecificData is now returned as a free-form object (with additionalProperties: true) instead of a oneOf union of *PlatformData schemas.

This avoids generated clients failing to deserialize PlatformTarget responses when platformSpecificData doesn’t match exactly one variant. Treat platformSpecificData as an untyped JSON object on responses (it may be omitted rather than returned as an empty object).

WhatsApp inbox conversation creation now supports sending values for template buttons that carry their own payload (copy-code / flow tokens), via templateButtonParams on POST /v1/inbox/conversations.

Use this when your approved WhatsApp template has buttons that need a per-send value (e.g. Pix copy-and-paste code, coupon code, Flow token). This complements templateParams (text variables + dynamic URL buttons).

Set templateButtonParams as an array of:
• index (0-9)
• subType: url | copy_code | flow
• value

Message lineage is now exposed as sentVia on GET /v1/inbox/conversations/{conversationId}/messages and on the message.sent webhook, with values:
human | api | broadcast | sequence | workflow | comment_automation | bulk-api | null

Note: existing stored messages are not backfilled; treat sentVia: null as “unknown”.

DELETE /v1/ads/campaigns/{campaignId} now accepts platform=google.

You can delete Google campaigns using the same endpoint and request body shape as Facebook/Instagram.

Set platform to one of: facebook, instagram, google

For empty campaigns (0 ads), include accountId to allow deletion: accountId (Zernio SocialAccount id).

GET /v1/whatsapp/template-library now supports selecting a specific language variant via an optional language query param.

This lets you request a desired locale (e.g. es, en_US); if it’s not available, the API returns the first available variant and reports the actual variant in template.language.

New:
• Query param: language
• Response field: template.availableLanguages (array of supported language codes)

GET /v1/users now returns lastLoginAt for each user.

This lets you track recent workspace sign-ins (stamped at most once per hour). The field may be omitted for users with no recorded sign-in since it was introduced.

New field:
• users[].lastLoginAt

The message.sent webhook payload now supports more platforms and can include send context in a new metadata object.

Updated enum:
• message.platform: instagram, facebook, telegram, whatsapp, twitter, reddit, bluesky, slack

New optional fields:
• metadata.quotedMessageId
• metadata.threadTs (Slack only)

You can now fetch a single Google Business Profile review by ID via GET /v1/accounts/{accountId}/gmb-reviews/{reviewId}.

This returns one review in the same shape as the items from GET /v1/accounts/{accountId}/gmb-reviews, which is useful for checking the latest state before replying (replies are overwritten in place).

Key params:
• accountId (path)
• reviewId (path, ID portion only)
• locationId (query, optional override; otherwise uses the account’s selected location)

Response includes review (GoogleBusinessReview).

Instagram now supports publishing videos muted via muteAudio in platformSpecificData.

When muteAudio=true, we strip the audio track before sending the video to Instagram, so the published video is permanently silent.

Use:
• muteAudio (boolean, default false)

Applies to Reels, Stories, and video carousel slides; ignored for images. Videos above 200MB cannot be muted (mute before uploading).

Threads posts now support an optional first comment via platformSpecificData.threads.firstComment.

This lets you automatically publish a reply immediately after the main post is published; when using threadItems, it replies to the root post.

Key field:
• firstComment (string, max 500)

Note: the first comment is a Threads post and counts toward the profile’s 250 posts / 24h limit.

Pinterest posts now support targeting a board section and optionally disclosing AI-modified content via PinterestPlatformData.

Use boardSectionId to publish into a specific section within boardId (omit it to post to the board). Pinterest rejects the pin if the section doesn’t belong to the board, so send both together.

Set isAiGenerated to true to include Pinterest’s AI_MODIFIED disclosure (shows an “AI modified” label); false (default) omits the disclosure.

Google Search ads created via POST /v1/ads/create now support campaign-level sitelinks.

You can create and attach sitelink assets during ad creation (Google reviews them asynchronously; approval is not immediate).

Use sitelinks (Google Search only):
• 2–20 items
• each item: text (max 25) + linkUrl (URI)
• optional: description1, description2 (each max 35)

Applies when campaignType is search.

Meta ads now support the Page Likes objective via goal = page_likes.

This lets you create campaigns/ads optimized for Page Likes (Meta maps this to Engagement/Page Likes) using the same create flows.

Use goal with:
• POST /v1/ads/campaigns: goal now includes page_likes
• POST /v1/ads/create: goal now includes page_likes

Notes for page_likes (Meta): promotedObject.pageId is optional (auto-filled from the connected Page). Creative fields like headline, body, linkUrl, callToAction, imageUrl/video are optional (Meta derives the Like button + destination from the Page).

Inbox list endpoints now return which connected accounts were skipped during aggregation via meta.accountsSkipped.

This helps you distinguish between accounts that failed (meta.failedAccounts) vs accounts that were intentionally not queried because the platform/account doesn’t support the feature or isn’t enabled.

New response field:
• meta.accountsSkipped: array of { accountId, platform }

Applies to:
• GET /v1/inbox/conversations
• GET /v1/inbox/comments
• GET /v1/inbox/reviews

GET /v1/ads/tree now supports scoping the tree to multiple ad accounts via adAccountId.

You can pass a comma-separated list to limit results to a subset of connected accounts (useful for agency profiles).

Use adAccountId=act1,act2,act_3 (max 50 per request). Single values keep the old behavior.

Note: the plural aliases adAccountIds and platformAdAccountIds are now rejected with 400 (to avoid silently returning unfiltered results).

GET /v1/ads/videos now returns a playable video URL via source in the default response.

This lets you preview a video before selecting it (useful when multiple videos share the same first frame).

Key field:
• data[].source — signed CDN MP4 URL (expires; use for preview only and re-list to refresh)

WhatsApp interactive messages now support native address capture via interactive.type = address_message on POST /v1/inbox/conversations/{conversationId}/messages.

This lets you prompt users with Meta’s structured shipping-address form in-chat; submissions arrive as metadata.interactiveType = nfm_reply on the message.received webhook.

To send, set:
• interactive.type: address_message
• interactive.action.name: address_message
• interactive.action.parameters.country: ISO 3166-1 alpha-2 (required)

Webhook parsing update: WebhookPayloadMessage.metadata now includes nfmReplyName (e.g. flow vs address_message) to distinguish address submissions from Flow submissions; address fields are included in flowResponseData.

New endpoint GET /v1/ads/{adId}/media returns direct signed URLs for every image/video asset used by an ad’s live creative (normalized across single, carousel, Reels/Story, and dynamic creative).

Use it to fetch short-lived asset URLs on demand (don’t cache long-term; re-fetch before serving/downloading).

Key details:
• Path param: adId (Zernio 24-char hex or platform ad id)
• Response: platform (facebook | instagram), media[] items with type (image | video), url, and for videos: thumbnailUrl, videoId, length, index
• Errors: 422 (no active Meta connection), 501 (only supported on Meta)

CTWA ad creation now supports a custom chat welcome message via welcomeMessage.

This lets you override Meta’s default greeting and prefilled user text when the WhatsApp chat opens, so ads can steer the first message toward what they promote.

Set welcomeMessage (single-creative) or creatives[].welcomeMessage (multi-creative) with:
• text
• prefillText

GET /v1/inbox/comments and GET /v1/inbox/comments/{postId} responses are now cached for up to 10 minutes.

This means comment counts/threads may lag new comments within that window; for real-time updates, use the comment.received webhook instead of polling.

Notes:
• Cache window: up to 10 minutes
• Recommended real-time mechanism: comment.received
• On GET /v1/inbox/comments/{postId}, your own writes (create/reply/delete) refresh the cache immediately.

Meta ad videos can now be managed directly via the API: upload standalone videos and delete them from an ad account’s video library.

Use POST /v1/ads/videos to upload before an ad exists (for reuse in POST /v1/ads/create via video.id or in POST /v1/ads/preview).

Upload params:
• accountId, adAccountId
• Exactly one of videoUrl (https) or videoBase64
• Optional filename (only for videoBase64)
Returns video.id and optional video.thumbnailUrl.

Use DELETE /v1/ads/videos/{videoId} with accountId + adAccountId to remove a video; returns { success: true } on success.

Breaking change (CTWA): when using multi-creative creatives[], setting any top-level headline/body/imageUrl/video now returns 400 (previously those fields could be silently ignored).

Also added for sorting: createdTime on AdTreeCampaign and AdTreeAdSet (proxy based on earliest ad creation time).

CTWA ad creation request (CtwaAdRequestBody) now supports reusing existing videos and more control over activation.

You can now pass video.id to reuse a video already uploaded to the ad account (instead of uploading via video.url). video.thumbnailUrl is now optional (Meta may auto-pick a thumbnail).

Video fields:
• video.url or video.id (either; id wins)
• video.thumbnailUrl (optional)

New status controls:
• status: ACTIVE | PAUSED (ad-level; default ACTIVE)
• campaignStatus: ACTIVE | PAUSED (campaign-level; default ACTIVE; rejected when using adSetId)

Connecting WhatsApp via POST /v1/connect/whatsapp/credentials now explicitly subscribes your Meta app to the WABA with a Zernio override callback, cutting over webhook delivery immediately (no overlap). Unsubscribing the app from the WABA afterward will also stop Zernio delivery and requires calling this endpoint again.

Response updates:
• webhookNotice may be returned on success with cutover/unsubscribe guidance
• account.phoneNumber replaces account.selectedPhoneNumber
• account.verifiedName and account.qualityRating are now included when available

WhatsApp Flows now let you set a data exchange endpoint via endpointUri when creating or updating a flow.

This enables configuring the HTTPS callback endpoint directly on DRAFT flows (and it will be used only if your uploaded Flow JSON declares dataapiversion "3.0").

New field:
• POST /v1/whatsapp/flows: endpointUri
• PATCH /v1/whatsapp/flows/{flowId}: endpointUri

Notes:
• endpointUri is uri format and HTTPS-only
• Settable only while the flow is in DRAFT

LinkedIn reshare behavior is now explicitly defined for platformSpecificData.reshareUrl on POST /v1/posts.

When you set reshareUrl, the published post is always a reshare authored by your account with the original embedded underneath: with content it’s a quote-style reshare, and with no content it’s a text-free reshare.

Note: a text-free reshare is not LinkedIn’s one-click “Repost” feed treatment (LinkedIn’s API doesn’t support creating that), so it will still appear authored by you.

Use: platformSpecificData.reshareUrl (mutually exclusive with media).

SIP trunking is now available for Voice: you can create SIP trunks and attach Zernio numbers to route inbound/outbound calls through an external SIP platform.

New endpoints:
• GET /v1/phone-numbers/sip-trunks (returns trunks, plus enabled)
• POST /v1/phone-numbers/sip-trunks (create; returns digestPassword only once)
• GET /v1/phone-numbers/sip-trunks/{id}
• DELETE /v1/phone-numbers/sip-trunks/{id}
• POST /v1/phone-numbers/sip-trunks/{id}/rotate-credentials (returns new digestPassword only once)
• POST /v1/phone-numbers/{id}/sip-trunk (attach with trunkId)
• DELETE /v1/phone-numbers/{id}/sip-trunk (detach)

Create trunk request fields: label, sipHost, optional sipPort, transport (tls/tcp/udp).

Phone number responses now include sipTrunkId (null when not trunked) on GET /v1/phone-numbers and GET /v1/phone-numbers/{id} (and the deprecated WhatsApp aliases).

Behavior change: when a number is attached to a trunk, these endpoints can return 409 (invalidresourcestate) and require detaching first:
• DELETE /v1/phone-numbers/{id}
• POST /v1/phone-numbers/{id}/voice
• POST /v1/phone-numbers/{id}/whatsapp/calling

LinkedIn company_list audiences can now be updated after creation via POST /v1/ads/audiences/{audienceId}/companies.

This uploads a new full company list and replaces the existing list (not appended/merged). Matching is asynchronous and the audience stays processing while LinkedIn processes the update.

Send:
• audienceId (path)
• companies (array, 1..300000) — each row must include at least one of name, domain, website, linkedinPageUrl

Notes:
• company_list is filled at creation from companies on POST /v1/ads/audiences; use the new endpoint for later changes
• POST /v1/ads/audiences/{audienceId}/users is customerlist-only and returns 422 for companylist (use /companies instead)

New endpoint GET /v1/ads/videos is available.

It lists a Meta ad account’s existing ad video library so you can reuse an already-uploaded video when creating ads (avoid duplicate uploads and share one upload across multiple ads).

Call with:
• accountId (required)
• adAccountId (required, act_<n>)
• fields (optional Graph field override)
• limit (optional, default 25, max 100)
• after (optional cursor)

Use returned data[].id as video.id on POST /v1/ads/create. A video is only usable once status.video_status is ready.

Note: this endpoint is Meta-only; other platforms return 501.

POST /v1/inbox/conversations now returns more specific Reddit error details.

This improves client-side handling when creating a Reddit DM thread fails (missing user, DM not allowed, or rate limiting).

Key response changes:
• 404 now includes code: PARTICIPANTNOTFOUND when the u/username doesn’t exist
• 422 now also applies to Reddit when the recipient doesn’t accept private messages (still code: DMNOTALLOWED)
• 429 may now be returned for Reddit rate limits with code: rate_limited

POST /v1/posts/{postId}/edit now supports editing published posts on more platforms and can target a specific account’s copy of a post.

You can now edit on platform: twitter, discord, facebook, reddit, linkedin, telegram, pinterest, googlebusiness, youtube, slack.

When a post was published to multiple accounts on the same platform, pass accountId to choose which one to edit (defaults to the first).

Request body: platform, content, optional accountId.

External Instagram posts and analytics responses now include additional Instagram-specific metadata fields.

This helps you distinguish content types like Reels vs Feed, detect AI-generated labels, and see whether a Reel was shared to the main feed.

New optional fields:
• mediaProductType (Instagram only; e.g. FEED, REELS, STORY, AD)
• isAiGenerated (Instagram only)
• isSharedToFeed (Instagram Reels only)
• mediaAudioType (Instagram only; MUSIC or ORIGINAL_SOUND)

Also, GET /v1/whatsapp/account-events events now include accountId in each event item.

Phone number listings now include WhatsApp Business Calling status via callingEnabled.

This lets you detect whether Calling is enabled per number when listing purchased numbers and connected (bring-your-own) numbers.

New fields:
• GET /v1/phone-numbers
- numbers[].callingEnabled
- connected[].callingEnabled
• GET /v1/whatsapp/phone-numbers (deprecated alias)
- numbers[].callingEnabled
- connected[].callingEnabled

New endpoint: GET /v1/whatsapp/account-events.

You can now poll a WhatsApp account’s Meta-originated event history (newest first), including template review outcomes and WABA status changes. This complements webhook push events with a queryable feed.

Required query: accountId
Optional query: limit (1–200, default 50)

Response: events[] with id, type (e.g. templateapproved, templaterejected, accountrestricted, accountdisconnected), severity (info/success/warning/critical), title, detail, createdAt.

New endpoint: POST /v1/connect/shopify/token to connect a Shopify store using a merchant-created custom-app Admin token (token-paste alternative to OAuth).

Use this when OAuth connect isn’t available or when users prefer not to install a third-party app; the token is validated against the store before saving and reconnecting replaces the stored token.

Request body:
• profileId
• shop (e.g. your-store.myshopify.com)
• accessToken (starts with shpat_)

Response includes account with platform = shopify and username = store domain.

WhatsApp connect endpoints now return a clearer 409 conflict when the selected number is already connected on another profile/workspace.

This lets you distinguish between “number pinned to another profile” vs “number already connected elsewhere” and handle the conflict programmatically.

On POST /v1/connect/whatsapp/credentials and POST /v1/connect/whatsapp/select-phone-number, 409 may include:
• WHATSAPPNUMBERPINNEDTOPROFILE — move it first with PATCH /v1/whatsapp/phone-numbers/{id}/profile
• WHATSAPPNUMBERALREADY_CONNECTED — disconnect it from the other profile/workspace first (a number can only be live on one profile)

mediaStatus on external/synced post media items can now be explicitly returned as available.

This makes media availability explicit instead of relying only on the field being absent, while keeping backward compatibility (older synced items may still omit mediaStatus).

Updated enums:
• ExternalPostMediaItem.mediaStatus: available | unavailable
• AnalyticsSinglePostResponse.mediaItems[].mediaStatus: available | unavailable

Notes: unavailable indicates the media file couldn’t be retrieved (often url is null, or LinkedIn video may return a cover image), and unavailableReason may be platform_withheld.

In post.external.* webhooks, ExternalPostMediaItem now clarifies LinkedIn video behavior: when LinkedIn returns no video file, url falls back to the cover image and the item includes mediaStatus.

This lets you distinguish a real downloadable media file from a thumbnail/cover-image fallback.

Check:
• url (may be null, or for LinkedIn videos may be a cover image)
• mediaStatus: unavailable (present only when the media file could not be retrieved)
• unavailableReason: platform_withheld

X (Twitter) posts now support long-form X Articles via platformSpecificData.article in POST /v1/posts.

This lets you create and publish an X Article (or save it as a draft) from the same post creation endpoint. When posting only Articles, content can be omitted.

Use platforms[].platformSpecificData.article with:
• title
• content_state
• mode: publish | draft
• optional cover.url (+ cover.altText)

Billing/pricing: GET /v1/billing/x-pricing now includes articledraft and articlepublish (both in tier xapi010, $0.010/call).

POST /v1/ads/boost now accepts a Meta-only CTA value VIEWINSTAGRAMPROFILE in callToAction.

This lets you boost a post with a CTA that drives clicks to an Instagram profile (typically paired with the profile URL).

Use:
• callToAction: VIEWINSTAGRAMPROFILE
• linkUrl: (Instagram profile URL)

Applies to Meta boosts only; other platforms will reject Meta-only options.

PlatformTarget.errorCategory now includes more granular failure types: platformratelimit and quota_exhausted.

Use these to distinguish platform throttling vs. shared daily API quota exhaustion and adjust retry/backoff or alerting logic accordingly.

Updated errorCategory values now include: authexpired, usercontent, userabuse, accountissue, platformrejected, platformerror, platformratelimit, quotaexhausted, systemerror, unknown.

WhatsApp messages sent via the inbox endpoints can now disable link previews using linkPreview.

This lets you send WhatsApp text without the URL thumbnail/preview (useful for cleaner utility messages or when previews are undesirable).

Set linkPreview (boolean, default true):
• false - send without link preview
• true - send with link preview

Available on:
• POST /v1/inbox/conversations (WhatsApp Direct Send with category = utility)
• POST /v1/inbox/conversations/{conversationId}/messages (WhatsApp; ignored on other platforms)

Comment webhooks now include comment.author.isOwnAccount in WebhookPayloadComment.

This lets you detect when a comment.received event was authored by the connected account itself (Meta can re-deliver the account’s own replies as comment events), so you can filter or route them differently.

New field:
• comment.author.isOwnAccount (boolean) — populated on Instagram/Facebook realtime webhooks only; if absent, it was not evaluated (don’t treat missing as false).

Webhook message.received payload now may include metadata.noRenderableContent (Instagram / Facebook Messenger only).

This flag indicates the inbound message contains nothing you can render (e.g., a template attachment with no text/parseable content, or Meta’s is_unsupported flag). Use it to suppress/handle “empty” messages in your UI.

New field: metadata.noRenderableContent (boolean)

Bluesky now supports default post languages at the account level, and per-post language tagging for feed-generator filtering.

Use the new endpoints to get/set an account default that applies at publish time when a post omits platformSpecificData.langs:
• GET /v1/accounts/{accountId}/bluesky-settings → returns defaultLangs
• PATCH /v1/accounts/{accountId}/bluesky-settings with defaultLangs = 1–3 BCP-47 codes (or null to clear)

On POST /v1/posts, Bluesky posts now accept platformSpecificData.langs (1–3 BCP-47 codes, e.g. pt, en-US). Per-post langs overrides the account default; if neither is set, the field is omitted. When using threadItems, the same langs applies to every item in the thread.

Meta ad creation now supports setting campaign status independently via campaignStatus on POST /v1/ads/create.

This lets you create a campaign ACTIVE while keeping the ad set/ad PAUSED (or the reverse), instead of using a single status value for all levels.

Set campaignStatus to ACTIVE or PAUSED (Meta only). If omitted, it follows status.

Ads now also return Meta’s creative id as ad.creative.creativeId, which you can reuse via existingCreativeId on POST /v1/ads/create.

Campaign/ad set status toggles now return clearer, more explicit results and always confirm what switch was written.

For PUT /v1/ads/campaigns/{campaignId}/status, the API writes the campaign on/off switch and returns the confirmed status (active | paused). updated/skipped now describe only ads whose stored status changed alongside the campaign switch, so updated: 0 can be a normal successful resume.

Response additions:
• status (active | paused)
• skippedReasons (why ads were skipped)

For ad sets (PUT /v1/ads/ad-sets/{adSetId} and PUT /v1/ads/ad-sets/{adSetId}/status), status toggling is now defined as writing the ad set’s own switch where supported (Meta/LinkedIn). Where a platform has no ad-set switch, the API may return no status and instead return a message when nothing was written.

Response additions/changes:
• status may be absent (see statusMessage/message)
• statusSkippedReasons / skippedReasons
• statusMessage / message

Also clarified: on Meta, resuming a campaign doesn’t automatically unpause ad sets paused independently—pair with PUT /v1/ads/ad-sets/{adSetId}/status when needed.

GET /v1/accounts/{accountId}/health now includes platformConnection for WhatsApp accounts.

This adds a live probe of the Meta link behind the channel (same read as GET /v1/whatsapp/number-info), so WhatsApp liveness can be detected even when tokenStatus is valid. When the Meta link is dead, platformConnection.status is disconnected and overall status is error.

New WhatsApp-only fields:
• platformConnection.status: connected | disconnected | unknown
• platformConnection.checkedAt
• platformConnection.phoneStatus
• platformConnection.metaError (when disconnected: code, subcode, message)

Webhooks now support the new WhatsApp event template category updates via whatsapp.template.category_updated.

This fires when Meta reclassifies a WhatsApp template’s category on a connected WABA, so you can react to upcoming (scheduled) and applied (applied) changes.

Subscribe by adding whatsapp.template.category_updated to events when calling POST /v1/webhooks/settings or PUT /v1/webhooks/settings.

Payload highlights:
• event: whatsapp.template.category_updated
• template.changeType: scheduled | applied
• template.category: UTILITY | MARKETING | AUTHENTICATION
• template.previousCategory (only when applied)
• template.scheduledCategory, template.effectiveAt (only when scheduled)

Meta ad creation changed how the default Instagram identity is chosen when instagramAccountId is omitted on POST /v1/ads/create.

If you don’t pass instagramAccountId, we now use the Instagram actor Meta already runs the Page’s other ads as, falling back to the Page’s page-backed Instagram account.

To force a specific IG identity, set instagramAccountId to the desired Instagram Business Account ID (e.g. 17841...).

Meta conversion setup on POST /v1/ads/create is now stricter/clearer around promotedObject.

Meta rejects promotedObject.pixelId unless promotedObject.customEventType is also provided (even if promotedObject.customConversionId is set). If you want to optimize for a Custom Conversion without sending pixel/event, you can now send promotedObject.customConversionId alone.

Key fields:
• promotedObject.pixelId + promotedObject.customEventType (required together for Meta pixel-based conversion optimization)
• promotedObject.customConversionId (can be sent alone; if pixelId is also sent, customEventType is still required)
• For pixel custom events: promotedObject.customEventType = OTHER + promotedObject.customEventStr

SMS is now supported in inbox webhooks, and SMS sends now explicitly fail for opted-out recipients.

Inbound SMS replies arrive via message.received with message.platform = sms, and outgoing SMS outcomes arrive via message.delivered / message.failed (carrier error details included on failure).

When sending via POST /v1/sms/messages:
• Opted-out recipients (replied STOP) are refused with 409
• 409 can also mean the same Idempotency-Key is still in flight

Webhook platform enum now includes sms (alongside instagram, facebook, telegram, whatsapp).

KYC address payloads now accept an optional extended_address field on:
• POST /v1/phone-numbers/kyc
• POST /v1/phone-numbers/kyc/validate-address
(and the deprecated /v1/whatsapp/... aliases).

Use extendedaddress for address complements like apartment/suite/unit (or quadra/lote in some countries). This can help pass address validation without changing streetaddress.

Set address.extendedaddress (KYC submit) or top-level extendedaddress (validate-address).

Webhooks now support referral click events via the new referral.received event.

This lets you capture Meta referral payloads even when a click opens an existing thread without generating a message (previously you could only see referrals on message.received when Meta attached them).

To subscribe, include referral.received in events when creating/updating a webhook:
• POST /v1/webhooks/settings events
• PUT /v1/webhooks/settings events

The webhook payload is WebhookPayloadReferral with:
• event = referral.received
• referral (Meta object forwarded verbatim; may include ref, source, type, refereruri, adid, adscontextdata)
• sender, conversation, account, timestamp

You can now attach a Meta multi-language ad when adding an ad to an existing ad set via POST /v1/ads/create.

In adSetId (attach) mode, you can provide a per-locale asset feed so one ad carries localized copy (and optional localized media) while keeping social proof on a single post.

Use:
• adSetId (attach mode)
• defaultLocale (e.g. en, pt_BR)
• translations[] with required fields: locale, headline, body, description (optional per-locale: linkUrl, imageUrl, videoUrl, thumbnailUrl)

Note: translations is mutually exclusive with dynamicCreative, placementAssets, carouselCards, existingCreativeId and creatives[].

POST /v1/posts now supports LinkedIn plain reposts (no commentary).

If every platform entry is a LinkedIn repost using platformSpecificData.reshareUrl, you can omit top-level content (and omit customContent) to publish LinkedIn’s one-click “Repost” with no text.

Use platformSpecificData.reshareUrl (LinkedIn post URL or urn:li:share/urn:li:ugcPost/urn:li:groupPost). If you include content, it becomes a quote-reshare (repost with your thoughts).

Workflow nodes now support an optional display label via WorkflowNode.label.

This lets you set a human-friendly name shown in the builder canvas/inspector (falls back to the node type when omitted). If you update a workflow, remember the nodes array is replaced wholesale—so resend label to keep it.

Use label (string, 1–80 chars) on WorkflowNode.

GET /v1/ads/targeting/search expands geo targeting with a new geoType option all and additional geo types.

You can now search across multiple geo levels in one call (relevance-ranked) instead of picking a single level.

Updated geoType enum:
• all, country, region, city, subcity, neighborhood, place, zip, metroarea, geomarket

Pinterest notes: city is treated as an alias for all (Pinterest has no city-level catalog), and some geo types (e.g. zip) return 400 because Pinterest doesn’t expose those catalogs.

GET /v1/inbox/comments/{postId} now supports passing a Facebook/Instagram comment ID as postId to fetch that comment’s replies (instead of the post’s top-level comments).

This lets you page deeper reply threads without a separate endpoint; on YouTube, postId must still be a video id.

Use:
• GET /v1/inbox/comments/{postId}?accountId=... where {postId} can be a post ID or (FB/IG only) a comment ID
• New response signal (Facebook only): repliesHasMore (when true, fetch remaining replies by calling the same endpoint with that comment’s id as postId)

Also updated for GET /v1/inbox/comments pagination:
• nextCursor pagination can continue past the first page on facebook, instagram, threads, linkedin, youtube
• Cursor paging is only coherent for sortBy=date + sortOrder=desc; other sort combinations can make page 2 unreliable
• Treat nextCursor as opaque and dedupe results by id

Shopify is now supported as a connect-only platform, with a new Blogs API to manage store blogs and articles.

Start the OAuth flow with GET /v1/connect/shopify using profileId, shop (e.g. your-store.myshopify.com), and optional redirect_url. This creates an account on the profile with platform shopify.

Manage blogs on a connected Shopify account (accountId):
• GET /v1/accounts/{accountId}/blogs (limit 1-50, cursor)
• POST /v1/accounts/{accountId}/blogs (title, optional handle)
• GET/PATCH/DELETE /v1/accounts/{accountId}/blogs/{blogId} (blogId is platform-native numeric)

Manage articles within a blog:
• GET /v1/accounts/{accountId}/blogs/{blogId}/articles (limit 1-50, cursor)
• POST /v1/accounts/{accountId}/blogs/{blogId}/articles (supports bodyHtml, tags, image.url, seo.title/seo.description, isPublished, publishDate)
• GET/PATCH/DELETE /v1/accounts/{accountId}/blogs/{blogId}/articles/{articleId} (articleId is platform-native numeric)

Notes: a future publishDate schedules publication natively on Shopify; DELETE on a blog deletes the blog and all its articles permanently.

Also added: GET /v1/connect/{platform} now accepts WhatsApp-only onboarding = api | business_app.

Campaign listing and tree endpoints now support filtering by delivery/spend within a date window.

On GET /v1/ads/campaigns, you can now return only campaigns that actually delivered in fromDate–toDate, or that reached a spend threshold.

New query params:
• hasDelivery (boolean) — only campaigns with delivery in the window (spend > 0 or impressions at zero spend)
• minSpend (number, min 0) — only campaigns whose spend in the window reaches this amount (in the campaign’s own currency); implies hasDelivery

On GET /v1/ads/tree, the same filters were added, and fromDate is clarified: it affects metrics only unless you also pass hasDelivery or minSpend. Pagination totals reflect the filtered campaign set.

Google Local Services Ads lead insights are now available via two new endpoints.

You can fetch LSA leads live from Google (newest first) and then pull the conversation history (calls/messages) for a specific lead. Note: data is not persisted (Google is the source of truth), and requests draw from the shared Google Ads operations budget.

Get leads with GET /v1/ads/local-services/leads
Required: accountId
Optional filters: customerId, fromDate, toDate, leadType (PHONECALL/MESSAGE/BOOKING), leadStatus (e.g. NEW, BOOKED, WIPEDOUT), chargedOnly, pageToken
Key fields: id, contact (null when WIPED_OUT), charged, creditState, createdTime

Get lead conversations with GET /v1/ads/local-services/leads/{leadId}/conversations
Params: leadId, accountId (+ optional customerId, pageToken)
Conversation fields include channel (PHONECALL/MESSAGE/SMS/EMAIL/WHATSAPP/ADSAPI), participantType (ADVERTISER/CONSUMER), plus phoneCall.callRecordingUrl / message.attachmentUrls when applicable.

TikTok ads now populate engagement breakdown in AdEngagementCounts (previously Meta-only).

You can now read paid engagement interactions for TikTok directly from engagementBreakdown (while TikTok follows remain in actions).

Key fields:
• AdMetrics.engagementBreakdown.reactions (TikTok paid likes)
• AdMetrics.engagementBreakdown.comments
• AdMetrics.engagementBreakdown.shares
• AdMetrics.actions.follow (TikTok followers objective result)

Other platforms are unchanged (still 0 where not supported).

POST /v1/ads/create now supports TikTok Smart+ campaigns via smartPlus.

When smartPlus: true, Zernio creates an Upgraded Smart+ campaign where TikTok automates targeting/bidding/delivery (within your provided geo targeting).

Key fields:
• Enable: smartPlus (boolean)
• Supported goal: conversions, leadgeneration, apppromotion
• Web Smart+ requires promotedObject.pixelId + promotedObject.customEventType
• App Smart+ requires promotedObject.applicationId
• Budget is campaign-level; budgetType=lifetime requires endDate
• Cannot be combined with adSetId

LinkedIn posts now support polls via poll in LinkedInPlatformData.

Use this to publish a LinkedIn poll with your post. Polls cannot be combined with media or reshareUrl, cannot be edited after publishing, and API-created polls are non-sponsored only.

Set poll with:
• question (1-140 chars)
• options (2-4 items, 1-30 chars each)
• duration (optional): ONEDAY | THREEDAYS | SEVENDAYS | FOURTEENDAYS (default SEVEN_DAYS)

Ad analytics now include additional Meta click + cost breakdown fields in AdMetrics.

This adds per-action cost metrics and separates different click definitions (attributed vs in-session vs outbound), making it easier to build accurate dashboards and optimize campaigns.

New fields:
• costPerAction (object) — derived spend / actions[type] per action type
• outboundClicks, outboundClicksCtr
• inlineLinkClicks, inlineLinkClickCtr
• uniqueClicks, uniqueCtr

Note: these click fields are Meta-only; other platforms return 0 (and costPerAction may be {} when not applicable).

Google Ads now supports keyword edits on existing ads via PUT /v1/ads/{adId}.

You can update Google Search ad group keywords by sending targeting.keywords and/or targeting.negativeKeywords. Each list you send becomes the FULL new set of that kind (items not included are removed); omit a kind to leave it unchanged.

Use:
• targeting.keywords (Google only) — items are "string" (defaults to broad) or { text, matchType } where matchType is exact | phrase | broad
• targeting.negativeKeywords (Google only) — same shape as above

Also added for Google Search creation via POST /v1/ads/create:
• negativeKeywords — broad-match negative keywords on the new ad group (editable later via PUT /v1/ads/{adId} targeting.negativeKeywords).

TikTok ad reporting now populates additional video metrics in AdMetrics (previously documented as Meta-only).

This lets you use the same video KPI fields across Meta and TikTok when reading ad/campaign metrics.

TikTok sources now apply to:
• videoPlayActions
• videoP25WatchedActions
• videoP50WatchedActions
• videoP75WatchedActions
• videoP100WatchedActions
• videoAvgTimeWatchedActions

Meta-only remains:
• video30SecWatchedActions
• videoThruplayWatchedActions
• videoP95WatchedActions
• costPerThruplay

Instagram now supports attaching catalog audio to Reels via platformSpecificData.audioConfiguration.

You can search/trend audio with GET /v1/accounts/{accountId}/instagram/audio (omit q for trending) and fetch metadata with GET /v1/accounts/{accountId}/instagram/audio/{audioId}. Use the returned audioId when creating a Reel.

Search params:
• audioType: music | original_sound
• q: optional keywords (omit for trending)

To publish with audio, set:
• platformSpecificData.audioConfiguration.audioId (required)
• platformSpecificData.audioConfiguration.audioVolume (0-100)
• platformSpecificData.audioConfiguration.videoVolume (0-100)

Requires an Instagram account connected via Facebook Login. Classic Instagram Login accounts will get a 400 instagramaudiorequiresfacebooklogin and must be reconnected using the Facebook option.

GET /v1/broadcasts/{broadcastId}/recipients now returns errorTraceId for failed recipients.

Use errorTraceId (Meta fbtrace_id) to correlate a failed send and quote it when escalating to Meta Direct Support. It’s only populated when status is failed (Meta platforms).

New field: errorTraceId (string | null)

GET /v1/accounts/{accountId}/instagram/stories/{storyId}/insights can now return 502 when Instagram rejects the upstream request.

This makes upstream failures explicit so clients can distinguish Instagram-side rejection from successful-but-empty expired story results.

Handle these responses:
• 200 with data.source = live | cached | unavailable
• 502 - Instagram rejected the request

Meta ads now support scheduled budget increases via POST /v1/ads/high-demand-periods.

This lets you pre-schedule temporary budget bumps (e.g. Black Friday) instead of editing budgets manually on the day.

Send:
• accountId
• exactly one of campaignId / adSetId
• budgetValueType: ABSOLUTE | MULTIPLIER
• budgetValue
• timeStart, timeEnd (Unix seconds, 15-min boundaries)
• optional recurrenceType: ONE_TIME | WEEKLY | MONTHLY

Meta custom conversions are now manageable via the API:

• List: GET /v1/accounts/{accountId}/custom-conversions (requires adAccountId)
• Create or reuse: POST /v1/accounts/{accountId}/custom-conversions

Creating supports reuse (to avoid duplicates) by matching name + pixelId; reused conversions return 200 with reused: true, otherwise 201. The response includes customConversionId for promotedObject.customConversionId on POST /v1/ads/create.

Meta creatives now accept multiAdvertiser: OPTIN | OPTOUT on:
• POST /v1/ads/creatives
• POST /v1/ads/create

Use OPT_OUT to disable Meta’s multi-advertiser ads behavior (Meta auto-enrolls by default).

POST /v1/media/presign no longer accepts the permanent request field.

If you were sending permanent: true to write uploads to non-expiring storage, remove this parameter from your request payload. Uploads will now follow the default behavior described by the endpoint.

Removed parameter: permanent (boolean)

POST /v1/media/presign now supports permanent uploads.

By default, presigned uploads go to temporary storage and auto-delete 7 days after upload (so the publicUrl stops working after that). Set permanent: true to write to permanent storage with no expiry—useful for media that must remain reachable longer (e.g., covers/thumbnails for posts scheduled >7 days out).

New request field: permanent (boolean, default false)

When permanent is true, the response publicUrl and key use the media/ prefix instead of temp/.

You can now like/unlike posts via the Inbox API.

This enables executive engagement (like/react as any connected accountId on a brand post). postId accepts a Zernio post ID or the platform native post ID.

New endpoints:
• POST /v1/inbox/posts/{postId}/like with accountId (+ optional reactionType for LinkedIn: LIKE, PRAISE, EMPATHY, INTEREST, APPRECIATION, ENTERTAINMENT; optional cid for Bluesky)
• DELETE /v1/inbox/posts/{postId}/like with accountId (+ likeUri required for Bluesky)

Also updated: comment like/unlike now supports LinkedIn on POST /v1/inbox/comments/{postId}/{commentId}/like and DELETE /v1/inbox/comments/{postId}/{commentId}/like. For LinkedIn likes, pass the composite comment URN as commentId and you can set reactionType (same enum as above).

Workflow AI nodes now support openrouter as an ai.provider value.

This lets you route AI steps through OpenRouter using your BYOK setup (set provider + model).

Set ai.provider to one of: anthropic, openai, google, mistral, groq, openrouter.

Inbox messages now support refreshable attachment URLs for Instagram/Facebook DMs.

Meta DM media URLs expire; attachments now include a stable refreshUrl you can store and call later to get a working media URL.

New endpoint: GET /v1/inbox/conversations/{conversationId}/messages/{messageId}/attachments/{index}
Key params: accountId (required), format (redirect | json, default redirect)

Response behavior:
• Default format=redirect returns 302 to the live media URL
• format=json returns { url, refreshed }

Also added on GET /v1/inbox/conversations/{conversationId}/messages attachments:
• attachments[].refreshUrl (Instagram/Facebook only)
• attachments[].url is now documented as expiring on Instagram/Facebook (use immediately; don’t store).

Comment-to-DM automations can now also trigger from inbound DMs via alsoMatchInDms.

Set alsoMatchInDms: true on a trigger=comment automation to answer users who DM the keyword instead of commenting it. Deduplication is per source (comment vs DM).

Key details:
• alsoMatchInDms (boolean, default false) on POST /v1/comment-automations and PATCH /v1/comment-automations/{automationId}
• Requires at least one keywords entry (empty keyword lists are rejected when enabling)
• Not allowed for trigger=story_reply

Responses now include:
• alsoMatchInDms on automation objects (list/get/create/update)
• source on log entries: comment | story_reply | dm

Instagram connect now supports headless mode for loginMethod=facebook_login on GET /v1/connect/instagram.

This lets you run the Facebook Login-based Instagram flow with your own UI: after OAuth, the callback redirects to your redirect_url with selection-step params, and you finish by calling GET /v1/connect/instagram/select-account.

Use:
• GET /v1/connect/instagram?loginMethod=facebook_login&headless=true
Callback includes: platform=instagram, step=selectaccount, profileId, tempToken, connecttoken

WhatsApp connect now rejects Zernio-provisioned numbers that are pinned to a different profile with a 409 conflict.

This prevents accidentally connecting a provisioned WhatsApp number from the wrong profileId. If you need to connect it on another profile, move the number first, then retry the connect.

New 409 responses:
• GET /v1/connect/whatsapp (when profileId doesn’t match the provisioned number’s profile)
• POST /v1/connect/whatsapp/credentials
• POST /v1/connect/whatsapp/select-phone-number

Remediation:
• Move the number with PATCH /v1/whatsapp/phone-numbers/{id}/profile, then connect again.

Google Business location selection/updates now validate the provided Google account resource name and will reject mismatches.

If you pass an account identifier to speed up location resolution for large GBP accounts, the API will now return 400 when the provided account is not one of the accounts the connection manages.

Applies to:
• POST /v1/connect/googlebusiness/select-location with accountId
• PUT /v1/accounts/{accountId}/gmb-locations with googleAccountId (legacy body field accountId still accepted)
• POST /v1/accounts/{accountId}/gmb-locations/assign with googleAccountId

POST /v1/ads/boost now supports attaching a boost to an existing Meta ad set via adSetId, and adds Meta support for CTA destinations via linkUrl + callToAction.

This lets you refresh/boost an existing post while keeping the ad set’s learning phase (attach to an existing ad set instead of provisioning a new campaign/ad set).

Key changes:
• Meta-only attach: send adSetId to attach under an existing ad set
• When adSetId is set, budget/schedule/targeting are owned by the ad set and sending any of them is a 400
• budget is now required only when adSetId is NOT set
• Meta-only additions: instagramAccountId, destinationType (INSTAGRAMPROFILE, WEBSITE, ONAD, MESSENGER, WHATSAPP)
• linkUrl is now supported on Meta boosts (still supported on TikTok); callToAction must be sent together with linkUrl (sending either alone is a 400)

POST /v1/ads/ctwa (deprecated) also adds an attach flow:
• Send adSetId to add creatives to an existing messaging ad set; then budgetAmount/budgetType/endDate/objective/countries/interests/audienceId are rejected with 400

Schema note (breaking for generated clients): CtwaAdRequestBody no longer lists budgetAmount/budgetType as always-required (they’re required unless adSetId is set).

New endpoint: PATCH /v1/whatsapp/phone-numbers/{id}/profile to move a provisioned number to another profile.

This re-homes the number and any associated accounts together (so you don’t split the number across profiles by moving only the social account).

Send { "profileId": "..." } where id is the phone number record id from GET /v1/phone-numbers (not an account id).

Response may include movedPlatforms with values phone, sms, whatsapp. Conflicts return 409 if the destination profile already has an account on any of those platforms.

PUT /v1/ads/campaigns/{campaignId} now supports Google campaigns (in addition to Meta) and enforces platform-level field support (unsupported fields return 400, not silently ignored).

For Google, you can set campaign bidding via:
• platform: google
• bidStrategy (Meta + Google)
• bidAmount (Google only; required for LOWESTCOSTWITHBIDCAP and COST_CAP)
• roasAverageFloor (Google only; required for LOWESTCOSTWITHMINROAS)

The 200 response now echoes back only the fields you sent, plus updated (and may include bidAmount/roasAverageFloor when provided).

Message reactions are now supported on Instagram, Facebook Messenger, and Slack via the existing reactions endpoints.

You can add/remove reactions across more inbox channels, and reaction webhooks now cover these platforms too.

Use:
• POST /v1/inbox/conversations/{conversationId}/messages/{messageId}/reactions with emoji
• DELETE /v1/inbox/conversations/{conversationId}/messages/{messageId}/reactions with accountId (query)

Notes:
• Slack reactions require a Slack emoji name like :thumbsup: (unnamed Unicode emoji returns 400)
• Instagram/Messenger reactions are subject to Meta’s 24h messaging window
• reaction.received webhook now includes Slack/Instagram/Messenger (sender can be the business platform id; compare reaction.sender.id with conversation.participantId)

Comment-to-DM automations now support sending a Meta generic template (product card) as the first DM.

Set template on POST /v1/comment-automations / PATCH /v1/comment-automations/{automationId}:
• template.type: generic
• template.elements: 1–10 cards (each supports title, subtitle, imageUrl, buttons)

Constraints:
• template is mutually exclusive with buttons (sending both is a 400)
• For PATCH, pass template: null to clear the card

Also: for POST /v1/inbox/conversations/{conversationId}/messages on Instagram/Facebook, top-level buttons are now explicitly mutually exclusive with template (sending both returns 400).

Instagram follow checks are now available via GET /v1/accounts/{accountId}/follow-status/{userId}.

This resolves the follow relationship (when Meta allows it) and returns isFollower (can be null when unknown) plus basic public counters; use refresh=true to bypass the short cache.

Key fields:
• isFollower: true | null (null = unknown, never “no”)
• unavailableReason: consentrequired | dmaccessdisabled | notmessageable | error | null

Comment-to-DM automations now support follower-based targeting + optional follow verification (Instagram only), and delayed sends.

New request fields on POST /v1/comment-automations and PATCH /v1/comment-automations/{automationId}:
• dmDelaySeconds (0–86400)
• commentReplyDelaySeconds (0–86400)
• audience (followerStatus: any | follower | non_follower; whenUnknown: send | skip | verify; optional minFollowerCount)
• followGate (message, buttonLabel, optional notFollowingMessage)

Automation logs (GET /v1/comment-automations/{automationId} and .../logs) add new status values pending and gated, plus fields like audienceOutcome (passed | blocked | gatesent | gatepassed | gate_failed) and nextDueAt while queued.

Webhook comment payloads now may include Instagram-only comment.author.instagramProfile (best-effort) with isFollower/followerCount when available; absence means “unknown”.

GET /v1/comment-automations/{automationId}/logs now returns non-matching comment diagnostics via a new misses object.

Use misses to see how many comments reached the automation but matched none of its keywords (and a few recent samples) to troubleshoot keyword/exclusion setups.

New response fields:
• misses.total
• misses.retentionDays
• misses.samples[]: commentText, commenterName, excludedBy, at

Request validation tightened:
• limit now 1..200
• skip now >= 0
• Invalid values may return 400 BadRequest

PATCH /v1/comment-automations/{automationId} now accepts trigger to control what fires an automation.

You can switch an automation between comment-based and story-reply-based triggers; changing it will detach the automation from its currently bound post/story unless the same request sets a new binding.

Set trigger to: • comment • story_reply (Instagram only)

Ads analytics now includes funnel step counts, an engagement breakdown, and cost per ThruPlay.

This makes it easier to report on Meta ads without parsing/deduping raw actions keys (and avoids double-counting), and adds a direct cost metric for ThruPlays.

New fields in AdMetrics:
• costPerThruplay
• funnel (ref AdFunnelCounts): landingPageViews, contentViews, searches, wishlistAdds, cartAdds, checkoutsInitiated, paymentInfoAdds, purchases, leads, registrationsCompleted, appInstalls, messagingConversationsStarted, messagingFirstReplies
• engagementBreakdown (ref AdEngagementCounts): postEngagement, pageEngagement, reactions, comments, shares, saves, pageLikes, videoViews, linkClicks

Also new in Ad:
• creativeType: carousel | video | document | image | null

Comment-to-DM automations now support more precise keyword matching and exclusions via matchMode=word, plus new fields excludeKeywords and typoTolerance.

This lets you avoid accidental triggers (e.g., keyword app no longer firing on happy) and optionally match close misspellings when using word-based matching.

Use matchMode:
• contains • word • exact

New fields:
• excludeKeywords: string[] - comments matching these never trigger (compared using the same matchMode)
• typoTolerance: boolean - only with matchMode=word

Available on POST /v1/comment-automations, PATCH /v1/comment-automations/{automationId}, and returned by GET endpoints.

LinkedIn connected accounts now include additional profile details in SocialAccount.metadata.profileData (refreshed on each daily snapshot).

This lets you read LinkedIn bio/headline and vanity slug info directly from the account object without extra lookups.

Key fields:
• metadata.profileData.bio (nullable)
• metadata.profileData.extraData.vanityName (personal accounts)
• metadata.organizationInfo.vanityName (organization accounts)

Meta ads creation now supports optimizing for pixel custom events via promotedObject.customEventStr on POST /v1/ads/create.

Use this when you want goal=conversions (or lead_conversion) to optimize against a custom event name from Events Manager (instead of a standard event or a Custom Conversion).

Set:
• promotedObject.customEventType = OTHER
• promotedObject.customEventStr = <youreventname>

customEventStr is case-sensitive, and OTHER requires customEventStr (and vice versa).

Incoming message.received webhooks now include quote-reply context via metadata.quotedMessageId.

This lets you correlate an inbound message that quotes/replies to an earlier message (WhatsApp/Instagram/Facebook Messenger) using the original message’s platformMessageId.

New field:
• metadata.quotedMessageId - platformMessageId of the message being quoted/replied to

Also clarified POST /v1/inbox/conversations/{conversationId}/messages replyTo behavior:
• WhatsApp: pass wamid
• Telegram: pass Telegram message ID
• Instagram: outbound quote replies are not supported by Meta's Send API; replyTo is ignored. Quote context is available on inbound messages only.
• Slack: threads the reply (uses thread_ts)
• Silently ignored on platforms without reply support (incl. Facebook Messenger)

Meta multi-language ads now support per-locale destination URLs via translations[].linkUrl on POST /v1/ads/create.

This lets you send users to different landing pages per language while keeping a single ad (shared social proof).

Set translations[].linkUrl to override the destination for that locale; when omitted it inherits the top-level linkUrl (which must be present if any locale uses translations[].linkUrl).

Webhooks now support per-subscription event blocking via disabledResourceGroups on POST /v1/webhooks/settings and PUT /v1/webhooks/settings.

This lets you prevent specific resource-group events (e.g. private messages) from ever being delivered to a webhook endpoint, even if those events are listed in events. The same filtering applies to replay paths (test fire, redelivery, dead-letter requeue).

Use disabledResourceGroups (enum: publishing, engagement, messages, contacts, analytics, ads, telephony, accounts, billing, webhooks):
• Create: include disabledResourceGroups to opt out; omit or [] to receive everything in events
• Update: sending disabledResourceGroups replaces the denylist; send [] to clear; omit to leave unchanged

Restricted zrk_ keys: the key’s own disabled groups are always unioned into the subscription, so a restricted key can’t create or widen a subscription beyond itself.

New/expanded 403 behavior (ResourceGroupForbidden) was added to:
• GET /v1/webhooks/settings
• DELETE /v1/webhooks/settings
• POST /v1/webhooks/test (note: webhook.test is in the webhooks group)

Note: after updating a webhook denylist, already-queued events may still arrive for up to ~5 minutes.

Non-draft updates to PUT /v1/posts/{postId} now run the same per-platform validation as post creation.

If the resulting post violates platform rules (media requirements, platform-specific fields, etc.), the update will return 400 instead of succeeding.

Also, PostUpdateResponse may now include warnings (array of strings).

WhatsApp now supports requesting a user’s contact info via interactive messages.

You can send a consent-based “share contact” prompt, and inbound replies include contact cards plus an origin flag so you can distinguish consented self-share vs address-book shares.

Send with interactive.type:
• requestcontactinfo

On message.received, check:
• metadata.contacts (array)
• metadata.contactsOrigin: contact_request | other

Slack DMs are now supported in the Inbox API.

You can list eligible Slack workspace members (for a recipient picker) via GET /v1/accounts/{accountId}/slack-members, then start a DM by passing the member id as participantId to POST /v1/inbox/conversations.

Key params:
• GET /v1/accounts/{accountId}/slack-members: query, limit
• POST /v1/inbox/conversations: participantId (Slack member id, e.g. U01ABCDEF)

Also updated: POST /v1/inbox/conversations now lists supported platforms as X/Twitter, Bluesky, Reddit, WhatsApp, SMS, and Slack.

OAuth connect now surfaces upstream token-exchange failures via a new 502 response on POST /v1/connect/{platform}.

This helps distinguish platform-side rejections from internal errors; handle 502 separately from 500 (the upstream 4xx is forwarded as platform_error).

Key response codes:
• 502 - platform rejected token exchange (platform_error)
• 500 - internal error while connecting the account

Lead form creation can now return 422 on POST /v1/ads/lead-forms when Meta rejects the form (error code 3), typically because the Facebook Page hasn’t accepted the Lead Ads Terms.

Key response code:
• 422 - Meta rejected lead form (often requires a Page admin to accept Lead Ads Terms)

Contacts listing now supports filtering by SocialAccount via accountId on GET /v1/contacts.

Use accountId to list contacts through their channel; when accountId is set, the profileId contact filter is not applied (a provided profileId is still access-checked and still scopes filters.tags).

New query param: accountId

Also, POST /v1/contacts 409 is now explicitly documented as: Duplicate channel. The platformIdentifier is already bound to a channel on this accountId.

New endpoint GET /v1/auth/verify was added to validate a bearer credential (API key or OAuth access token) without calling a data endpoint.

Use it to confirm a credential is valid before proceeding (e.g., when verifying an incoming token).

On 200 it returns valid, userId, authType (api_key | oauth | session), and scope (space-separated OAuth scopes; null for API keys). 401 if invalid.

POST /v1/ads/boost now supports Meta-only optimization goal overrides via optimizationGoal.

This lets you explicitly set the ad set optimization_goal instead of relying on the default derived from goal, which can be useful when Meta requires a different optimization goal for the boost objective.

Set optimizationGoal to a Meta-compatible value for the objective derived from your goal (e.g. boost goal engagement maps to Meta objective OUTCOMEAWARENESS, so values like REACH, IMPRESSIONS, ADRECALLLIFT, or THRUPLAY-class are accepted; POSTENGAGEMENT is rejected under that objective).

Meta Ads now supports Value Rule Sets (bid adjustments by audience segment) via new endpoints under /v1/ads/value-rule-sets.

You can create/list/read/replace/delete value rule sets, then attach one to an ad set to increase/decrease bids for matching segments (rule order matters: first match wins).

New endpoints:
• GET /v1/ads/value-rule-sets
• POST /v1/ads/value-rule-sets
• GET /v1/ads/value-rule-sets/{valueRuleSetId}
• PUT /v1/ads/value-rule-sets/{valueRuleSetId} (full replace, not patch)
• DELETE /v1/ads/value-rule-sets/{valueRuleSetId}

Attach/detach on ad sets (Meta only) via PUT /v1/ads/ad-sets/{adSetId}:
• Attach/replace: send valueRuleSetId (optionally valueRulesApplied: true)
• Detach: send valueRulesApplied: false and omit valueRuleSetId
• Sending valueRulesApplied: false with valueRuleSetId returns 400 mutuallyexclusivefields

Also supported on create (Meta only) via POST /v1/ads/create:
• Attach to the new ad set with valueRuleSetId (optional valueRulesApplied: true)
• valueRulesApplied: false is rejected on create

Eligibility (Meta enforced): only ad sets on LOWESTCOSTWITHOUTCAP or COSTCAP.

WhatsApp template creation now supports NAMED variables via parameter_format on POST /v1/whatsapp/templates.

This lets you use {{customer_name}}-style tokens (in addition to the existing positional {{1}} style) and provide per-variable examples for Meta review.

Set parameter_format to POSITIONAL | NAMED (also accepts positional | named).

For NAMED templates, include examples in:
• components[].example.bodytextnamed_params
• components[].example.headertextnamed_params

Each named param example uses: { param_name, example }.

Ad.creative.thumbnailUrl can now be null (was always a string).

This affects ad preview/rendering: don’t assume a thumbnail URL is always available; fall back to other creative fields when it’s missing.

Key change: creative.thumbnailUrl: string | null

Connect flow redirects now include the created social account id in the success redirect_url for these endpoints:
• POST /v1/connect/facebook/select-page
• POST /v1/connect/googlebusiness/select-location
• POST /v1/connect/pinterest/select-board
• POST /v1/connect/snapchat/select-profile

This lets you reliably capture the connected account immediately after OAuth without extra lookup.

Look for accountId in the returned redirect_url query params (e.g. ...&accountId=...).

PUT /v1/posts/{postId} now requires platforms when sending root-level tiktokSettings or facebookSettings.

If you include tiktokSettings or facebookSettings in an update request without a platforms array, the API will return 400. Include the target platforms (with platform + accountId) in the same request when updating these settings.

In PUT /v1/posts/{postId}, platforms[].platformSpecificData update behavior is now explicitly defined.

A Settings namespace (e.g. facebookSettings, tiktokSettings) that is omitted from the request is preserved from the stored post. If you send the key, it replaces the entire namespace (it is not deep-merged).

Key field: platforms[].platformSpecificData

GET /v1/inbox/conversations now supports filtering by platform=whatsapp, and conversation objects can include new ad attribution data via metadata.

This lets you identify conversations that started from Meta ads (Click-to-Message / Click-to-Direct, and WhatsApp Click-to-WhatsApp) and store/route them differently.

Use platform enum values: facebook, instagram, twitter, bluesky, reddit, telegram, whatsapp

New field: metadata (nullable). Keys are optional and may include:
• WhatsApp CTWA: ctwaclid, ctwasourceid, ctwasourcetype, ctwasourceurl, ctwaheadline, ctwacapturedat
• IG/FB ads: metaadid, metaadsource, metaadtype, metaadref, metaadtitle, metaadphotourl, metaadvideourl, metaadpostid, metaadproductid, metaadflowid, metaadcapturedat

GET /v1/inbox/conversations/{conversationId} also returns metadatametaad*` family there.