@redotech/redo-api-schema 2.2.432 → 2.2.435

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/lib/openapi.d.ts CHANGED
@@ -810,10 +810,10 @@ export interface components {
810
810
  /**
811
811
  * Created at
812
812
  * Format: date-time
813
- * @description Timestamp when the customer was created.
813
+ * @description Timestamp when the customer was created. May be null for older customers created before this field was tracked.
814
814
  */
815
- createdAt: string;
816
- /** @description Custom field values as key-value pairs, where keys are field names and values can be strings, numbers, or booleans. */
815
+ createdAt?: string | null;
816
+ /** @description Custom field values as key-value pairs, where keys are field names and values can be strings, numbers, or booleans. DATE custom field values are returned as ISO 8601 datetime strings (e.g., "2026-01-15T12:00:00.000Z"), not Date objects. */
817
817
  customFields?: {
818
818
  [key: string]: string | number | boolean;
819
819
  };
@@ -834,9 +834,9 @@ export interface components {
834
834
  /**
835
835
  * Updated at
836
836
  * Format: date-time
837
- * @description Timestamp when the customer was last updated.
837
+ * @description Timestamp when the customer was last updated. May be null for older customers created before this field was tracked.
838
838
  */
839
- updatedAt: string;
839
+ updatedAt?: string | null;
840
840
  };
841
841
  /** @description Email subscription updates */
842
842
  "customer-subscription-email.schema": {
@@ -884,12 +884,19 @@ export interface components {
884
884
  */
885
885
  "customer-upsert-request.schema": {
886
886
  /**
887
- * @description Custom field values as key-value pairs. Keys are field names and values can be strings, numbers, or booleans. New fields are created automatically if they don't exist yet.
887
+ * @description Custom field values as key-value pairs. Keys are field names and values can be strings, numbers, or booleans. The field type is determined automatically based on the value:
888
+ * - String values → STRING custom field
889
+ * - Number values → NUMBER custom field
890
+ * - Boolean values → BOOLEAN custom field
891
+ * - ISO 8601 datetime strings (e.g., "2026-02-24T12:15:00.000Z") → DATE custom field (auto-detected)
892
+ *
893
+ * If a field name does not already have a declaration, one is created automatically. For STRING fields, unique values are tracked as options (used for segment filtering dropdowns). NUMBER, BOOLEAN, and DATE fields do not track options.
888
894
  * @example {
889
895
  * "subscription_source": "web",
890
896
  * "status": "Active",
891
897
  * "loyalty_points": 1250,
892
- * "vip_member": true
898
+ * "vip_member": true,
899
+ * "signup_date": "2026-02-24T12:15:00.000Z"
893
900
  * }
894
901
  */
895
902
  customFields?: {
package/lib/openapi.yaml CHANGED
@@ -1943,7 +1943,7 @@ components:
1943
1943
  location:
1944
1944
  $ref: '#/components/schemas/customer-location.schema'
1945
1945
  customFields:
1946
- description: Custom field values as key-value pairs, where keys are field names and values can be strings, numbers, or booleans.
1946
+ description: Custom field values as key-value pairs, where keys are field names and values can be strings, numbers, or booleans. DATE custom field values are returned as ISO 8601 datetime strings (e.g., "2026-01-15T12:00:00.000Z"), not Date objects.
1947
1947
  type: object
1948
1948
  additionalProperties:
1949
1949
  oneOf:
@@ -1955,25 +1955,28 @@ components:
1955
1955
  status: Active
1956
1956
  loyalty_points: 1250
1957
1957
  vip_member: true
1958
+ signup_date: '2026-02-24T12:15:00.000Z'
1958
1959
  createdAt:
1959
- description: Timestamp when the customer was created.
1960
+ description: Timestamp when the customer was created. May be null for older customers created before this field was tracked.
1960
1961
  format: date-time
1961
1962
  title: Created at
1962
1963
  examples:
1963
1964
  - '2026-02-20T18:30:00.000Z'
1964
- type: string
1965
+ type:
1966
+ - string
1967
+ - 'null'
1965
1968
  updatedAt:
1966
- description: Timestamp when the customer was last updated.
1969
+ description: Timestamp when the customer was last updated. May be null for older customers created before this field was tracked.
1967
1970
  format: date-time
1968
1971
  title: Updated at
1969
1972
  examples:
1970
1973
  - '2026-02-24T12:15:00.000Z'
1971
- type: string
1974
+ type:
1975
+ - string
1976
+ - 'null'
1972
1977
  required:
1973
1978
  - id
1974
1979
  - email
1975
- - createdAt
1976
- - updatedAt
1977
1980
  title: Customer
1978
1981
  type: object
1979
1982
  customer-upsert-request.schema:
@@ -1998,7 +2001,14 @@ components:
1998
2001
  location:
1999
2002
  $ref: '#/components/schemas/customer-location.schema'
2000
2003
  customFields:
2001
- description: Custom field values as key-value pairs. Keys are field names and values can be strings, numbers, or booleans. New fields are created automatically if they don't exist yet.
2004
+ description: |-
2005
+ Custom field values as key-value pairs. Keys are field names and values can be strings, numbers, or booleans. The field type is determined automatically based on the value:
2006
+ - String values → STRING custom field
2007
+ - Number values → NUMBER custom field
2008
+ - Boolean values → BOOLEAN custom field
2009
+ - ISO 8601 datetime strings (e.g., "2026-02-24T12:15:00.000Z") → DATE custom field (auto-detected)
2010
+
2011
+ If a field name does not already have a declaration, one is created automatically. For STRING fields, unique values are tracked as options (used for segment filtering dropdowns). NUMBER, BOOLEAN, and DATE fields do not track options.
2002
2012
  type: object
2003
2013
  additionalProperties:
2004
2014
  oneOf:
@@ -2010,6 +2020,7 @@ components:
2010
2020
  status: Active
2011
2021
  loyalty_points: 1250
2012
2022
  vip_member: true
2023
+ signup_date: '2026-02-24T12:15:00.000Z'
2013
2024
  required:
2014
2025
  - email
2015
2026
  title: Customer Upsert Request
package/package.json CHANGED
@@ -31,5 +31,5 @@
31
31
  ]
32
32
  }
33
33
  },
34
- "version": "2.2.432"
34
+ "version": "2.2.435"
35
35
  }