Completed
Expose LinkedIn B2B facets in /v1/ads/targeting/search
/v1/ads/targeting/search currently exposes only the interests facet for LinkedIn. The B2B facets that actually matter for our customers, industries, job functions, seniorities and company sizes, have to be passed as URN id fragments we supply ourselves, and there is no way to search them by name. Why it matters to us: we maintain our own static lists of LinkedIn's facet codes, currently 147 industries, 26 job functions, 10 seniorities and 9 company sizes. That means two things. We carry the risk that those lists drift from LinkedIn's own tables without us noticing, and our users can't type "roofing" and get the matching industry, they can only pick from a list we happened to include. What would help: name search over those four facets in the same endpoint, returning the URN we should pass back. We don't need anything clever, just lookup, so we can stop maintaining a copy of someone else's taxonomy.

JW Stukart about 3 hours ago
Completed
Expose LinkedIn B2B facets in /v1/ads/targeting/search
/v1/ads/targeting/search currently exposes only the interests facet for LinkedIn. The B2B facets that actually matter for our customers, industries, job functions, seniorities and company sizes, have to be passed as URN id fragments we supply ourselves, and there is no way to search them by name. Why it matters to us: we maintain our own static lists of LinkedIn's facet codes, currently 147 industries, 26 job functions, 10 seniorities and 9 company sizes. That means two things. We carry the risk that those lists drift from LinkedIn's own tables without us noticing, and our users can't type "roofing" and get the matching industry, they can only pick from a list we happened to include. What would help: name search over those four facets in the same endpoint, returning the URN we should pass back. We don't need anything clever, just lookup, so we can stop maintaining a copy of someone else's taxonomy.

JW Stukart about 3 hours ago
Update location targeting on an existing Google campaign
Device targeting on Google is editable through targeting.devices on the ad route. Locations are not: any other targeting field on an existing Google campaign returns a 400, so a campaign that targets the wrong region has to be recreated or fixed in Google Ads. Why it matters to us: region is the single most common thing a local business wants to change. An installer who adds a second service area, or someone who realises they're paying for clicks two provinces away, is making a small correction, not starting over. "Delete this campaign and build a new one" loses the history and the learning, and it's a lot to ask for what feels like editing one line. What would help: allow updating the location set on an existing campaign, even with the same constraint that already applies elsewhere, where an update replaces the full set rather than merging it. We can work with "send the complete list you want to keep"; we already do exactly that for LinkedIn targeting.

JW Stukart about 3 hours ago
Update location targeting on an existing Google campaign
Device targeting on Google is editable through targeting.devices on the ad route. Locations are not: any other targeting field on an existing Google campaign returns a 400, so a campaign that targets the wrong region has to be recreated or fixed in Google Ads. Why it matters to us: region is the single most common thing a local business wants to change. An installer who adds a second service area, or someone who realises they're paying for clicks two provinces away, is making a small correction, not starting over. "Delete this campaign and build a new one" loses the history and the learning, and it's a lot to ask for what feels like editing one line. What would help: allow updating the location set on an existing campaign, even with the same constraint that already applies elsewhere, where an update replaces the full set rather than merging it. We can work with "send the complete list you want to keep"; we already do exactly that for LinkedIn targeting.

JW Stukart about 3 hours ago
Edit creative on Google image and Performance Max campaigns
Today we can replace the creative on a Google search campaign through the top-level headlines / descriptions / finalUrls arrays on PUT /v1/ads/{adId}, and that works well. For Google campaigns with imagery (display and Performance Max) there is no equivalent: the text can't be changed afterwards and the image can't be replaced at all. Why it matters to us: we build campaigns for small business owners who don't log into Google Ads themselves. When their ad needs a new photo or a sharper line, the whole point of our tool is that they can do it where they already are. Right now our only honest answer is "this one you have to do in Google Ads", which is exactly the step they hired a tool to avoid. What would help, in order of usefulness: 1. Replacing individual assets (an image, a headline) on an existing image or PMax campaign. 2. If replacing in place isn't possible, an endpoint that swaps the whole asset set at once, the way the search arrays already work. Meta and LinkedIn already support both text and image edits after creation, so for us this is the one platform where the flow breaks.

