@getlatedev/node 0.2.1361 → 0.2.1363

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1361",
+  version: "0.2.1363",
   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.1361",
+  version: "0.2.1363",
   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.1361",
+  "version": "0.2.1363",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -11875,6 +11875,15 @@ export const getAdsTimeline = <ThrowOnError extends boolean = false>(options: Op
  * `platformStatus`) and its ad set and campaign switches (`platformAdSetStatus`,
  * `platformCampaignStatus`) are read live.
  *
+ * **Meta ads that are not synced yet.** Pass `accountId` with a Meta `platformAdId` to read an ad
+ * Zernio has not synced (for example one created in Ads Manager on an ad account reached only
+ * through a Facebook connection). The ad is read live from Meta and mapped exactly like a synced
+ * row (name, `status`, `platformStatus`, `configuredStatus`, `platformAdSetId`,
+ * `platformCampaignId`, campaign and ad set names, budgets, and `creative` with its `id`, body,
+ * link, image and video), with `synced: false`, no `id` (it has no Zernio row) and `statusReadAt`
+ * set to the time of the read. Synced ads answer `synced: true`. Only a numeric id takes this
+ * path, so dark post ids (`{pageId}_{postId}`) keep the dark post lookup above.
+ *
  */
 export const getAd = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAdData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetAdResponse, GetAdError, ThrowOnError>({
@@ -12219,6 +12228,9 @@ export const generateAdPreviews = <ThrowOnError extends boolean = false>(options
  * Renders an EXISTING ad per placement via Meta's `/{ad_id}/previews`. Each preview is an HTML
  * `<iframe>` snippet embeddable directly. Unknown `formats` values return Meta's 400 verbatim.
  *
+ * **Meta ads that are not synced yet.** Pass `accountId` with a Meta platform ad id that is not in
+ * Zernio's store to render it live through that connection; the response carries `synced: false`.
+ *
  */
 export const getAdPreviews = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAdPreviewsData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetAdPreviewsResponse, GetAdPreviewsError, ThrowOnError>({
@@ -12263,6 +12275,10 @@ export const getAdPreviews = <ThrowOnError extends boolean = false>(options: Opt
  * `platformStatus`: TikTok reports `AD_STATUS_AUDIT` while the ad is in review and
  * `AD_STATUS_AD_PRE_ONLINE` once it passed and is about to deliver (both map to
  * `status: pending_review`); `AD_STATUS_AUDIT_DENY` maps to `rejected`.
+ *
+ * **Meta ads that are not synced yet.** Pass `accountId` with a Meta platform ad id that is not in
+ * Zernio's store to read its review live through that connection. The response then has
+ * `adId: null`, `synced: false`, and nothing is stored. Synced ads answer `synced: true`.
  */
 export const getAdReview = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAdReviewData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetAdReviewResponse, GetAdReviewError, ThrowOnError>({
@@ -12323,6 +12339,9 @@ export const getTikTokSmartPlusAdReview = <ThrowOnError extends boolean = false>
  * URLs carry an `oe=<hex>` expiration (image_url ~24 h, video source ~12 d). Treat
  * URLs as short-lived: re-fetch this endpoint before serving or downloading assets
  * instead of caching URLs beyond that window.
+ *
+ * **Meta ads that are not synced yet.** Pass `accountId` with a Meta platform ad id that is not in
+ * Zernio's store to read its media live through that connection; the response carries `synced: false`.
  */
 export const getAdMedia = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAdMediaData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetAdMediaResponse, GetAdMediaError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -143,6 +143,10 @@ export type Ad = {
      * True for ads synced from platform ad managers
      */
     isExternal?: boolean;
+    /**
+     * Only on GET /v1/ads/{adId}. True when the ad comes from Zernio's synced store; false when it was read live from Meta because it is not synced yet (request made with `accountId`). An unsynced ad has no `id`.
+     */
+    synced?: boolean;
     budget?: {
         amount?: number;
         type?: 'daily' | 'lifetime';
@@ -2008,6 +2012,10 @@ export type AdTreeAdSet = {
      * LinkedIn only. Why the LinkedIn campaign backing this ad set is (or is not) delivering. A LinkedIn Campaign maps to this ad-set node, so this is the level where LinkedIn's holds actually apply. Empty means no serving data, ["RUNNABLE"] means eligible to serve, anything else is a hold. See the `servingStatuses` field on `Ad` for the known values.
      */
     servingStatuses?: Array<(string)>;
+    /**
+     * Meta only. Where the ad set stands in Meta's learning phase, as of the last sync: LEARNING while delivery is still being optimized (about 50 optimization events in 7 days end it), SUCCESS once it has left learning, FAIL when it could not gather enough events (Ads Manager's "Learning limited"). Null on other platforms and for ad sets not yet synced.
+     */
+    learningStatus?: ('LEARNING' | 'SUCCESS' | 'FAIL') | null;
     /**
      * Meta promoted object for this ad set (conversion event details)
      */
@@ -2026,6 +2034,11 @@ export type AdTreeAdSet = {
     daily?: Array<AdDailyMetrics>;
 };
 
+/**
+ * Meta only. Where the ad set stands in Meta's learning phase, as of the last sync: LEARNING while delivery is still being optimized (about 50 optimization events in 7 days end it), SUCCESS once it has left learning, FAIL when it could not gather enough events (Ads Manager's "Learning limited"). Null on other platforms and for ad sets not yet synced.
+ */
+export type learningStatus = 'LEARNING' | 'SUCCESS' | 'FAIL';
+
 /**
  * Campaign with nested ad sets and rolled-up metrics
  */
@@ -11329,6 +11342,11 @@ export type ParameterLiveStatusRead = boolean;
  */
 export type ParameterPageParam = number;
 
+/**
+ * Meta only. A Zernio connection id (Meta Ads or Facebook connection) used when `{adId}` is a Meta ad id that is not in Zernio's synced store, for example an ad created in Ads Manager on an ad account reached only through a Facebook connection. The ad is then read live from Meta through that connection and the response carries `synced: false`. The same rules as GET /v1/ads/campaigns/{campaignId} apply: a connection on a profile the API key cannot access answers 404, and an ad on an ad account outside the connection's selected ad accounts answers 403 `ad_account_not_selected`. An id Meta cannot read through the connection, or that is not an ad (a campaign or ad set id, for example), answers 404 `ad_not_found`, and a connection that is not Meta answers 501. Ads Meta reports as DELETED are returned too, with their status. Ignored when the ad is in the store (the stored ad's own connection is used). Without it an unsynced ad answers 404 `ad_not_found`. Writes (PUT, DELETE, status) still need the ad in the store.
+ */
+export type ParameterUnsyncedMetaAdAccountId = string;
+
 export type PhoneNumberStockWatch = {
     id: string;
     /**
@@ -48182,6 +48200,10 @@ export type GetAdData = {
         adId: string;
     };
     query?: {
+        /**
+         * Meta only. A Zernio connection id (Meta Ads or Facebook connection) used when `{adId}` is a Meta ad id that is not in Zernio's synced store, for example an ad created in Ads Manager on an ad account reached only through a Facebook connection. The ad is then read live from Meta through that connection and the response carries `synced: false`. The same rules as GET /v1/ads/campaigns/{campaignId} apply: a connection on a profile the API key cannot access answers 404, and an ad on an ad account outside the connection's selected ad accounts answers 403 `ad_account_not_selected`. An id Meta cannot read through the connection, or that is not an ad (a campaign or ad set id, for example), answers 404 `ad_not_found`, and a connection that is not Meta answers 501. Ads Meta reports as DELETED are returned too, with their status. Ignored when the ad is in the store (the stored ad's own connection is used). Without it an unsynced ad answers 404 `ad_not_found`. Writes (PUT, DELETE, status) still need the ad in the store.
+         */
+        accountId?: string;
         /**
          * Read the on/off switches live from the platform instead of returning the synced values. The fresh values are stored (so later reads return them too) and the response carries `statusReadAt`, the time of the read. At most 20 platform objects are read per request. Where a read fails (credentials, platform error, no reader on that platform), the stored values come back with `statusReadAt: null`. See "Status freshness" in the operation description. On X the budget is read live in the same read: on GET /v1/ads/{adId} `budget`, `adSetBudget`, `campaignBudget` and `budgetLevel` are the line item and campaign budgets X holds now (stored like the switches); on the ad set and campaign listings `budget` is the one that line item or campaign holds now (returned, not stored); a row whose budget the other level holds keeps its synced `budget`.
          */
@@ -48200,7 +48222,7 @@ export type GetAdResponse = ({
      */
     stale?: boolean;
     /**
-     * Only with `live=true`. When the switches were read from the platform; null when the live read failed and the stored values were returned.
+     * With `live=true`, when the switches were read from the platform; null when the live read failed and the stored values were returned. Always set on an unsynced Meta ad read with `accountId`, the time of that read.
      */
     statusReadAt?: (string) | null;
     /**
@@ -48240,7 +48262,7 @@ export type GetAdResponse = ({
 
 export type GetAdError = (ErrorResponse | {
     error?: string;
-});
+} | unknown);
 
 export type UpdateAdData = {
     body: {
@@ -48953,11 +48975,15 @@ export type GenerateAdPreviewsError = (unknown | ErrorResponse);
 export type GetAdPreviewsData = {
     path: {
         /**
-         * Zernio ad id (24-char hex).
+         * Zernio ad id (24-char hex) or Meta platform ad id.
          */
         adId: string;
     };
     query?: {
+        /**
+         * Meta only. A Zernio connection id (Meta Ads or Facebook connection) used when `{adId}` is a Meta ad id that is not in Zernio's synced store, for example an ad created in Ads Manager on an ad account reached only through a Facebook connection. The ad is then read live from Meta through that connection and the response carries `synced: false`. The same rules as GET /v1/ads/campaigns/{campaignId} apply: a connection on a profile the API key cannot access answers 404, and an ad on an ad account outside the connection's selected ad accounts answers 403 `ad_account_not_selected`. An id Meta cannot read through the connection, or that is not an ad (a campaign or ad set id, for example), answers 404 `ad_not_found`, and a connection that is not Meta answers 501. Ads Meta reports as DELETED are returned too, with their status. Ignored when the ad is in the store (the stored ad's own connection is used). Without it an unsynced ad answers 404 `ad_not_found`. Writes (PUT, DELETE, status) still need the ad in the store.
+         */
+        accountId?: string;
         /**
          * Comma-separated Meta ad_format values (max 10), one preview per format. Defaults to DESKTOP_FEED_STANDARD.
          */
@@ -48967,6 +48993,10 @@ export type GetAdPreviewsData = {
 
 export type GetAdPreviewsResponse = ({
     adId?: string;
+    /**
+     * False when the ad was read live from Meta because it is not in Zernio's store (request made with `accountId`).
+     */
+    synced?: boolean;
     previews?: Array<{
         format?: string;
         /**
@@ -48985,12 +49015,25 @@ export type GetAdReviewData = {
          */
         adId: string;
     };
+    query?: {
+        /**
+         * Meta only. A Zernio connection id (Meta Ads or Facebook connection) used when `{adId}` is a Meta ad id that is not in Zernio's synced store, for example an ad created in Ads Manager on an ad account reached only through a Facebook connection. The ad is then read live from Meta through that connection and the response carries `synced: false`. The same rules as GET /v1/ads/campaigns/{campaignId} apply: a connection on a profile the API key cannot access answers 404, and an ad on an ad account outside the connection's selected ad accounts answers 403 `ad_account_not_selected`. An id Meta cannot read through the connection, or that is not an ad (a campaign or ad set id, for example), answers 404 `ad_not_found`, and a connection that is not Meta answers 501. Ads Meta reports as DELETED are returned too, with their status. Ignored when the ad is in the store (the stored ad's own connection is used). Without it an unsynced ad answers 404 `ad_not_found`. Writes (PUT, DELETE, status) still need the ad in the store.
+         */
+        accountId?: string;
+    };
 };
 
 export type GetAdReviewResponse = ({
-    adId?: string;
+    /**
+     * Zernio ad id; null for an unsynced Meta ad read with `accountId`.
+     */
+    adId?: (string) | null;
     platform?: string;
     platformAdId?: string;
+    /**
+     * False when the ad was read live from Meta because it is not in Zernio's store.
+     */
+    synced?: boolean;
     review?: {
         /**
          * TikTok `is_approved`. Google and Meta: derived from the platform status (see the description).
@@ -49127,6 +49170,12 @@ export type GetAdMediaData = {
          */
         adId: string;
     };
+    query?: {
+        /**
+         * Meta only. A Zernio connection id (Meta Ads or Facebook connection) used when `{adId}` is a Meta ad id that is not in Zernio's synced store, for example an ad created in Ads Manager on an ad account reached only through a Facebook connection. The ad is then read live from Meta through that connection and the response carries `synced: false`. The same rules as GET /v1/ads/campaigns/{campaignId} apply: a connection on a profile the API key cannot access answers 404, and an ad on an ad account outside the connection's selected ad accounts answers 403 `ad_account_not_selected`. An id Meta cannot read through the connection, or that is not an ad (a campaign or ad set id, for example), answers 404 `ad_not_found`, and a connection that is not Meta answers 501. Ads Meta reports as DELETED are returned too, with their status. Ignored when the ad is in the store (the stored ad's own connection is used). Without it an unsynced ad answers 404 `ad_not_found`. Writes (PUT, DELETE, status) still need the ad in the store.
+         */
+        accountId?: string;
+    };
 };
 
 export type GetAdMediaResponse = ({
@@ -49135,6 +49184,10 @@ export type GetAdMediaResponse = ({
      * 'facebook' or 'instagram'. Only Meta is supported for now.
      */
     platform?: string;
+    /**
+     * False when the ad was read live from Meta because it is not in Zernio's store (request made with `accountId`).
+     */
+    synced?: boolean;
     media?: Array<{
         type?: 'image' | 'video';
         /**