@getlatedev/node 0.2.1375 → 0.2.1377

package/dist/index.d.mts

@@ -57935,9 +57935,31 @@ type EstimateAdReachData = {
          */
         adAccountId: string;
         /**
-         * The targeting spec to estimate. Same shape used by POST /v1/ads/create.
+         * The targeting spec to estimate. Same shape used by POST /v1/ads/create. Required unless `rawTargeting` is sent; with `rawTargeting` it can be omitted or minimal.
          */
-        spec: (TargetingSpec);
+        spec?: (TargetingSpec);
+        /**
+         * Meta only. A Meta-native targeting spec (snake_case: `geo_locations`, `age_min`,
+         * `flexible_spec`, `excluded_custom_audiences`, `user_os`, ...), the same field
+         * `POST /v1/ads/create` accepts, so the estimate covers the exact audience the ad
+         * set will use. For layered targeting, send `flexible_spec` here: entries AND
+         * together, ids inside one entry OR.
+         *
+         * It uses the same merge rules as `POST /v1/ads/create`: rawTargeting is the BASE
+         * layer and `spec`, converted to Meta's wire shape, is merged on top key by key,
+         * with `spec` winning on collision. The merge goes one level deep inside
+         * `geo_locations` and `excluded_geo_locations` (spec sub-keys win, raw-only
+         * sub-keys such as `location_types` survive). Array values (`flexible_spec`, ...)
+         * are replaced as a whole key when `spec` builds them, never element-merged, so
+         * `spec.interests` or `spec.behaviors` replace a raw `flexible_spec`. The result is
+         * sent to Meta `delivery_estimate` as `targeting_spec`.
+         *
+         * Sending it for an account on another platform returns 400 naming `rawTargeting`.
+         *
+         */
+        rawTargeting?: {
+            [key: string]: unknown;
+        };
         /**
          * Optional. The optimization goal the estimate should assume (platform's
          * own vocabulary, e.g. Meta `REACH`, `LINK_CLICKS`, `OFFSITE_CONVERSIONS`).

package/dist/index.d.ts

@@ -57935,9 +57935,31 @@ type EstimateAdReachData = {
          */
         adAccountId: string;
         /**
-         * The targeting spec to estimate. Same shape used by POST /v1/ads/create.
+         * The targeting spec to estimate. Same shape used by POST /v1/ads/create. Required unless `rawTargeting` is sent; with `rawTargeting` it can be omitted or minimal.
          */
-        spec: (TargetingSpec);
+        spec?: (TargetingSpec);
+        /**
+         * Meta only. A Meta-native targeting spec (snake_case: `geo_locations`, `age_min`,
+         * `flexible_spec`, `excluded_custom_audiences`, `user_os`, ...), the same field
+         * `POST /v1/ads/create` accepts, so the estimate covers the exact audience the ad
+         * set will use. For layered targeting, send `flexible_spec` here: entries AND
+         * together, ids inside one entry OR.
+         *
+         * It uses the same merge rules as `POST /v1/ads/create`: rawTargeting is the BASE
+         * layer and `spec`, converted to Meta's wire shape, is merged on top key by key,
+         * with `spec` winning on collision. The merge goes one level deep inside
+         * `geo_locations` and `excluded_geo_locations` (spec sub-keys win, raw-only
+         * sub-keys such as `location_types` survive). Array values (`flexible_spec`, ...)
+         * are replaced as a whole key when `spec` builds them, never element-merged, so
+         * `spec.interests` or `spec.behaviors` replace a raw `flexible_spec`. The result is
+         * sent to Meta `delivery_estimate` as `targeting_spec`.
+         *
+         * Sending it for an account on another platform returns 400 naming `rawTargeting`.
+         *
+         */
+        rawTargeting?: {
+            [key: string]: unknown;
+        };
         /**
          * Optional. The optimization goal the estimate should assume (platform's
          * own vocabulary, e.g. Meta `REACH`, `LINK_CLICKS`, `OFFSITE_CONVERSIONS`).

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1375",
+  version: "0.2.1377",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1375",
+  version: "0.2.1377",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getlatedev/node",
-  "version": "0.2.1375",
+  "version": "0.2.1377",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -169,7 +169,7 @@ export const getAnalyticsDelta = <ThrowOnError extends boolean = false>(options?
  * Response shape matches /v1/analytics/instagram/account-insights so the same client
  * handling works. Requires yt-analytics.readonly scope (412 with reauthorizeUrl if
  * missing). Data has a 2-3 day delay (endDate is clamped accordingly). Max 89 days,
- * defaults to last 30 days. Requires the Analytics add-on.
+ * defaults to last 30 days.
  *
  * NOT exposed: impressions (Studio thumbnail impressions) and impressionsClickThroughRate.
  * YouTube Analytics API v2 does not expose these for any principal type, not channel
@@ -192,7 +192,7 @@ export const getYouTubeChannelInsights = <ThrowOnError extends boolean = false>(
  * organizationalEntityFollowerStatistics, and organizationPageStatistics endpoints.
  *
  * Response shape matches /v1/analytics/instagram/account-insights. Max 89 days,
- * defaults to last 30 days. Requires the Analytics add-on.
+ * defaults to last 30 days.
  *
  * Scope requirements: r_organization_social, r_organization_followers, and
  * r_organization_admin must all be present on the account. Accounts connected before
@@ -223,7 +223,7 @@ export const getLinkedInOrgAggregateAnalytics = <ThrowOnError extends boolean =
  * time series joined from Zernio's daily snapshotter (AccountStats).
  *
  * Response shape matches /v1/analytics/instagram/account-insights. Max 89 days,
- * defaults to last 30 days. Requires the Analytics add-on and the user.info.stats
+ * defaults to last 30 days. Requires the user.info.stats
  * scope on the account (412 if missing).
  *
  * Scope intentionally narrow: this ACCOUNT-level endpoint exposes only the four
@@ -302,7 +302,7 @@ export const getYouTubeVideoRetention = <ThrowOnError extends boolean = false>(o
  * below. Because Meta did not provide direct adds/removes replacements, Zernio synthesizes
  * followers_gained / followers_lost from the daily follower snapshotter.
  *
- * Max 89 days, defaults to last 30 days. Requires the Analytics add-on.
+ * Max 89 days, defaults to last 30 days.
  *
  */
 export const getFacebookPageInsights = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetFacebookPageInsightsData, ThrowOnError>) => {
@@ -315,7 +315,7 @@ export const getFacebookPageInsights = <ThrowOnError extends boolean = false>(op
 /**
  * Get Facebook post monetization earnings
  * Returns lifetime monetization earnings for ONE Facebook post, read live from Meta on every
- * request. Requires the Analytics add-on.
+ * request.
  *
  * Earnings are CUMULATIVE since the post was published, not earnings within a date range, so
  * this endpoint takes no since/until and the totals must not be summed across dates or across
@@ -344,7 +344,7 @@ export const getFacebookPostEarnings = <ThrowOnError extends boolean = false>(op
  * Returns account-level Instagram insights such as reach, views, accounts engaged, and total interactions.
  * These metrics reflect the entire account's performance across all content surfaces (feed, stories, explore, profile),
  * and are fundamentally different from post-level metrics. Data may be delayed up to 48 hours.
- * Max 90 days, defaults to last 30 days. Requires the Analytics add-on.
+ * Max 90 days, defaults to last 30 days.
  *
  */
 export const getInstagramAccountInsights = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetInstagramAccountInsightsData, ThrowOnError>) => {
@@ -362,7 +362,7 @@ export const getInstagramAccountInsights = <ThrowOnError extends boolean = false
  * via any public API.
  *
  * Response envelope matches /v1/analytics/instagram/account-insights so the same client
- * handling works. Max 89 days, defaults to last 30 days. Requires the Analytics add-on.
+ * handling works. Max 89 days, defaults to last 30 days.
  *
  */
 export const getInstagramFollowerHistory = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetInstagramFollowerHistoryData, ThrowOnError>) => {
@@ -377,7 +377,7 @@ export const getInstagramFollowerHistory = <ThrowOnError extends boolean = false
  * Returns the follower breakdown of a connected Facebook Page by country and/or city, from Meta's latest daily snapshot.
  * Country keys are ISO 3166-1 alpha-2 codes; city keys are "City, Region, Country" strings as Meta returns them.
  * Meta removed age and gender demographics for Pages (page_fans_gender_age) on November 15 2025 with no replacement, so only country and city are available.
- * Meta reports small counts at a privacy floor, so the long tail can show identical low values. Requires the Analytics add-on.
+ * Meta reports small counts at a privacy floor, so the long tail can show identical low values.
  *
  */
 export const getFacebookDemographics = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetFacebookDemographicsData, ThrowOnError>) => {
@@ -406,7 +406,7 @@ export const getLinkedInDemographics = <ThrowOnError extends boolean = false>(op
  * Get Instagram demographics
  * Returns audience demographic insights for an Instagram account, broken down by age, city, country, and/or gender.
  * Requires at least 100 followers. Returns top 45 entries per dimension.
- * Data may be delayed up to 48 hours. Requires the Analytics add-on.
+ * Data may be delayed up to 48 hours.
  *
  */
 export const getInstagramDemographics = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetInstagramDemographicsData, ThrowOnError>) => {
@@ -421,7 +421,7 @@ export const getInstagramDemographics = <ThrowOnError extends boolean = false>(o
  * Returns how many of an Instagram account's followers were online in each hour, for every day of the last 30 days that Meta has data for.
  * Hour keys are "0" to "23" as Meta returns them. endTime is the end_time Meta returns for that day. Meta does not document the timezone of the hour keys.
  * Data is delayed up to 48 hours, so the most recent days are left out until Meta fills them.
- * Requires at least 100 followers; for smaller accounts days is empty. Requires the Analytics add-on.
+ * Requires at least 100 followers; for smaller accounts days is empty.
  *
  */
 export const getInstagramOnlineFollowers = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetInstagramOnlineFollowersData, ThrowOnError>) => {
@@ -438,7 +438,6 @@ export const getInstagramOnlineFollowers = <ThrowOnError extends boolean = false
  * Age and gender values are viewer percentages (0-100). Country values are view counts.
  * Data is based on signed-in viewers only, with a 2-3 day delay. YouTube suppresses demographics
  * for videos with too few signed-in views, so low-traffic videos can return empty breakdowns.
- * Requires the Analytics add-on.
  *
  */
 export const getYouTubeDemographics = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetYouTubeDemographicsData, ThrowOnError>) => {
@@ -452,7 +451,7 @@ export const getYouTubeDemographics = <ThrowOnError extends boolean = false>(opt
  * Get daily aggregated metrics
  * Returns daily aggregated analytics metrics and a per-platform breakdown.
  * Each day includes post count, platform distribution, and summed metrics (impressions, reach, likes, comments, shares, saves, clicks, views).
- * Defaults to the last 180 days. Requires the Analytics add-on.
+ * Defaults to the last 180 days.
  *
  */
 export const getDailyMetrics = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<GetDailyMetricsData, ThrowOnError>) => {
@@ -467,7 +466,7 @@ export const getDailyMetrics = <ThrowOnError extends boolean = false>(options?:
  * Everything an analytics dashboard needs in one call: window totals, follower growth, a per-day series, top posts, recent posts and, optionally, the same figures for the previous period.
  * Daily and total metrics use received attribution: each day holds the engagement that arrived that day, on any post, so `totals` is always the sum of `daily`.
  * `topPosts` and `recentPosts` list posts published in the window with their lifetime metrics. A post cross-posted to several platforms appears once per platform.
- * All dates are UTC days. Requires the Analytics add-on.
+ * All dates are UTC days.
  *
  */
 export const getAnalyticsDashboard = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAnalyticsDashboardData, ThrowOnError>) => {
@@ -481,7 +480,7 @@ export const getAnalyticsDashboard = <ThrowOnError extends boolean = false>(opti
  * Get best times to post
  * Returns the best times to post based on historical engagement data.
  * Groups all published posts by day of week and hour (UTC), calculating average engagement per slot.
- * Use this to auto-schedule posts at optimal times. Requires the Analytics add-on.
+ * Use this to auto-schedule posts at optimal times.
  *
  */
 export const getBestTimeToPost = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<GetBestTimeToPostData, ThrowOnError>) => {
@@ -496,7 +495,6 @@ export const getBestTimeToPost = <ThrowOnError extends boolean = false>(options?
  * Returns how engagement accumulates over time after a post is published.
  * Each bucket shows what percentage of the post's total engagement had been reached by that time window.
  * Useful for understanding content lifespan (e.g. "posts reach 78% of total engagement within 24 hours").
- * Requires the Analytics add-on.
  *
  */
 export const getContentDecay = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<GetContentDecayData, ThrowOnError>) => {
@@ -511,7 +509,6 @@ export const getContentDecay = <ThrowOnError extends boolean = false>(options?:
  * Returns the correlation between posting frequency (posts per week) and engagement rate, broken down by platform.
  * Helps find the optimal posting cadence for each platform. Each row represents a specific (platform, posts_per_week) combination
  * with the average engagement rate observed across all weeks matching that frequency.
- * Requires the Analytics add-on.
  *
  */
 export const getPostingFrequency = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<GetPostingFrequencyData, ThrowOnError>) => {
@@ -817,7 +814,7 @@ export const cancelPayoutBatch = <ThrowOnError extends boolean = false>(options:
  * Get post analytics timeline
  * Returns a daily timeline of analytics metrics for a specific post, showing how impressions, likes,
  * and other metrics evolved day-by-day since publishing. Each row represents one day of data per platform.
- * For multi-platform Zernio posts, returns separate rows for each platform. Requires the Analytics add-on.
+ * For multi-platform Zernio posts, returns separate rows for each platform.
  *
  */
 export const getPostTimeline = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetPostTimelineData, ThrowOnError>) => {
@@ -878,7 +875,7 @@ export const getGoogleAnalyticsMetadata = <ThrowOnError extends boolean = false>
  * ends with one final read, after which the `post.tracking_completed` webhook fires. Identify the post
  * with `postId` (an external post id from Zernio), or with `accountId` together with the post's `url`.
  * Opening a window for a post that is already tracked returns the existing window with `200`. A new
- * window returns `201`. Requires the Analytics add-on.
+ * window returns `201`.
  *
  */
 export const openTrackingWindow = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<OpenTrackingWindowData, ThrowOnError>) => {
@@ -891,7 +888,7 @@ export const openTrackingWindow = <ThrowOnError extends boolean = false>(options
 /**
  * List tracking windows
  * Lists the tracking windows you can see, newest first. Each window carries the latest verified
- * numbers we read from the platform. Requires the Analytics add-on.
+ * numbers we read from the platform.
  *
  */
 export const listTrackingWindows = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<ListTrackingWindowsData, ThrowOnError>) => {
@@ -904,7 +901,7 @@ export const listTrackingWindows = <ThrowOnError extends boolean = false>(option
 /**
  * Get a tracking window
  * Returns one tracking window with the latest verified numbers we read from the platform. Once the window
- * has completed, `finalReadAt` and `completionReason` say how it closed. Requires the Analytics add-on.
+ * has completed, `finalReadAt` and `completionReason` say how it closed.
  *
  */
 export const getTrackingWindow = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetTrackingWindowData, ThrowOnError>) => {
@@ -918,7 +915,7 @@ export const getTrackingWindow = <ThrowOnError extends boolean = false>(options:
  * Cancel a tracking window
  * Stops tracking and returns the window with its final status. A window that already completed keeps its
  * `completed` status and its final read. A cancelled window gets no final read and fires no
- * `post.tracking_completed` webhook. Requires the Analytics add-on.
+ * `post.tracking_completed` webhook.
  *
  */
 export const cancelTrackingWindow = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<CancelTrackingWindowData, ThrowOnError>) => {
@@ -934,7 +931,7 @@ export const cancelTrackingWindow = <ThrowOnError extends boolean = false>(optio
  * views and engagement as the platform reported them at `syncedAt`. Zernio only stores what it fetched from
  * the platform, so nothing here was self-reported. `shares` and `saves` are null on platforms that do not
  * return that counter, which is different from a real zero. `watchSeconds` and `completionRate` are null
- * when the platform gives no watch signal. Requires the Analytics add-on.
+ * when the platform gives no watch signal.
  *
  */
 export const getPostSamples = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetPostSamplesData, ThrowOnError>) => {
@@ -951,7 +948,7 @@ export const getPostSamples = <ThrowOnError extends boolean = false>(options: Op
  * samples we fetched from the platform, never from anything the creator or caller reported, and `reasons`
  * lists each factor that lowered it with its weight in points. `confidence` (0 to 1) says how much data
  * the score rests on. A stored score newer than 30 minutes is returned as is, otherwise it is recomputed.
- * The `post.authenticity_changed` webhook fires when a score crosses 40. Requires the Analytics add-on.
+ * The `post.authenticity_changed` webhook fires when a score crosses 40.
  *
  */
 export const getPostAuthenticity = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetPostAuthenticityData, ThrowOnError>) => {
@@ -982,7 +979,6 @@ export const listPostAuthenticity = <ThrowOnError extends boolean = false>(optio
  * Metrics include impressions (Maps/Search, desktop/mobile), website clicks,
  * call clicks, direction requests, conversations, bookings, and food orders.
  * Data may be delayed 2-3 days. Max 18 months of historical data.
- * Requires the Analytics add-on.
  *
  */
 export const getGoogleBusinessPerformance = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetGoogleBusinessPerformanceData, ThrowOnError>) => {
@@ -997,7 +993,7 @@ export const getGoogleBusinessPerformance = <ThrowOnError extends boolean = fals
  * Returns search keywords that triggered impressions for a Google Business Profile location.
  * Data is aggregated monthly. Keywords Google reports only as below a threshold have `impressions` 0 and `impressionsThreshold` set to that threshold.
  * Returns up to 100 keywords per page. When `nextPageToken` is not null, pass it as `pageToken` with the same `startMonth` and `endMonth` to get the next page.
- * Max 18 months of historical data. Requires the Analytics add-on.
+ * Max 18 months of historical data.
  *
  */
 export const getGoogleBusinessSearchKeywords = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetGoogleBusinessSearchKeywordsData, ThrowOnError>) => {

package/src/generated/types.gen.ts

@@ -59162,9 +59162,31 @@ export type EstimateAdReachData = {
          */
         adAccountId: string;
         /**
-         * The targeting spec to estimate. Same shape used by POST /v1/ads/create.
+         * The targeting spec to estimate. Same shape used by POST /v1/ads/create. Required unless `rawTargeting` is sent; with `rawTargeting` it can be omitted or minimal.
          */
-        spec: (TargetingSpec);
+        spec?: (TargetingSpec);
+        /**
+         * Meta only. A Meta-native targeting spec (snake_case: `geo_locations`, `age_min`,
+         * `flexible_spec`, `excluded_custom_audiences`, `user_os`, ...), the same field
+         * `POST /v1/ads/create` accepts, so the estimate covers the exact audience the ad
+         * set will use. For layered targeting, send `flexible_spec` here: entries AND
+         * together, ids inside one entry OR.
+         *
+         * It uses the same merge rules as `POST /v1/ads/create`: rawTargeting is the BASE
+         * layer and `spec`, converted to Meta's wire shape, is merged on top key by key,
+         * with `spec` winning on collision. The merge goes one level deep inside
+         * `geo_locations` and `excluded_geo_locations` (spec sub-keys win, raw-only
+         * sub-keys such as `location_types` survive). Array values (`flexible_spec`, ...)
+         * are replaced as a whole key when `spec` builds them, never element-merged, so
+         * `spec.interests` or `spec.behaviors` replace a raw `flexible_spec`. The result is
+         * sent to Meta `delivery_estimate` as `targeting_spec`.
+         *
+         * Sending it for an account on another platform returns 400 naming `rawTargeting`.
+         *
+         */
+        rawTargeting?: {
+            [key: string]: unknown;
+        };
         /**
          * Optional. The optimization goal the estimate should assume (platform's
          * own vocabulary, e.g. Meta `REACH`, `LINK_CLICKS`, `OFFSITE_CONVERSIONS`).