JW Stukart about 3 hours ago
Edit creative on Google image and Performance Max campaigns
Today we can replace the creative on a Google search campaign through the top-level headlines / descriptions / finalUrls arrays on PUT /v1/ads/{adId}, and that works well. For Google campaigns with imagery (display and Performance Max) there is no equivalent: the text can't be changed afterwards and the image can't be replaced at all. Why it matters to us: we build campaigns for small business owners who don't log into Google Ads themselves. When their ad needs a new photo or a sharper line, the whole point of our tool is that they can do it where they already are. Right now our only honest answer is "this one you have to do in Google Ads", which is exactly the step they hired a tool to avoid. What would help, in order of usefulness: 1. Replacing individual assets (an image, a headline) on an existing image or PMax campaign. 2. If replacing in place isn't possible, an endpoint that swaps the whole asset set at once, the way the search arrays already work. Meta and LinkedIn already support both text and image edits after creation, so for us this is the one platform where the flow breaks.

JW Stukart about 3 hours ago
TikTok: expose per-video audience countries and watch-through via the Accounts API
When a TikTok video takes off, I want to read its viewer countries and watch-through rate from the API, so I can tell whether the reach landed in a market the business actually sells to, and whether the opening seconds held attention — without opening TikTok Studio by hand. Problem. For TikTok organic, /v1/analytics returns only views, likes, comments and shares. reach, completionRate, profileViews and clicks come back 0, and videoDurationSeconds null, on every video we've checked. /v1/analytics/tiktok/account-insights adds only cumulative follower / like / video counters. The gap is that these metrics do exist upstream. On the "Video retention graph" thread you noted TikTok publishes "only averages such as average watch time" — that's right, and those averages are exactly what we're asking for. They live on TikTok's Accounts (Organic) API at business-api.tiktok.com, where business/video/list returns, per video: audience_countries, full_video_watched_rate, average_time_watched, total_time_watched, reach and impression_sources. Worth noting the /v1/analytics/tiktok/account-insights docs currently state watch time, impression_sources and reach are "not available on any public TikTok API, even for Business accounts". That's accurate for the Display API scopes the TikTok connection requests today (user.info.basic|profile|stats, video.list, video.publish|upload), but reads as broader than intended — and it contradicts the averages you acknowledged on that thread. This is also a different case from the IG per-post country request you rejected in August. That answer was right: Meta has no geo dimension on media insights at any version. TikTok is the opposite — the platform does expose it per video, so the bar set there ("if the platform ever adds it, we will wire it up") is already met. Not asking for a per-second retention curve. You've already established TikTok publishes none, and we agree. A single watch-through rate per video is the realistic ceiling and is enough to act on. Frequency. Every content review — weekly per account, and in every monthly client report. Current workaround. Opening TikTok Studio by hand, video by video, and transcribing the Locations list and the watch-through figure into a report. It doesn't scale past a handful of accounts and can't be automated at all. Desired outcome. A TikTok video's viewer-country split and watch-through metrics are readable from the API — whether surfaced on /v1/analytics per post, or as a /v1/analytics/tiktok/video-insights sibling to the existing YouTube and Instagram endpoints. Open to the shape; the Accounts API authorization is the gating piece. That same authorization is what the separate TikTok comment-moderation request needs, so the two share one integration cost.

