@getlatedev/node 0.2.1277 → 0.2.1279

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -4135,6 +4135,7 @@ export type CommerceOrder = {
     billingAddress?: (CommerceAddress | null);
     shippingAddress?: (CommerceAddress | null);
     buyerNote?: (string) | null;
+    attribution?: CommerceOrderAttribution;
     lineItems?: Array<{
         id?: string;
         /**
@@ -4200,6 +4201,31 @@ export type CommerceOrder = {
     } | null;
 };
 
+/**
+ * Where the order came from. Shopify reads it from the customer journey, WooCommerce from its order attribution (WooCommerce 8.5+ with the feature on, orders placed after it was turned on).
+ */
+export type CommerceOrderAttribution = {
+    /**
+     * False while Shopify is still attributing a new order. No webhook fires when it becomes true, so read the order again later. Always true on WooCommerce.
+     */
+    ready?: boolean;
+    /**
+     * The first session before the order. Shopify only; WooCommerce records the last session alone.
+     */
+    firstVisit?: (CommerceOrderVisit | null);
+    /**
+     * The last session before the order.
+     */
+    lastVisit?: (CommerceOrderVisit | null);
+    /**
+     * Shopify cart and note attributes, or WooCommerce public order meta.
+     */
+    customAttributes?: Array<{
+        key?: string;
+        value?: string;
+    }>;
+};
+
 /**
  * A shipping or fee line.
  */
@@ -4219,6 +4245,39 @@ export type CommerceOrderChargeLine = {
  */
 export type CommerceOrderStatus = 'pending_payment' | 'on_hold' | 'awaiting_fulfillment' | 'partially_fulfilled' | 'in_transit' | 'delivered' | 'completed' | 'cancelled';
 
+/**
+ * A store session that led to the order.
+ */
+export type CommerceOrderVisit = {
+    /**
+     * Null on WooCommerce, which records the session start without a timezone.
+     */
+    occurredAt?: (string) | null;
+    /**
+     * The first page of the session, with its query string.
+     */
+    landingUrl?: (string) | null;
+    referrerUrl?: (string) | null;
+    /**
+     * Where the visit came from, as the platform names it.
+     */
+    source?: (string) | null;
+    /**
+     * Shopify marketing tactic (e.g. SOCIAL, AD, SEARCH) or WooCommerce source type (utm, organic, referral, typein, admin).
+     */
+    sourceType?: (string) | null;
+    /**
+     * Null when the landing URL carried no UTM parameters.
+     */
+    utm?: {
+        source?: (string) | null;
+        medium?: (string) | null;
+        campaign?: (string) | null;
+        term?: (string) | null;
+        content?: (string) | null;
+    } | null;
+};
+
 export type CommercePage = {
     id?: string;
     accountId?: string;
@@ -20071,7 +20130,7 @@ export type CreatePostData = {
          */
         requiresApproval?: boolean;
         /**
-         * TikTok only. Preview whether each `tiktok` entry in `platforms` could publish right now under the TikTok Direct Post daily limits, without creating, scheduling or publishing anything: no post is persisted and no upload slot is claimed, so it can be repeated freely. The request still goes through auth, the payment gate and body validation, then returns HTTP 200 with `{ dryRun: true, canPublish, tiktok: [...] }` instead of 201. Only `tiktok` entries are evaluated; other platforms in the body are ignored, and a body with no `tiktok` entry is rejected with 400 `invalid_field_value` on `platforms`. An entry with `platformSpecificData.tiktokSettings.draft: true` (Creator Inbox upload) is not subject to the limit and always reports `canPublish: true`. Accounts connected through the TikTok for Business app do not go through these limits at all and also always report `canPublish: true`, so on those accounts a dry run confirms the request is well-formed rather than gating it.
+         * TikTok only. Preview whether each `tiktok` entry in `platforms` could publish right now under the TikTok Direct Post daily limits, without creating, scheduling or publishing anything: no post is persisted and no upload slot is claimed, so it can be repeated freely. The request still goes through auth, the payment gate and body validation, and runs the same account access checks as a real create (it can return 400 or 403), then returns HTTP 200 with `{ dryRun: true, canPublish, tiktok: [...] }` instead of 201. Only `tiktok` entries are evaluated; other platforms in the body are ignored, and a body with no `tiktok` entry is rejected with 400 `invalid_field_value` on `platforms`. An entry with `platformSpecificData.tiktokSettings.draft: true` (Creator Inbox upload) is not subject to the limit and always reports `canPublish: true`. Accounts connected through the TikTok for Business app do not go through these limits at all and also always report `canPublish: true`, so on those accounts a dry run confirms the request is well-formed rather than gating it.
          */
         dryRun?: boolean;
         /**