@getlatedev/node 0.2.1314 → 0.2.1316

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.
package/dist/index.d.mts CHANGED
@@ -8180,12 +8180,13 @@ type ErrorResponse = {
8180
8180
  * single reply is already spent, and `privateReplyOutcome: "unknown"` on its 502 when Meta
8181
8181
  * answered a server error and the reply may have been delivered.
8182
8182
  *
8183
- * On a Google Ads 429 it carries `quotaExhausted: true`, which marks the failure as
8184
- * Google's own ads quota rather than a Zernio rate limit, so you can keep calling
8185
- * other platforms instead of backing off everywhere. When Google names the scope it
8186
- * also carries `quotaScope`: `DEVELOPER` means the shared developer-token budget
8187
- * (every Google account is affected and there is nothing to change on your side),
8188
- * `ACCOUNT` means your own ad account. A Meta 429 carries neither field.
8183
+ * On a Google Ads or YouTube Analytics 429 it carries `quotaExhausted: true`, which marks
8184
+ * the failure as Google's own quota rather than a Zernio rate limit, so you can keep
8185
+ * calling other platforms instead of backing off everywhere. When Google names the scope
8186
+ * it also carries `quotaScope`: `DEVELOPER` means the shared budget (the developer token
8187
+ * for Google Ads, the Google Cloud project for YouTube Analytics; every account on
8188
+ * Zernio is affected and there is nothing to change on your side), `ACCOUNT` means your
8189
+ * own ad account (Google Ads only). A Meta 429 carries neither field.
8189
8190
  *
8190
8191
  * A Zernio Google Ads burst-limit 429 carries `budgetScope` instead, and never
8191
8192
  * `quotaExhausted`: these are Zernio's own limits, applied before the call
@@ -8248,11 +8249,11 @@ type ErrorResponse = {
8248
8249
  parentId?: string;
8249
8250
  };
8250
8251
  /**
8251
- * Google Ads 429 only. True when the upstream Google Ads quota is spent rather than a Zernio limit.
8252
+ * Google Ads and YouTube Analytics 429 only. True when the upstream Google quota is spent rather than a Zernio limit.
8252
8253
  */
8253
8254
  quotaExhausted?: boolean;
8254
8255
  /**
8255
- * Google Ads 429 only, when Google names the scope. DEVELOPER is the shared developer-token budget; ACCOUNT is your ad account.
8256
+ * Google Ads and YouTube Analytics 429 only, when the scope is known. DEVELOPER is the shared budget (the developer token for Google Ads, the Google Cloud project for YouTube Analytics); ACCOUNT is your ad account (Google Ads only).
8256
8257
  */
8257
8258
  quotaScope?: 'DEVELOPER' | 'ACCOUNT';
8258
8259
  /**
@@ -8271,7 +8272,7 @@ type type8 = 'invalid_request_error' | 'authentication_error' | 'permission_erro
8271
8272
  */
8272
8273
  type stage = 'media' | 'campaign' | 'adset' | 'creative' | 'ad' | 'activation' | 'other';
8273
8274
  /**
8274
- * Google Ads 429 only, when Google names the scope. DEVELOPER is the shared developer-token budget; ACCOUNT is your ad account.
8275
+ * Google Ads and YouTube Analytics 429 only, when the scope is known. DEVELOPER is the shared budget (the developer token for Google Ads, the Google Cloud project for YouTube Analytics); ACCOUNT is your ad account (Google Ads only).
8275
8276
  */
8276
8277
  type quotaScope = 'DEVELOPER' | 'ACCOUNT';
8277
8278
  /**
@@ -50107,7 +50108,7 @@ type CreateStandaloneAdData = {
50107
50108
  */
50108
50109
  aiDisclosure?: 'OPT_IN' | 'OPT_OUT';
50109
50110
  /**
50110
- * Google Performance Max validates the complete atomic campaign and asset group with no resource creation or local persistence. Google validation still downloads image URLs and consumes quota. On Meta, validates the complete inline campaign, ad set, creative and ad with execution_options validate_only. Nothing is uploaded or created, and validation bypasses Idempotency-Key storage. Supports a single image or existing video.id (each also with bodies[] / headlines[] Multiple Text Options), all-image placementAssets with per-rule copy and text pools, or existingCreativeId; dynamicCreative, translations, carouselCards, placement videos, new video uploads, creatives[], adSetId and RESERVED buying return 400. Placement validation uses existing Instagram identities only. Existing campaign or creative nodes are marked skipped. When Meta cannot dry-run the nested tree (code 2, or an unknown-error code 1 on an OFFSITE_CONVERSIONS ad set nested in a new campaign, which Meta returns for some website-conversion ad sets that it then creates normally), the campaign and creative are validated on their own and the adSet and ad nodes come back unverified with the reason. Success returns 200 with per-node results; Meta rejection returns an error. ChatGPT (OpenAI) has no platform dry-run: Zernio runs every check it knows (creative lengths, budget, bid strategy, targeting) plus live lookups of the conversion event and target countries, and uploads or creates nothing. OpenAI's own write-time checks (image fetch, currency-specific minimums, ad review) still run only on a real create. Any other platform, or a Google campaignType other than pmax or demand_gen, returns 501 `feature_not_available`.
50111
+ * Google Performance Max validates the complete atomic campaign and asset group with no resource creation or local persistence. Google validation still downloads image URLs and consumes quota. On Meta, validates the complete inline campaign, ad set, creative and ad with execution_options validate_only. Nothing is uploaded or created, and validation bypasses Idempotency-Key storage. Supports a single image or existing video.id (each also with bodies[] / headlines[] Multiple Text Options), all-image placementAssets with per-rule copy and text pools, or existingCreativeId; dynamicCreative, translations, carouselCards, placement videos, new video uploads, creatives[], adSetId and RESERVED buying return 400. Placement validation uses existing Instagram identities only. Existing campaign or creative nodes are marked skipped. When Meta cannot dry-run the nested tree (code 2, or an unknown-error code 1 on an OFFSITE_CONVERSIONS ad set nested in a new campaign, which Meta returns for some website-conversion ad sets that it then creates normally, or a code 100 subcode 2446880 "WhatsApp number required" on an ad that does not message on WhatsApp, which Meta returns intermittently and then creates the ad normally), the campaign and creative are validated on their own and the adSet and ad nodes come back unverified with the reason. If the creative's own dry run also asks for a WhatsApp number, the creative comes back unverified too. Messaging ads still fail on 2446880. Success returns 200 with per-node results; Meta rejection returns an error. ChatGPT (OpenAI) has no platform dry-run: Zernio runs every check it knows (creative lengths, budget, bid strategy, targeting) plus live lookups of the conversion event and target countries, and uploads or creates nothing. OpenAI's own write-time checks (image fetch, currency-specific minimums, ad review) still run only on a real create. Any other platform, or a Google campaignType other than pmax or demand_gen, returns 501 `feature_not_available`.
50111
50112
  */
50112
50113
  validateOnly?: boolean;
50113
50114
  /**
package/dist/index.d.ts CHANGED
@@ -8180,12 +8180,13 @@ type ErrorResponse = {
8180
8180
  * single reply is already spent, and `privateReplyOutcome: "unknown"` on its 502 when Meta
8181
8181
  * answered a server error and the reply may have been delivered.
8182
8182
  *
8183
- * On a Google Ads 429 it carries `quotaExhausted: true`, which marks the failure as
8184
- * Google's own ads quota rather than a Zernio rate limit, so you can keep calling
8185
- * other platforms instead of backing off everywhere. When Google names the scope it
8186
- * also carries `quotaScope`: `DEVELOPER` means the shared developer-token budget
8187
- * (every Google account is affected and there is nothing to change on your side),
8188
- * `ACCOUNT` means your own ad account. A Meta 429 carries neither field.
8183
+ * On a Google Ads or YouTube Analytics 429 it carries `quotaExhausted: true`, which marks
8184
+ * the failure as Google's own quota rather than a Zernio rate limit, so you can keep
8185
+ * calling other platforms instead of backing off everywhere. When Google names the scope
8186
+ * it also carries `quotaScope`: `DEVELOPER` means the shared budget (the developer token
8187
+ * for Google Ads, the Google Cloud project for YouTube Analytics; every account on
8188
+ * Zernio is affected and there is nothing to change on your side), `ACCOUNT` means your
8189
+ * own ad account (Google Ads only). A Meta 429 carries neither field.
8189
8190
  *
8190
8191
  * A Zernio Google Ads burst-limit 429 carries `budgetScope` instead, and never
8191
8192
  * `quotaExhausted`: these are Zernio's own limits, applied before the call
@@ -8248,11 +8249,11 @@ type ErrorResponse = {
8248
8249
  parentId?: string;
8249
8250
  };
8250
8251
  /**
8251
- * Google Ads 429 only. True when the upstream Google Ads quota is spent rather than a Zernio limit.
8252
+ * Google Ads and YouTube Analytics 429 only. True when the upstream Google quota is spent rather than a Zernio limit.
8252
8253
  */
8253
8254
  quotaExhausted?: boolean;
8254
8255
  /**
8255
- * Google Ads 429 only, when Google names the scope. DEVELOPER is the shared developer-token budget; ACCOUNT is your ad account.
8256
+ * Google Ads and YouTube Analytics 429 only, when the scope is known. DEVELOPER is the shared budget (the developer token for Google Ads, the Google Cloud project for YouTube Analytics); ACCOUNT is your ad account (Google Ads only).
8256
8257
  */
8257
8258
  quotaScope?: 'DEVELOPER' | 'ACCOUNT';
8258
8259
  /**
@@ -8271,7 +8272,7 @@ type type8 = 'invalid_request_error' | 'authentication_error' | 'permission_erro
8271
8272
  */
8272
8273
  type stage = 'media' | 'campaign' | 'adset' | 'creative' | 'ad' | 'activation' | 'other';
8273
8274
  /**
8274
- * Google Ads 429 only, when Google names the scope. DEVELOPER is the shared developer-token budget; ACCOUNT is your ad account.
8275
+ * Google Ads and YouTube Analytics 429 only, when the scope is known. DEVELOPER is the shared budget (the developer token for Google Ads, the Google Cloud project for YouTube Analytics); ACCOUNT is your ad account (Google Ads only).
8275
8276
  */
8276
8277
  type quotaScope = 'DEVELOPER' | 'ACCOUNT';
8277
8278
  /**
@@ -50107,7 +50108,7 @@ type CreateStandaloneAdData = {
50107
50108
  */
50108
50109
  aiDisclosure?: 'OPT_IN' | 'OPT_OUT';
50109
50110
  /**
50110
- * Google Performance Max validates the complete atomic campaign and asset group with no resource creation or local persistence. Google validation still downloads image URLs and consumes quota. On Meta, validates the complete inline campaign, ad set, creative and ad with execution_options validate_only. Nothing is uploaded or created, and validation bypasses Idempotency-Key storage. Supports a single image or existing video.id (each also with bodies[] / headlines[] Multiple Text Options), all-image placementAssets with per-rule copy and text pools, or existingCreativeId; dynamicCreative, translations, carouselCards, placement videos, new video uploads, creatives[], adSetId and RESERVED buying return 400. Placement validation uses existing Instagram identities only. Existing campaign or creative nodes are marked skipped. When Meta cannot dry-run the nested tree (code 2, or an unknown-error code 1 on an OFFSITE_CONVERSIONS ad set nested in a new campaign, which Meta returns for some website-conversion ad sets that it then creates normally), the campaign and creative are validated on their own and the adSet and ad nodes come back unverified with the reason. Success returns 200 with per-node results; Meta rejection returns an error. ChatGPT (OpenAI) has no platform dry-run: Zernio runs every check it knows (creative lengths, budget, bid strategy, targeting) plus live lookups of the conversion event and target countries, and uploads or creates nothing. OpenAI's own write-time checks (image fetch, currency-specific minimums, ad review) still run only on a real create. Any other platform, or a Google campaignType other than pmax or demand_gen, returns 501 `feature_not_available`.
50111
+ * Google Performance Max validates the complete atomic campaign and asset group with no resource creation or local persistence. Google validation still downloads image URLs and consumes quota. On Meta, validates the complete inline campaign, ad set, creative and ad with execution_options validate_only. Nothing is uploaded or created, and validation bypasses Idempotency-Key storage. Supports a single image or existing video.id (each also with bodies[] / headlines[] Multiple Text Options), all-image placementAssets with per-rule copy and text pools, or existingCreativeId; dynamicCreative, translations, carouselCards, placement videos, new video uploads, creatives[], adSetId and RESERVED buying return 400. Placement validation uses existing Instagram identities only. Existing campaign or creative nodes are marked skipped. When Meta cannot dry-run the nested tree (code 2, or an unknown-error code 1 on an OFFSITE_CONVERSIONS ad set nested in a new campaign, which Meta returns for some website-conversion ad sets that it then creates normally, or a code 100 subcode 2446880 "WhatsApp number required" on an ad that does not message on WhatsApp, which Meta returns intermittently and then creates the ad normally), the campaign and creative are validated on their own and the adSet and ad nodes come back unverified with the reason. If the creative's own dry run also asks for a WhatsApp number, the creative comes back unverified too. Messaging ads still fail on 2446880. Success returns 200 with per-node results; Meta rejection returns an error. ChatGPT (OpenAI) has no platform dry-run: Zernio runs every check it knows (creative lengths, budget, bid strategy, targeting) plus live lookups of the conversion event and target countries, and uploads or creates nothing. OpenAI's own write-time checks (image fetch, currency-specific minimums, ad review) still run only on a real create. Any other platform, or a Google campaignType other than pmax or demand_gen, returns 501 `feature_not_available`.
50111
50112
  */
50112
50113
  validateOnly?: boolean;
50113
50114
  /**
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: "@getlatedev/node",
39
- version: "0.2.1314",
39
+ version: "0.2.1316",
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: "@getlatedev/node",
8
- version: "0.2.1314",
8
+ version: "0.2.1316",
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": "@getlatedev/node",
3
- "version": "0.2.1314",
3
+ "version": "0.2.1316",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -6350,12 +6350,13 @@ export type ErrorResponse = {
6350
6350
  * single reply is already spent, and `privateReplyOutcome: "unknown"` on its 502 when Meta
6351
6351
  * answered a server error and the reply may have been delivered.
6352
6352
  *
6353
- * On a Google Ads 429 it carries `quotaExhausted: true`, which marks the failure as
6354
- * Google's own ads quota rather than a Zernio rate limit, so you can keep calling
6355
- * other platforms instead of backing off everywhere. When Google names the scope it
6356
- * also carries `quotaScope`: `DEVELOPER` means the shared developer-token budget
6357
- * (every Google account is affected and there is nothing to change on your side),
6358
- * `ACCOUNT` means your own ad account. A Meta 429 carries neither field.
6353
+ * On a Google Ads or YouTube Analytics 429 it carries `quotaExhausted: true`, which marks
6354
+ * the failure as Google's own quota rather than a Zernio rate limit, so you can keep
6355
+ * calling other platforms instead of backing off everywhere. When Google names the scope
6356
+ * it also carries `quotaScope`: `DEVELOPER` means the shared budget (the developer token
6357
+ * for Google Ads, the Google Cloud project for YouTube Analytics; every account on
6358
+ * Zernio is affected and there is nothing to change on your side), `ACCOUNT` means your
6359
+ * own ad account (Google Ads only). A Meta 429 carries neither field.
6359
6360
  *
6360
6361
  * A Zernio Google Ads burst-limit 429 carries `budgetScope` instead, and never
6361
6362
  * `quotaExhausted`: these are Zernio's own limits, applied before the call
@@ -6418,11 +6419,11 @@ export type ErrorResponse = {
6418
6419
  parentId?: string;
6419
6420
  };
6420
6421
  /**
6421
- * Google Ads 429 only. True when the upstream Google Ads quota is spent rather than a Zernio limit.
6422
+ * Google Ads and YouTube Analytics 429 only. True when the upstream Google quota is spent rather than a Zernio limit.
6422
6423
  */
6423
6424
  quotaExhausted?: boolean;
6424
6425
  /**
6425
- * Google Ads 429 only, when Google names the scope. DEVELOPER is the shared developer-token budget; ACCOUNT is your ad account.
6426
+ * Google Ads and YouTube Analytics 429 only, when the scope is known. DEVELOPER is the shared budget (the developer token for Google Ads, the Google Cloud project for YouTube Analytics); ACCOUNT is your ad account (Google Ads only).
6426
6427
  */
6427
6428
  quotaScope?: 'DEVELOPER' | 'ACCOUNT';
6428
6429
  /**
@@ -6444,7 +6445,7 @@ export type type8 = 'invalid_request_error' | 'authentication_error' | 'permissi
6444
6445
  export type stage = 'media' | 'campaign' | 'adset' | 'creative' | 'ad' | 'activation' | 'other';
6445
6446
 
6446
6447
  /**
6447
- * Google Ads 429 only, when Google names the scope. DEVELOPER is the shared developer-token budget; ACCOUNT is your ad account.
6448
+ * Google Ads and YouTube Analytics 429 only, when the scope is known. DEVELOPER is the shared budget (the developer token for Google Ads, the Google Cloud project for YouTube Analytics); ACCOUNT is your ad account (Google Ads only).
6448
6449
  */
6449
6450
  export type quotaScope = 'DEVELOPER' | 'ACCOUNT';
6450
6451
 
@@ -51020,7 +51021,7 @@ export type CreateStandaloneAdData = {
51020
51021
  */
51021
51022
  aiDisclosure?: 'OPT_IN' | 'OPT_OUT';
51022
51023
  /**
51023
- * Google Performance Max validates the complete atomic campaign and asset group with no resource creation or local persistence. Google validation still downloads image URLs and consumes quota. On Meta, validates the complete inline campaign, ad set, creative and ad with execution_options validate_only. Nothing is uploaded or created, and validation bypasses Idempotency-Key storage. Supports a single image or existing video.id (each also with bodies[] / headlines[] Multiple Text Options), all-image placementAssets with per-rule copy and text pools, or existingCreativeId; dynamicCreative, translations, carouselCards, placement videos, new video uploads, creatives[], adSetId and RESERVED buying return 400. Placement validation uses existing Instagram identities only. Existing campaign or creative nodes are marked skipped. When Meta cannot dry-run the nested tree (code 2, or an unknown-error code 1 on an OFFSITE_CONVERSIONS ad set nested in a new campaign, which Meta returns for some website-conversion ad sets that it then creates normally), the campaign and creative are validated on their own and the adSet and ad nodes come back unverified with the reason. Success returns 200 with per-node results; Meta rejection returns an error. ChatGPT (OpenAI) has no platform dry-run: Zernio runs every check it knows (creative lengths, budget, bid strategy, targeting) plus live lookups of the conversion event and target countries, and uploads or creates nothing. OpenAI's own write-time checks (image fetch, currency-specific minimums, ad review) still run only on a real create. Any other platform, or a Google campaignType other than pmax or demand_gen, returns 501 `feature_not_available`.
51024
+ * Google Performance Max validates the complete atomic campaign and asset group with no resource creation or local persistence. Google validation still downloads image URLs and consumes quota. On Meta, validates the complete inline campaign, ad set, creative and ad with execution_options validate_only. Nothing is uploaded or created, and validation bypasses Idempotency-Key storage. Supports a single image or existing video.id (each also with bodies[] / headlines[] Multiple Text Options), all-image placementAssets with per-rule copy and text pools, or existingCreativeId; dynamicCreative, translations, carouselCards, placement videos, new video uploads, creatives[], adSetId and RESERVED buying return 400. Placement validation uses existing Instagram identities only. Existing campaign or creative nodes are marked skipped. When Meta cannot dry-run the nested tree (code 2, or an unknown-error code 1 on an OFFSITE_CONVERSIONS ad set nested in a new campaign, which Meta returns for some website-conversion ad sets that it then creates normally, or a code 100 subcode 2446880 "WhatsApp number required" on an ad that does not message on WhatsApp, which Meta returns intermittently and then creates the ad normally), the campaign and creative are validated on their own and the adSet and ad nodes come back unverified with the reason. If the creative's own dry run also asks for a WhatsApp number, the creative comes back unverified too. Messaging ads still fail on 2446880. Success returns 200 with per-node results; Meta rejection returns an error. ChatGPT (OpenAI) has no platform dry-run: Zernio runs every check it knows (creative lengths, budget, bid strategy, targeting) plus live lookups of the conversion event and target countries, and uploads or creates nothing. OpenAI's own write-time checks (image fetch, currency-specific minimums, ad review) still run only on a real create. Any other platform, or a Google campaignType other than pmax or demand_gen, returns 501 `feature_not_available`.
51024
51025
  */
51025
51026
  validateOnly?: boolean;
51026
51027
  /**