Henrik Raitasola about 7 hours ago
TikTok: expose per-video audience countries and watch-through via the Accounts API
When a TikTok video takes off, I want to read its viewer countries and watch-through rate from the API, so I can tell whether the reach landed in a market the business actually sells to, and whether the opening seconds held attention — without opening TikTok Studio by hand. Problem. For TikTok organic, /v1/analytics returns only views, likes, comments and shares. reach, completionRate, profileViews and clicks come back 0, and videoDurationSeconds null, on every video we've checked. /v1/analytics/tiktok/account-insights adds only cumulative follower / like / video counters. The gap is that these metrics do exist upstream. On the "Video retention graph" thread you noted TikTok publishes "only averages such as average watch time" — that's right, and those averages are exactly what we're asking for. They live on TikTok's Accounts (Organic) API at business-api.tiktok.com, where business/video/list returns, per video: audience_countries, full_video_watched_rate, average_time_watched, total_time_watched, reach and impression_sources. Worth noting the /v1/analytics/tiktok/account-insights docs currently state watch time, impression_sources and reach are "not available on any public TikTok API, even for Business accounts". That's accurate for the Display API scopes the TikTok connection requests today (user.info.basic|profile|stats, video.list, video.publish|upload), but reads as broader than intended — and it contradicts the averages you acknowledged on that thread. This is also a different case from the IG per-post country request you rejected in August. That answer was right: Meta has no geo dimension on media insights at any version. TikTok is the opposite — the platform does expose it per video, so the bar set there ("if the platform ever adds it, we will wire it up") is already met. Not asking for a per-second retention curve. You've already established TikTok publishes none, and we agree. A single watch-through rate per video is the realistic ceiling and is enough to act on. Frequency. Every content review — weekly per account, and in every monthly client report. Current workaround. Opening TikTok Studio by hand, video by video, and transcribing the Locations list and the watch-through figure into a report. It doesn't scale past a handful of accounts and can't be automated at all. Desired outcome. A TikTok video's viewer-country split and watch-through metrics are readable from the API — whether surfaced on /v1/analytics per post, or as a /v1/analytics/tiktok/video-insights sibling to the existing YouTube and Instagram endpoints. Open to the shape; the Accounts API authorization is the gating piece. That same authorization is what the separate TikTok comment-moderation request needs, so the two share one integration cost.

Henrik Raitasola about 7 hours ago
Threads/IG/Facebook location search (quick implementation)
Threads location search api - that should give location ids for facebook/instagram/threads

ShotOnDJI 1 day ago
Threads/IG/Facebook location search (quick implementation)
Threads location search api - that should give location ids for facebook/instagram/threads

ShotOnDJI 1 day ago
Rejected
Graduate a trial reel via the API
Today trialParams.graduationStrategy can only be set at creation. With MANUAL, the actual "share to followers" step has to be done by hand in the Instagram app, which breaks the workflow for anyone publishing through the API: the reel is created programmatically, but the decision that makes it reach the audience is not. Two things would close the loop: An endpoint to graduate an existing trial reel (share it to followers) by post ID, so the decision can be taken from the tool that published it. A way to know that a graduation happened — a field on the post or a webhook — including for SS_PERFORMANCE. Right now, when Instagram auto-graduates, we never learn about it, so we cannot tell whether a reel reached our followers, and any performance comparison between a trial reel and a normal post is unreliable. Of the two, (2) matters more: without it we're publishing into a state we can never read back.

Thomas Rodier 2 days ago
Rejected
Graduate a trial reel via the API
Today trialParams.graduationStrategy can only be set at creation. With MANUAL, the actual "share to followers" step has to be done by hand in the Instagram app, which breaks the workflow for anyone publishing through the API: the reel is created programmatically, but the decision that makes it reach the audience is not. Two things would close the loop: An endpoint to graduate an existing trial reel (share it to followers) by post ID, so the decision can be taken from the tool that published it. A way to know that a graduation happened — a field on the post or a webhook — including for SS_PERFORMANCE. Right now, when Instagram auto-graduates, we never learn about it, so we cannot tell whether a reel reached our followers, and any performance comparison between a trial reel and a normal post is unreliable. Of the two, (2) matters more: without it we're publishing into a state we can never read back.

Thomas Rodier 2 days ago
Completed
Adding Facebook catalog and the post option for 5 headlines and primary text in Facebook ads
Hi Zernio team, I'd like to request two features related to Facebook Ads. Catalogs: connecting a catalog currently returns error #100. Multiple headlines and primary texts: it's not possible to add more than one headline or primary text to an ad, while the Meta API allows up to five of each. It will help my platform greatly is these could be added. Thanks in advance, Damian adhocq.io

Mark Eter 2 days ago
Completed
Adding Facebook catalog and the post option for 5 headlines and primary text in Facebook ads
Hi Zernio team, I'd like to request two features related to Facebook Ads. Catalogs: connecting a catalog currently returns error #100. Multiple headlines and primary texts: it's not possible to add more than one headline or primary text to an ad, while the Meta API allows up to five of each. It will help my platform greatly is these could be added. Thanks in advance, Damian adhocq.io

