@getlatedev/node 0.2.1337 → 0.2.1339

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -10638,7 +10638,10 @@ export const createAdCampaign = <ThrowOnError extends boolean = false>(options:
  *
  * **Live read, then write.** The campaign's switch is read from the platform first. When that
  * live read shows it already in the requested state nothing is written (`updated: 0`,
- * `skipped: 1`, with the reason). Otherwise the switch is written (`updated: 1`), read back and
+ * `skipped: 1`, with the reason), and when the campaign delivers in that state but some of its
+ * ads are stored in the other state (for example ads switched on in the platform's own UI and
+ * still stored `paused`), those ads (up to 20, at most once every 10 minutes per campaign) are
+ * re-read and stored. Otherwise the switch is written (`updated: 1`), read back and
  * stored, and the delivery status of the ads under it (up to 20) is re-read and stored, so an
  * immediate GET returns what the platform now reports. A stored switch never skips a write, and
  * when the platform cannot be read the write always goes out. On Meta the check reads the
@@ -11202,8 +11205,8 @@ export const duplicateAd = <ThrowOnError extends boolean = false>(options: Optio
  *
  * Reads the ad set live from Meta, returned verbatim. The default projection includes
  * `learning_stage_info` (learning-phase status: LEARNING / SUCCESS / FAIL / WAIVING; Meta
- * omits its `status` key on paused ad sets), delivery settings, budgets, schedule and
- * targeting. `fields` is a raw-passthrough override; unknown fields return Meta's 400
+ * omits its `status` key on paused ad sets), delivery settings, budgets, schedule, dayparting
+ * (`adset_schedule`, `pacing_type`) and targeting. `fields` is a raw-passthrough override; unknown fields return Meta's 400
  * verbatim.
  */
 export const getAdSetDetails = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAdSetDetailsData, ThrowOnError>) => {
@@ -11332,7 +11335,10 @@ export const deleteAdSet = <ThrowOnError extends boolean = false>(options: Optio
  *
  * **Live read, then write.** The ad set's switch is read from the platform
  * first. When that live read shows it already in the requested state
- * nothing is written (`updated: 0`, `skipped: 1`, with the reason).
+ * nothing is written (`updated: 0`, `skipped: 1`, with the reason), and
+ * when the ad set delivers in that state but some of its ads are stored in
+ * the other state, those ads (up to 20, at most once every 10 minutes per
+ * ad set) are re-read and stored.
  * Otherwise the switch is written (`updated: 1`), read back and stored, and
  * the delivery status of its ads (up to 20) is re-read and stored, so an
  * immediate GET returns what the platform now reports. A stored switch

package/src/generated/types.gen.ts

@@ -10088,6 +10088,27 @@ export type MessengerIceBreakerLocale = {
     }>;
 };
 
+/**
+ * Meta ad set dayparting: the hours the ad set delivers, in whole hours. Same `dayOfWeek` /
+ * `startHour` / `endHour` naming as the Google `PUT /v1/ads/campaigns/{campaignId}/ad-schedule`,
+ * but Meta has no minutes and no bid modifiers. Windows on one day must not overlap (adjacent is
+ * fine) and every window must use the same `timezoneType`. Invalid windows are a 400 on
+ * `platformSpecificData.adSchedule`.
+ *
+ */
+export type MetaAdSchedule = Array<{
+    dayOfWeek: 'MONDAY' | 'TUESDAY' | 'WEDNESDAY' | 'THURSDAY' | 'FRIDAY' | 'SATURDAY' | 'SUNDAY';
+    startHour: number;
+    /**
+     * Must be after startHour. 24 is midnight at the end of the day.
+     */
+    endHour: number;
+    /**
+     * Meta `timezone_type`: USER runs the hours in each viewer's time zone, ADVERTISER in the ad account time zone.
+     */
+    timezoneType?: 'USER' | 'ADVERTISER';
+}>;
+
 /**
  * Meta (facebook/instagram) options for platformSpecificData on POST /v1/ads/boost and /v1/ads/create. Unknown keys are rejected, not dropped.
  */
@@ -10110,6 +10131,15 @@ export type MetaAdsPlatformData = {
      */
     lifetimeMinSpendTarget?: number;
     customerLifecycle?: MetaCustomerLifecycle;
+    /**
+     * Dayparting on the ad set being created (Meta `adset_schedule` with `pacing_type: ["day_parting"]`).
+     * Meta runs a schedule only on a LIFETIME budget, so a daily budget (on the ad set, or on the
+     * campaign joined with `existingCampaignId`) is a 400 with `param: platformSpecificData.adSchedule`.
+     * Also a 400 when empty, in adSetId attach mode and with `buyingType: RESERVED`. Change it later with
+     * `PUT /v1/ads/ad-sets/{adSetId}`.
+     *
+     */
+    adSchedule?: (MetaAdSchedule);
 };
 
 export type MetaAssignedUser = {
@@ -46197,6 +46227,17 @@ export type UpdateAdSetData = {
              */
             lifetimeMinSpendTarget?: number;
             customerLifecycle?: MetaCustomerLifecycle;
+            /**
+             * Replaces the ad set's dayparting (Meta `adset_schedule`, `pacing_type: ["day_parting"]`).
+             * Meta runs a schedule only on a lifetime budget. Before anything in the request is written,
+             * Zernio takes `budget.type` from the same request or reads the ad set's budget (or its
+             * campaign's under Advantage campaign budget), and a daily one is a 400 with
+             * `param: platformSpecificData.adSchedule`. An empty array removes the schedule
+             * (`pacing_type: ["standard"]`). Read it back with `GET /v1/ads/ad-sets/{adSetId}`
+             * (`adset_schedule`, `pacing_type`) or as `adSchedule` on `GET /v1/ads/accounts/live`.
+             *
+             */
+            adSchedule?: (MetaAdSchedule);
             /**
              * Meta ad-set promoted_object (same shape as /v1/ads/create). Meta makes promoted_object immutable once the ad set exists, so only `pixelId`, `customEventType`, `customEventStr` (with `customEventType` OTHER), `applicationId` and `productCatalogId` can be sent here. Any other key (`pageId`, `whatsappPhoneNumber`, `customConversionId`, `objectStoreUrl`, `productSetId`, `offlineConversionDataSetId`) is a 400 with `param: platformSpecificData.promotedObject` and nothing is written; changing them needs a new ad set (POST /v1/ads/create). Unknown keys are rejected with 400.
              */
@@ -51003,6 +51044,10 @@ export type GetAdAccountLiveEntitiesResponse = ({
              */
             endDate?: string;
         } | null;
+        /**
+         * Meta only. The ad set's dayparting (`adset_schedule`) in the `platformSpecificData.adSchedule` shape, one window per day (a window Meta stores off the hour is widened to whole hours). Null when the ad set runs around the clock. Absent on TikTok.
+         */
+        adSchedule?: (MetaAdSchedule | null);
     }>;
     /**
      * One entry per level read. `after` is null on the last page.