@zernio/node 0.2.987 → 0.2.988

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/dist/index.d.mts +10 -9
  2. package/dist/index.d.ts +10 -9
  3. package/dist/index.js +1 -1
  4. package/dist/index.mjs +1 -1
  5. package/package.json +1 -1
  6. package/src/generated/types.gen.ts +10 -9
package/dist/index.d.mts CHANGED
@@ -38725,11 +38725,11 @@ type UpdateAdSetData = {
38725
38725
  */
38726
38726
  billingEvent?: string;
38727
38727
  /**
38728
- * Ad set start_time (ISO 8601).
38728
+ * Ad set start_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
38729
38729
  */
38730
38730
  startDate?: string;
38731
38731
  /**
38732
- * Ad set end_time (ISO 8601).
38732
+ * Ad set end_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
38733
38733
  */
38734
38734
  endDate?: string;
38735
38735
  /**
@@ -42967,11 +42967,11 @@ type BoostPostData = {
42967
42967
  */
42968
42968
  currency?: string;
42969
42969
  /**
42970
- * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. Same field as on POST /v1/ads/create.
42970
+ * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone. Same field as on POST /v1/ads/create.
42971
42971
  */
42972
42972
  startDate?: string;
42973
42973
  /**
42974
- * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. Same field as on POST /v1/ads/create.
42974
+ * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local. Same field as on POST /v1/ads/create.
42975
42975
  */
42976
42976
  endDate?: string;
42977
42977
  /**
@@ -44110,17 +44110,18 @@ type CreateStandaloneAdData = {
44110
44110
  [key: string]: (number);
44111
44111
  };
44112
44112
  /**
44113
- * Required for lifetime budgets. On TikTok a value without an offset (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone.
44113
+ * Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local.
44114
44114
  */
44115
44115
  endDate?: string;
44116
44116
  /**
44117
44117
  * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's
44118
44118
  * start (Meta `start_time`, TikTok ad group `schedule_start_time`, LinkedIn / Pinterest / X
44119
44119
  * / Google campaign start). When omitted the ad starts delivering immediately. For lifetime
44120
- * budgets Meta also requires `endDate`. On TikTok a value without an offset
44121
- * (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone. The created
44122
- * ad's `schedule` echoes the start and end the platform stored, as UTC instants. Same field
44123
- * as on `POST /v1/ads/boost`.
44120
+ * budgets Meta also requires `endDate`. On Meta and TikTok a value without an offset
44121
+ * (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account
44122
+ * timezone (Meta itself would read it as UTC). The created ad's `schedule` echoes the start
44123
+ * and end the platform stored, as UTC instants; when attaching to an existing ad set
44124
+ * (`adSetId`) it is that ad set's start and end. Same field as on `POST /v1/ads/boost`.
44124
44125
  *
44125
44126
  */
44126
44127
  startDate?: string;
package/dist/index.d.ts CHANGED
@@ -38725,11 +38725,11 @@ type UpdateAdSetData = {
38725
38725
  */
38726
38726
  billingEvent?: string;
38727
38727
  /**
38728
- * Ad set start_time (ISO 8601).
38728
+ * Ad set start_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
38729
38729
  */
38730
38730
  startDate?: string;
38731
38731
  /**
38732
- * Ad set end_time (ISO 8601).
38732
+ * Ad set end_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
38733
38733
  */
38734
38734
  endDate?: string;
38735
38735
  /**
@@ -42967,11 +42967,11 @@ type BoostPostData = {
42967
42967
  */
42968
42968
  currency?: string;
42969
42969
  /**
42970
- * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. Same field as on POST /v1/ads/create.
42970
+ * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone. Same field as on POST /v1/ads/create.
42971
42971
  */
42972
42972
  startDate?: string;
42973
42973
  /**
42974
- * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. Same field as on POST /v1/ads/create.
42974
+ * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local. Same field as on POST /v1/ads/create.
42975
42975
  */
42976
42976
  endDate?: string;
42977
42977
  /**
@@ -44110,17 +44110,18 @@ type CreateStandaloneAdData = {
44110
44110
  [key: string]: (number);
44111
44111
  };
44112
44112
  /**
44113
- * Required for lifetime budgets. On TikTok a value without an offset (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone.
44113
+ * Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local.
44114
44114
  */
44115
44115
  endDate?: string;
44116
44116
  /**
44117
44117
  * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's
44118
44118
  * start (Meta `start_time`, TikTok ad group `schedule_start_time`, LinkedIn / Pinterest / X
44119
44119
  * / Google campaign start). When omitted the ad starts delivering immediately. For lifetime
44120
- * budgets Meta also requires `endDate`. On TikTok a value without an offset
44121
- * (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone. The created
44122
- * ad's `schedule` echoes the start and end the platform stored, as UTC instants. Same field
44123
- * as on `POST /v1/ads/boost`.
44120
+ * budgets Meta also requires `endDate`. On Meta and TikTok a value without an offset
44121
+ * (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account
44122
+ * timezone (Meta itself would read it as UTC). The created ad's `schedule` echoes the start
44123
+ * and end the platform stored, as UTC instants; when attaching to an existing ad set
44124
+ * (`adSetId`) it is that ad set's start and end. Same field as on `POST /v1/ads/boost`.
44124
44125
  *
44125
44126
  */
44126
44127
  startDate?: string;
package/dist/index.js CHANGED
@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
36
36
  // package.json
37
37
  var package_default = {
38
38
  name: "@zernio/node",
39
- version: "0.2.987",
39
+ version: "0.2.988",
40
40
  description: "The official Node.js library for the Zernio API",
41
41
  main: "dist/index.js",
42
42
  module: "dist/index.mjs",
package/dist/index.mjs CHANGED
@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
5
5
  // package.json
6
6
  var package_default = {
7
7
  name: "@zernio/node",
8
- version: "0.2.987",
8
+ version: "0.2.988",
9
9
  description: "The official Node.js library for the Zernio API",
10
10
  main: "dist/index.js",
11
11
  module: "dist/index.mjs",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zernio/node",
3
- "version": "0.2.987",
3
+ "version": "0.2.988",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
package/src/generated/types.gen.ts CHANGED
@@ -39139,11 +39139,11 @@ export type UpdateAdSetData = {
39139
39139
  */
39140
39140
  billingEvent?: string;
39141
39141
  /**
39142
- * Ad set start_time (ISO 8601).
39142
+ * Ad set start_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
39143
39143
  */
39144
39144
  startDate?: string;
39145
39145
  /**
39146
- * Ad set end_time (ISO 8601).
39146
+ * Ad set end_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
39147
39147
  */
39148
39148
  endDate?: string;
39149
39149
  /**
@@ -43684,11 +43684,11 @@ export type BoostPostData = {
43684
43684
  */
43685
43685
  currency?: string;
43686
43686
  /**
43687
- * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. Same field as on POST /v1/ads/create.
43687
+ * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone. Same field as on POST /v1/ads/create.
43688
43688
  */
43689
43689
  startDate?: string;
43690
43690
  /**
43691
- * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. Same field as on POST /v1/ads/create.
43691
+ * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local. Same field as on POST /v1/ads/create.
43692
43692
  */
43693
43693
  endDate?: string;
43694
43694
  /**
@@ -44851,17 +44851,18 @@ export type CreateStandaloneAdData = {
44851
44851
  [key: string]: (number);
44852
44852
  };
44853
44853
  /**
44854
- * Required for lifetime budgets. On TikTok a value without an offset (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone.
44854
+ * Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local.
44855
44855
  */
44856
44856
  endDate?: string;
44857
44857
  /**
44858
44858
  * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's
44859
44859
  * start (Meta `start_time`, TikTok ad group `schedule_start_time`, LinkedIn / Pinterest / X
44860
44860
  * / Google campaign start). When omitted the ad starts delivering immediately. For lifetime
44861
- * budgets Meta also requires `endDate`. On TikTok a value without an offset
44862
- * (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone. The created
44863
- * ad's `schedule` echoes the start and end the platform stored, as UTC instants. Same field
44864
- * as on `POST /v1/ads/boost`.
44861
+ * budgets Meta also requires `endDate`. On Meta and TikTok a value without an offset
44862
+ * (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account
44863
+ * timezone (Meta itself would read it as UTC). The created ad's `schedule` echoes the start
44864
+ * and end the platform stored, as UTC instants; when attaching to an existing ad set
44865
+ * (`adSetId`) it is that ad set's start and end. Same field as on `POST /v1/ads/boost`.
44865
44866
  *
44866
44867
  */
44867
44868
  startDate?: string;