Mark Eter 2 days ago
Manual Sound Picker for Instagram (Trial) Reels for Dashboard
As someone not knowledgeable enough to use API, I think it would be wonderful to have a music picker or even similar as ‘add random sound’ currently available for TikTok Images, also for regular and Trial Reels. I have only seen this function in VERY limited other social media tools so far (Metricool, OneUp). My marketing niche contains a lot of ‘DIY’ marketers, who are also not versed in API and developing and would have great use for a social media tool that makes this easy.

C. S. 2 days ago
Manual Sound Picker for Instagram (Trial) Reels for Dashboard
As someone not knowledgeable enough to use API, I think it would be wonderful to have a music picker or even similar as ‘add random sound’ currently available for TikTok Images, also for regular and Trial Reels. I have only seen this function in VERY limited other social media tools so far (Metricool, OneUp). My marketing niche contains a lot of ‘DIY’ marketers, who are also not versed in API and developing and would have great use for a social media tool that makes this easy.

C. S. 2 days ago
Rejected
Feature request: Edit and unsend Instagram DMs via Inbox API
Hi Zernio team, We use Zernio’s Inbox API to send and receive Instagram DMs inside our CRM. We’d like to request support for two actions on messages sent by the connected Instagram account: Edit a sent Instagram DM. Delete/unsend a sent Instagram DM. We saw that Zernio already has generic message endpoints: PATCH /v1/inbox/conversations/{conversationId}/messages/{messageId} DELETE /v1/inbox/conversations/{conversationId}/messages/{messageId} However, the documentation currently says editing is only supported for Telegram, and deleting is not supported for Instagram. Our use case is to let support/sales agents quickly correct or remove messages sent by mistake from our CRM, with local time limits and audit logs. We already support this flow for WhatsApp through another provider, and would like to offer a similar experience for Instagram. Do you have plans to support editing or unsending Instagram DMs via API? If this is a Meta/Instagram API limitation, could you confirm whether there is any alternative approach or recommended implementation? Thank you.

Diogo Salvador 3 days ago
Rejected
Feature request: Edit and unsend Instagram DMs via Inbox API
Hi Zernio team, We use Zernio’s Inbox API to send and receive Instagram DMs inside our CRM. We’d like to request support for two actions on messages sent by the connected Instagram account: Edit a sent Instagram DM. Delete/unsend a sent Instagram DM. We saw that Zernio already has generic message endpoints: PATCH /v1/inbox/conversations/{conversationId}/messages/{messageId} DELETE /v1/inbox/conversations/{conversationId}/messages/{messageId} However, the documentation currently says editing is only supported for Telegram, and deleting is not supported for Instagram. Our use case is to let support/sales agents quickly correct or remove messages sent by mistake from our CRM, with local time limits and audit logs. We already support this flow for WhatsApp through another provider, and would like to offer a similar experience for Instagram. Do you have plans to support editing or unsending Instagram DMs via API? If this is a Meta/Instagram API limitation, could you confirm whether there is any alternative approach or recommended implementation? Thank you.

Diogo Salvador 3 days ago
Rejected
Profile Picture/avatar Whatsapp
I would like to request that the contact profile/avatar URL be included in the webhook payload—similar to how it was implemented for the Instagram webhook—so that we can display it in our inbox conversation list.

Daniel Pedrosa 3 days ago
Rejected
Profile Picture/avatar Whatsapp
I would like to request that the contact profile/avatar URL be included in the webhook payload—similar to how it was implemented for the Instagram webhook—so that we can display it in our inbox conversation list.

Daniel Pedrosa 3 days ago
Completed
Support message_send_ttl_seconds for WhatsApp templates
We use POST /v1/whatsapp/templates to automatically provision Utility templates for each connected WABA. Meta supports message_send_ttl_seconds, but Zernio’s current schema does not expose or pass this field through. Our use case requires: message_send_ttl_seconds: 600 so time-sensitive Utility messages expire after 10 minutes instead of using Meta’s 30-day API default. Ideally, POST /v1/whatsapp/templates should accept and pass message_send_ttl_seconds through to Meta. Support for updating the TTL as well, if Meta allows it, would also be useful. Current impact: automatically provisioned templates cannot use a short TTL, which can allow stale Utility messages to be delivered long after they are relevant.

Jorge Mora S. 4 days ago
Completed
Support message_send_ttl_seconds for WhatsApp templates
We use POST /v1/whatsapp/templates to automatically provision Utility templates for each connected WABA. Meta supports message_send_ttl_seconds, but Zernio’s current schema does not expose or pass this field through. Our use case requires: message_send_ttl_seconds: 600 so time-sensitive Utility messages expire after 10 minutes instead of using Meta’s 30-day API default. Ideally, POST /v1/whatsapp/templates should accept and pass message_send_ttl_seconds through to Meta. Support for updating the TTL as well, if Meta allows it, would also be useful. Current impact: automatically provisioned templates cannot use a short TTL, which can allow stale Utility messages to be delivered long after they are relevant.

Jorge Mora S. 4 days ago
someone mentioned me somewhere else on FB/IG" detection that isn't there yet
i need this feature Meta is activity on your own content: comments and DMs on your pages/posts land in the Inbox and fire webhooks. It's specifically the "someone mentioned me somewhere else on FB/IG" detection that isn't there yet. If that Meta mention detection matters

zuber qureshi 4 days ago
someone mentioned me somewhere else on FB/IG" detection that isn't there yet
i need this feature Meta is activity on your own content: comments and DMs on your pages/posts land in the Inbox and fire webhooks. It's specifically the "someone mentioned me somewhere else on FB/IG" detection that isn't there yet. If that Meta mention detection matters

zuber qureshi 4 days ago
TikTok comment moderation via the Business API surface (not Content Posting API)
Following up on a support conversation — TikTok has a separate API tier (business-api.tiktok.com) with real comment management endpoints, distinct from the Content Posting API used for publishing. Specifically: a reply-to-comment endpoint and an update-comment-status endpoint (approve/hide/reject). It's gated behind TikTok Business account approval, so it's a heavier integration than the current publishing flow, but it's a real, documented path — at least one other unified social API in this space has built against it. Flagging the concrete endpoint names since "please add TikTok comments" alone isn't actionable; this is the specific surface to evaluate.

Maruise kamta 4 days ago
TikTok comment moderation via the Business API surface (not Content Posting API)
Following up on a support conversation — TikTok has a separate API tier (business-api.tiktok.com) with real comment management endpoints, distinct from the Content Posting API used for publishing. Specifically: a reply-to-comment endpoint and an update-comment-status endpoint (approve/hide/reject). It's gated behind TikTok Business account approval, so it's a heavier integration than the current publishing flow, but it's a real, documented path — at least one other unified social API in this space has built against it. Flagging the concrete endpoint names since "please add TikTok comments" alone isn't actionable; this is the specific surface to evaluate.

Maruise kamta 4 days ago
Expand hide/unhide to YouTube, LinkedIn, Reddit, and Bluesky
I'm building a SaaS that reads comments across all 8 supported platforms to detect spam/hate/scam content. Right now, hide/unhide only works on Facebook, Instagram, Threads, and X (with the conversation-owner restriction on X). On YouTube, LinkedIn, Reddit, and Bluesky I can detect the same bad content but have no way to act on it beyond delete (which only works on comments the account controls). Parity here would let one moderation logic apply consistently across every platform the Comments API already reads from.

Maruise kamta 5 days ago
Expand hide/unhide to YouTube, LinkedIn, Reddit, and Bluesky
I'm building a SaaS that reads comments across all 8 supported platforms to detect spam/hate/scam content. Right now, hide/unhide only works on Facebook, Instagram, Threads, and X (with the conversation-owner restriction on X). On YouTube, LinkedIn, Reddit, and Bluesky I can detect the same bad content but have no way to act on it beyond delete (which only works on comments the account controls). Parity here would let one moderation logic apply consistently across every platform the Comments API already reads from.

Maruise kamta 5 days ago
Allow liking comments on Instagram via API
Building a white-label comment moderation tool (auto-hide spam, AI-generated replies, auto-like positive engagement) for DTC brands. The like-comment endpoint currently covers Facebook, Bluesky, Reddit, and X, but not Instagram — which is the primary platform for most of my target customers. Auto-liking positive comments is a core part of the product experience, and Instagram is the one platform where I currently can't offer it. Would love to see this added.

Maruise kamta 5 days ago
Allow liking comments on Instagram via API
Building a white-label comment moderation tool (auto-hide spam, AI-generated replies, auto-like positive engagement) for DTC brands. The like-comment endpoint currently covers Facebook, Bluesky, Reddit, and X, but not Instagram — which is the primary platform for most of my target customers. Auto-liking positive comments is a core part of the product experience, and Instagram is the one platform where I currently can't offer it. Would love to see this added.

Maruise kamta 5 days ago
Telegram and Yandex Ads
We are planning to use zernio as plaftorm integrate to our merchant stores, so they could launch/stop/resume ads when needed. Telegram and Yandex ads would be a great addition. So we could focus on building and you could work on integrations

Hojiakbar Karimov 5 days ago
Telegram and Yandex Ads
We are planning to use zernio as plaftorm integrate to our merchant stores, so they could launch/stop/resume ads when needed. Telegram and Yandex ads would be a great addition. So we could focus on building and you could work on integrations

Hojiakbar Karimov 5 days ago
Expose "draft" (Creator Inbox) option for TikTok posts in the Make.com connector
The Zernio API supports tiktokSettings.draft: true to deliver a TikTok post to Creator Inbox instead of direct posting (useful when direct-posting capacity is full). The Make.com "Add a Post to Tiktok" module doesn't expose this as a configurable field — would be great to have it added.

Francisco Vivo Pastor 7 days ago
Expose "draft" (Creator Inbox) option for TikTok posts in the Make.com connector
The Zernio API supports tiktokSettings.draft: true to deliver a TikTok post to Creator Inbox instead of direct posting (useful when direct-posting capacity is full). The Make.com "Add a Post to Tiktok" module doesn't expose this as a configurable field — would be great to have it added.

Francisco Vivo Pastor 7 days ago
Backfill missed comments from the Instagram API when the webhook never arrives
Meta does not send a comment webhook for every comment, so a large share never reach the automation. On our account 311 comments contained the trigger keyword and only 135 were processed. 176 were never seen. Yesterday 57%, today 70%. When it does fire it replies within about 8 seconds, so this is not backlog or slowness. Identical comments on the same post minutes apart either fire instantly or never at all. Because the comment never arrives there is no log row, no error and no skip, so it is invisible until a follower asks why they got no DM. It is also not comment filtering, the missing ones sit in the public comment list and Hidden Words is off. Request: have automations reconcile against the comments you already hold. The Comments tab clearly reads a cached snapshot of the full comment list from Instagram's API, with a lastUpdated stamp per post. Every comment the automation missed is already visible there. So the fetching exists, nothing just compares the two and runs what was skipped. Even a 15 minute sweep over posts from the last 48 hours would close most of the gap. Logging which comments came in via the sweep would also make the size of the gap visible instead of invisible.

z 7 days ago
Backfill missed comments from the Instagram API when the webhook never arrives
Meta does not send a comment webhook for every comment, so a large share never reach the automation. On our account 311 comments contained the trigger keyword and only 135 were processed. 176 were never seen. Yesterday 57%, today 70%. When it does fire it replies within about 8 seconds, so this is not backlog or slowness. Identical comments on the same post minutes apart either fire instantly or never at all. Because the comment never arrives there is no log row, no error and no skip, so it is invisible until a follower asks why they got no DM. It is also not comment filtering, the missing ones sit in the public comment list and Hidden Words is off. Request: have automations reconcile against the comments you already hold. The Comments tab clearly reads a cached snapshot of the full comment list from Instagram's API, with a lastUpdated stamp per post. Every comment the automation missed is already visible there. So the fetching exists, nothing just compares the two and runs what was skipped. Even a 15 minute sweep over posts from the last 48 hours would close most of the gap. Logging which comments came in via the sweep would also make the size of the gap visible instead of invisible.

z 7 days ago