@redotech/redo-api-schema 2.2.447 → 2.2.476

package/lib/openapi.d.ts

@@ -165,18 +165,53 @@ export interface paths {
      * @description Create a custom event to trigger flows with merchant-defined event names and properties.
      *
      * Custom events allow merchants to trigger flows based on events from their own systems.
-     * Events can include custom properties that are accessible in email and SMS templates.
+     * Events can include custom properties that are accessible in email and SMS templates,
+     * and are persisted for segmentation and historical queries.
      *
-     * ## Customer Matching
-     * The API matches customers by email or phone number. At least one must be provided.
+     * ## Identity Resolution
+     * The API resolves customers using the following priority order:
+     * 1. `customer.id` — Redo customer ObjectId (highest priority)
+     * 2. `customer.email` — customer email address
+     * 3. `customer.phoneNumber` — customer phone number
      *
-     * If no matching customer is found, the request will fail with a 404 error.
+     * At least one identifier must be provided. If no matching customer is found, one will
+     * be created automatically. If `customer.id` is provided but not found, the API falls
+     * back to email/phone rather than returning 404.
+     *
+     * ## Datetime Formatting
+     * All datetime values must be formatted as ISO 8601 (RFC 3339) strings, e.g., `2026-04-02T12:00:00Z`.
+     * This applies to `eventTimestamp`, any date-valued properties in `data`, and any date-valued `customFields`.
+     * Strings matching this format are automatically detected and indexed as dates for segmentation.
      *
      * ## Rate Limiting
      * This endpoint is rate-limited to 100 requests per second per store.
      */
     post: operations["Custom event create"];
   };
+  "/stores/{storeId}/events/bulk": {
+    /**
+     * Bulk create custom events
+     * @description Create multiple custom events in a single request. Accepts up to 100 events per request.
+     *
+     * Each event is validated independently. The response includes per-event results, allowing
+     * partial failures — some events may be accepted while others are rejected due to validation
+     * errors.
+     *
+     * ## Identity Resolution
+     * Each event resolves customers independently using the same priority order as the
+     * single-event endpoint:
+     * 1. `customer.id` — Redo customer ObjectId (highest priority)
+     * 2. `customer.email` — customer email address
+     * 3. `customer.phoneNumber` — customer phone number
+     *
+     * At least one identifier must be provided per event. If no matching customer is found,
+     * one will be created automatically.
+     *
+     * ## Rate Limiting
+     * This endpoint is rate-limited to 100 requests per second per store.
+     */
+    post: operations["Bulk create custom events"];
+  };
   "/stores/{storeId}/invoices": {
     /**
      * List Invoices
@@ -184,6 +219,71 @@ export interface paths {
      */
     get: operations["Invoice list"];
   };
+  "/stores/{storeId}/orders": {
+    /**
+     * Create Order
+     * @description Create a new order in the system with line items, customer information, and shipping details.
+     */
+    post: operations["Order create"];
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+      };
+    };
+  };
+  "/stores/{storeId}/orders/{orderId}": {
+    /**
+     * Get Order
+     * @description Retrieve an existing order from the system, including all fulfillments. The orderId parameter can be either the external order ID you provided when creating the order, or the internal Redo order ID returned from the create order response.
+     */
+    get: operations["Order get"];
+    /**
+     * Delete Order
+     * @description Delete an order from the system. The orderId parameter can be either the external order ID you provided when creating the order, or the internal Redo order ID returned from the create order response.
+     */
+    delete: operations["Order delete"];
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+      };
+    };
+  };
+  "/stores/{storeId}/orders/{orderId}/fulfillments": {
+    /**
+     * Create Fulfillment
+     * @description Create a fulfillment for specific line items within an order, including tracking information. The orderId parameter can be either the external order ID you provided when creating the order, or the internal Redo order ID returned from the create order response.
+     */
+    post: operations["Fulfillment create"];
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+      };
+    };
+  };
+  "/stores/{storeId}/orders/{orderId}/fulfillments/{fulfillmentId}/shipment-status": {
+    /**
+     * Update Fulfillment Status
+     * @description Post a shipment status update or trigger an automation event for a fulfillment.
+     *
+     * The status field accepts two types of values:
+     *
+     * **Statuses** (e.g., `in_transit`, `delivered`): Real carrier tracking statuses that update the shipment's current status. When you send these, the fulfillment's current status is updated to reflect the new state. Triggers any configured automations for that status.
+     *
+     * **Events** (e.g., `stalled_in_transit`, `delayed`, `arriving_early`): Special event types that trigger automations without changing the current shipment status. The status field remains unchanged, but you can still update estimated delivery date and add tracking history entries. Use these to trigger event-based automations.
+     *
+     * Both statuses and events can update other fields like estimated delivery date and tracking history.
+     */
+    post: operations["Fulfillment status update"];
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+        fulfillmentId: components["parameters"]["fulfillment-id.param"];
+      };
+    };
+  };
   "/stores/{storeId}/products/bulk-upload": {
     /**
      * Bulk upload products (Beta)
@@ -327,6 +427,14 @@ export interface components {
        */
       state: string;
     };
+    /**
+     * Bulk Custom Event Request
+     * @description Request body for sending multiple custom events in a single request.
+     */
+    "bulk-custom-event-request.schema": {
+      /** @description Array of custom events to create. */
+      events: components["schemas"]["custom-event-request.schema"][];
+    };
     /**
      * Product Family Image
      * @description An image associated with a product family or variant.
@@ -730,49 +838,77 @@ export interface components {
      * @description Custom event to trigger flows with merchant-defined event names and properties.
      */
     "custom-event-request.schema": {
-      /** @description Cart context for product recommendations in triggered emails. If not provided, no cart-aware recommendations will be made. */
-      cart_context?: ({
-        /** @description Items already in the customer's cart. */
-        alreadyInCart: {
-            productId: string;
-            quantity?: number;
-            variantId: string;
-          }[];
-        /** @description The ID of an existing cart to use for recommendations. */
-        existingCartId: string | null;
-        /** @description Product IDs to use as the basis for recommendations. */
-        productIdsForRecommendations: string[];
-      }) | null;
-      /** @description Customer email address (one of email or phone is required). */
-      email?: string;
-      /** @description The name of the custom event (e.g., 'user_registered', 'purchase_completed'). */
-      event_name: string;
-      /**
-       * Format: date-time
-       * @description ISO 8601 timestamp when the event occurred. Defaults to current time if not provided.
+      /** @description Customer identity and profile fields. At least one of `id`, `email`, or `phoneNumber` is required for identity resolution. */
+      customer: {
+        /** @description Merchant-defined customer attributes as key-value pairs. Values can be strings, numbers, or booleans. Date values should be passed as ISO 8601 strings (e.g., "2026-04-02T12:00:00Z") and are automatically detected and indexed as dates. */
+        customFields?: {
+          [key: string]: string | number | boolean;
+        };
+        /**
+         * Format: email
+         * @description Customer email address. Used for identity resolution.
+         */
+        email?: string;
+        /** @description Customer first name. Applied with patch semantics — does not erase existing value if omitted. */
+        firstName?: string;
+        /** @description Redo customer ObjectId. Used for identity resolution. Takes priority over email and phoneNumber when provided. */
+        id?: string;
+        /** @description Customer last name. Applied with patch semantics — does not erase existing value if omitted. */
+        lastName?: string;
+        /** @description Customer location for profile enrichment. All fields are optional. */
+        location?: {
+          /** @description City name. */
+          city?: string;
+          /** @description Country name. */
+          country?: string;
+          /** @description ISO 3166-1 alpha-2 country code (e.g., "US", "GB"). */
+          countryCode?: string;
+          /** @description IANA time zone identifier (e.g., "America/New_York"). */
+          ianaTimeZoneName?: string;
+          /** @description Geographic latitude coordinate. */
+          latitude?: number;
+          /** @description Geographic longitude coordinate. */
+          longitude?: number;
+          /** @description Postal or ZIP code. */
+          postalCode?: string;
+          /** @description State or province name. */
+          state?: string;
+          /** @description State or province abbreviation (e.g., "CA", "NY"). */
+          stateCode?: string;
+          /** @description Primary street address. */
+          street1?: string;
+          /** @description Secondary address line (apartment, suite, etc.). */
+          street2?: string;
+        };
+        /** @description Customer phone number in E.164 format. Used for identity resolution. */
+        phoneNumber?: string;
+      };
+      /**
+       * @description Custom properties for this event (must not exceed 400 properties). The size of the event payload must not exceed 5 MB, and each string cannot be larger than 100 KB. For a full list of data limits on event payloads, see [Limitations](/docs/guides/integrations/custom-events#rate-limits).
+       *
+       * Note any top-level property that is not an object can be used to create segments. The `$extra` property records any non-segmentable values that can be referenced later, e.g., HTML templates are useful on a segment but are not used to create a segment.
        */
-      event_timestamp?: string;
-      /** @description Customer phone number (one of email or phone is required). */
-      phone?: string;
-      /** @description Custom properties for this event. Access in templates using dot notation (e.g., {{ properties.product_name }}). */
-      properties?: {
-        [key: string]: unknown;
+      data?: {
+        /** @description Non-segmentable metadata bucket. Values inside `$extra` are stored on the event but excluded from segmentation indexes. Unlike top-level data properties, values of 0, null, and empty string are NOT stripped inside `$extra`. Use this for large text, debug info, nested objects, arrays, or any data you want to reference in templates but not segment on. */
+        $extra?: {
+          [key: string]: unknown;
+        };
+        [key: string]: (string | number | boolean) | undefined;
       };
-    };
-    /**
-     * Custom Event Response
-     * @description Response after successfully creating a custom event.
-     */
-    "custom-event-response.schema": {
-      /** @description The unique identifier for the created event. */
-      event_id: string;
-      /** @description The name of the custom event that was created. */
-      event_name: string;
+      /** @description The name of the custom event (e.g., 'User Registered', 'Loyalty Reward Earned'). */
+      eventName: string;
       /**
-       * @description Status of the event processing.
-       * @enum {string}
+       * Format: date-time
+       * @description ISO 8601 timestamp when the event occurred. Defaults to current time if not provided.
        */
-      status: "processed";
+      eventTimestamp?: string;
+      /** @description Merchant-controlled deduplication key (1-255 characters). If provided, subsequent events with the same uniqueId for the same store are silently deduplicated. Use this for safe retries and at-least-once delivery patterns. */
+      uniqueId?: string;
+      /** @description Monetary or conversion value associated with the event (e.g., purchase amount). */
+      value?: number;
+      /** @description ISO 4217 currency code for the value field (e.g., "USD", "EUR"). */
+      valueCurrency?: string;
+      [key: string]: unknown;
     };
     /**
      * Customer Location
@@ -1136,6 +1272,253 @@ export interface components {
        */
       total: components["schemas"]["money.schema"];
     };
+    /** @description Request body for creating a fulfillment. */
+    "orders-api-create-fulfillment-request.schema": {
+      /** @description Unique identifier for the fulfillment. If not provided, will be auto-generated. */
+      fulfillmentId?: string;
+      /** @description Initial tracking information for the dummy tracker. Only used when useDummyTracking is true. If not specified, defaults to status "pre_transit". */
+      initialTracking?: {
+        /**
+         * Format: date-time
+         * @description Timestamp of the tracking event in ISO 8601 format.
+         */
+        datetime?: string | null;
+        /**
+         * Format: date-time
+         * @description Estimated delivery date in ISO 8601 format.
+         */
+        estimatedDeliveryDate?: string | null;
+        location?: components["schemas"]["orders-api-tracking-location.schema"];
+        /** @description Tracking event message. */
+        message?: string | null;
+        /**
+         * @description Initial shipment status for the dummy tracker. Only actual statuses are allowed (not automation events).
+         * @enum {string}
+         */
+        status: "pre_transit" | "unknown" | "in_transit" | "out_for_delivery" | "available_for_pickup" | "delivered" | "return_to_sender" | "failure" | "cancelled" | "error";
+      };
+      /** @description List of line items to fulfill. */
+      lineItems: {
+          /** @description Line item ID to fulfill. */
+          id: string;
+          /** @description Quantity to fulfill for this line item. */
+          quantity: number;
+        }[];
+      /** @description Optional tracking information for the shipment. */
+      tracking?: {
+        /** @description Name of the shipping carrier (e.g., FedEx, UPS, USPS). */
+        carrier: string;
+        /** @description Tracking number/code for the shipment. */
+        code: string;
+      } | null;
+      /** @description If true, creates a dummy tracker for testing without calling external tracking APIs. Useful for development and testing the fulfillment status update endpoint. */
+      useDummyTracking?: boolean;
+    };
+    /** @description Request body for creating an order. */
+    "orders-api-create-order-request.schema": {
+      /**
+       * Format: date-time
+       * @description ISO 8601 date string for when the order was created.
+       */
+      createdAt: string;
+      /** @description Currency code from the ISO 4217 standard (e.g., USD, EUR, GBP). */
+      currencyCode?: string | null;
+      customer?: components["schemas"]["orders-api-customer.schema"];
+      /** @description List of line items in the order. */
+      lineItems: components["schemas"]["orders-api-line-item.schema"][];
+      /** @description Unique identifier for the order. */
+      orderId: string;
+      shipping?: components["schemas"]["orders-api-shipping.schema"];
+      /** @description Subtotal price excluding tax and shipping. */
+      subtotalPrice?: number | null;
+      /** @description Optional tags associated with the order. */
+      tags?: string[] | null;
+      /** @description Total order price including tax and shipping. */
+      totalPrice?: number | null;
+      /** @description Total tax amount. */
+      totalTax?: number | null;
+    };
+    /** @description Successful order creation response. */
+    "orders-api-create-order-response.schema": {
+      /** @description Original external order ID provided in the request. */
+      externalOrderId: string;
+      /** @description Internal Redo order ID. */
+      orderId: string;
+    };
+    /** @description Customer information. */
+    "orders-api-customer.schema": {
+      /** @description Customer email address. */
+      email?: string | null;
+      /** @description Customer first name. */
+      firstName?: string | null;
+      /** @description Customer ID from the external system. */
+      id?: string | null;
+      /** @description Customer last name. */
+      lastName?: string | null;
+      /** @description Customer full name. */
+      name?: string | null;
+      /** @description Customer phone number. */
+      phoneNumber?: string | null;
+    };
+    /** @description Successful order deletion response. */
+    "orders-api-delete-order-response.schema": {
+      /** @description External order ID that was deleted. */
+      externalOrderId: string;
+      /** @description Internal Redo order ID. */
+      orderId: string;
+      /** @description Indicates successful deletion. */
+      success: boolean;
+    };
+    /** @description Orders API error response. */
+    "orders-api-error.schema": {
+      /** @description Error message describing what went wrong. */
+      error: string;
+    };
+    /** @description Fulfilled line item details. */
+    "orders-api-fulfillment-line-item.schema": {
+      /** @description Line item ID that was fulfilled. */
+      id: string;
+      /** @description Product ID. */
+      productId: string;
+      /** @description Quantity fulfilled for this line item. */
+      quantity: number;
+      /** @description SKU of the product. */
+      sku?: string | null;
+      /** @description Title/name of the product. */
+      title: string;
+      /** @description Product variant ID. */
+      variantId?: string | null;
+    };
+    /** @description Successful fulfillment operation response. */
+    "orders-api-fulfillment-response.schema": {
+      fulfillment: components["schemas"]["orders-api-fulfillment.schema"];
+      /** @constant */
+      success: true;
+    };
+    /** @description Fulfillment information. */
+    "orders-api-fulfillment.schema": {
+      /**
+       * Format: date-time
+       * @description ISO 8601 date string for when the fulfillment was created.
+       */
+      createdAt: string;
+      /** @description Unique fulfillment ID. */
+      id: string;
+      /** @description List of line items in this fulfillment. */
+      lineItems: components["schemas"]["orders-api-fulfillment-line-item.schema"][];
+      /**
+       * @description Current shipment status.
+       * @enum {string}
+       */
+      status: "pre_transit" | "unknown" | "in_transit" | "out_for_delivery" | "available_for_pickup" | "delivered" | "return_to_sender" | "failure" | "cancelled" | "error";
+      /** @description Shipping carrier name (e.g., FedEx, UPS). */
+      trackingCompany?: string | null;
+      /** @description List of tracking events in chronological order. */
+      trackingHistory: components["schemas"]["orders-api-tracking-event.schema"][];
+      /** @description Tracking number for the shipment. */
+      trackingNumber?: string | null;
+    };
+    /** @description Response for getting an order, including fulfillments. */
+    "orders-api-get-order-response.schema": components["schemas"]["orders-api-create-order-request.schema"] & {
+      /** @description List of fulfillments for this order. */
+      fulfillments: components["schemas"]["orders-api-fulfillment.schema"][];
+    };
+    /** @description Line item in the order. */
+    "orders-api-line-item.schema": {
+      /** @description Unique identifier for the line item. */
+      id: string;
+      /** @description Price per unit of the product. */
+      price?: number | null;
+      /** @description Identifier for the product. */
+      productId: string;
+      /** @description Quantity of the product ordered. */
+      quantity: number;
+      /** @description SKU of the product. */
+      sku?: string | null;
+      /** @description Title/name of the product. */
+      title: string;
+      /** @description Identifier for the product variant. */
+      variantId?: string | null;
+    };
+    /** @description Shipping address. */
+    "orders-api-shipping-address.schema": {
+      /** @description Primary address line. */
+      address1?: string | null;
+      /** @description Secondary address line. */
+      address2?: string | null;
+      /** @description City. */
+      city?: string | null;
+      /** @description Country. */
+      country?: string | null;
+      /** @description Postal or zip code. */
+      postalCode?: string | null;
+      /** @description State or province. */
+      province?: string | null;
+    };
+    /** @description Shipping information. */
+    "orders-api-shipping.schema": {
+      address?: components["schemas"]["orders-api-shipping-address.schema"];
+      /** @description Shipping cost. */
+      cost?: number | null;
+      /** @description Shipping method name. */
+      method?: string | null;
+    };
+    /** @description Tracking event details. */
+    "orders-api-tracking-event.schema": {
+      /**
+       * Format: date-time
+       * @description ISO 8601 timestamp of the tracking event.
+       */
+      datetime: string;
+      location?: components["schemas"]["orders-api-tracking-location.schema"];
+      /** @description Tracking event message. */
+      message: string;
+      /** @description Status at this tracking event. */
+      status: string;
+    };
+    /** @description Location information for a tracking event. */
+    "orders-api-tracking-location.schema": {
+      city?: string | null;
+      country?: string | null;
+      postalCode?: string | null;
+      state?: string | null;
+    };
+    /**
+     * @description Request body for updating a fulfillment's tracking status.
+     *
+     * The status field accepts two types of values:
+     * - **Statuses** (e.g., `in_transit`, `delivered`): Update the shipment's current status and trigger configured automations.
+     * - **Events** (e.g., `stalled_in_transit`, `delayed`, `arriving_early`): Trigger automations without changing the current shipment status.
+     *
+     * Both can update other fields like estimated delivery date and tracking history.
+     */
+    "orders-api-update-fulfillment-status-request.schema": {
+      /**
+       * Format: date-time
+       * @description Timestamp of the tracking event in ISO 8601 format.
+       */
+      datetime?: string | null;
+      /**
+       * Format: date-time
+       * @description Estimated delivery date in ISO 8601 format.
+       */
+      estimatedDeliveryDate?: string | null;
+      location?: components["schemas"]["orders-api-tracking-location.schema"];
+      /** @description Tracking event message (e.g., "Departed shipping partner facility"). */
+      message?: string | null;
+      /**
+       * @description Shipment status or automation event.
+       *
+       * Statuses update the current shipment status and trigger automations:
+       * `pre_transit`, `in_transit`, `out_for_delivery`, `available_for_pickup`, `delivered`, `return_to_sender`, `failure`, `cancelled`, `error`.
+       *
+       * Events trigger automations without changing the current status:
+       * `stalled_in_transit`, `delayed`, `arriving_early`.
+       *
+       * @enum {string}
+       */
+      status: "pre_transit" | "in_transit" | "out_for_delivery" | "available_for_pickup" | "delivered" | "return_to_sender" | "failure" | "cancelled" | "error" | "stalled_in_transit" | "delayed" | "arriving_early";
+    };
     /**
      * Person name
      * @description Person name.
@@ -1955,10 +2338,14 @@ export interface components {
   };
   responses: never;
   parameters: {
+    /** @description Unique fulfillment identifier. */
+    "fulfillment-id.param": string;
     /** @description Optional idempotency key for safely retrying create requests. */
     "idempotency-key.param"?: string;
     /** @description Invoice ID */
     "invoice-id.param": string;
+    /** @description Order ID. Can be either the external order ID provided when creating the order, or the internal Redo order ID. */
+    "order-id.param": string;
     /**
      * @description Page marker, from X-Page-Next header
      * @example 64df700931a04885276c3364
@@ -2602,12 +2989,23 @@ export interface operations {
    * @description Create a custom event to trigger flows with merchant-defined event names and properties.
    *
    * Custom events allow merchants to trigger flows based on events from their own systems.
-   * Events can include custom properties that are accessible in email and SMS templates.
+   * Events can include custom properties that are accessible in email and SMS templates,
+   * and are persisted for segmentation and historical queries.
+   *
+   * ## Identity Resolution
+   * The API resolves customers using the following priority order:
+   * 1. `customer.id` — Redo customer ObjectId (highest priority)
+   * 2. `customer.email` — customer email address
+   * 3. `customer.phoneNumber` — customer phone number
    *
-   * ## Customer Matching
-   * The API matches customers by email or phone number. At least one must be provided.
+   * At least one identifier must be provided. If no matching customer is found, one will
+   * be created automatically. If `customer.id` is provided but not found, the API falls
+   * back to email/phone rather than returning 404.
    *
-   * If no matching customer is found, the request will fail with a 404 error.
+   * ## Datetime Formatting
+   * All datetime values must be formatted as ISO 8601 (RFC 3339) strings, e.g., `2026-04-02T12:00:00Z`.
+   * This applies to `eventTimestamp`, any date-valued properties in `data`, and any date-valued `customFields`.
+   * Strings matching this format are automatically detected and indexed as dates for segmentation.
    *
    * ## Rate Limiting
    * This endpoint is rate-limited to 100 requests per second per store.
@@ -2624,19 +3022,80 @@ export interface operations {
       };
     };
     responses: {
-      /** @description Event created successfully */
-      200: {
+      /** @description Event accepted and queued for processing. No response body is returned. */
+      202: {
+        content: never;
+      };
+      /** @description Invalid request body or missing required customer identifier */
+      400: {
         content: {
-          "application/json": components["schemas"]["custom-event-response.schema"];
+          "application/json": components["schemas"]["error.schema"];
         };
       };
-      /** @description Invalid request body or missing required customer identifier */
+      /** @description Store not found */
+      404: {
+        content: {
+          "application/json": components["schemas"]["error.schema"];
+        };
+      };
+      /** @description Rate limit exceeded */
+      429: {
+        content: {
+          "application/json": components["schemas"]["error.schema"];
+        };
+      };
+      /** @description Error */
+      default: {
+        content: {
+          "application/problem+json": components["schemas"]["error.schema"];
+        };
+      };
+    };
+  };
+  /**
+   * Bulk create custom events
+   * @description Create multiple custom events in a single request. Accepts up to 100 events per request.
+   *
+   * Each event is validated independently. The response includes per-event results, allowing
+   * partial failures — some events may be accepted while others are rejected due to validation
+   * errors.
+   *
+   * ## Identity Resolution
+   * Each event resolves customers independently using the same priority order as the
+   * single-event endpoint:
+   * 1. `customer.id` — Redo customer ObjectId (highest priority)
+   * 2. `customer.email` — customer email address
+   * 3. `customer.phoneNumber` — customer phone number
+   *
+   * At least one identifier must be provided per event. If no matching customer is found,
+   * one will be created automatically.
+   *
+   * ## Rate Limiting
+   * This endpoint is rate-limited to 100 requests per second per store.
+   */
+  "Bulk create custom events": {
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+      };
+    };
+    requestBody: {
+      content: {
+        "application/json": components["schemas"]["bulk-custom-event-request.schema"];
+      };
+    };
+    responses: {
+      /** @description Bulk request accepted and queued for processing. No response body is returned. */
+      202: {
+        content: never;
+      };
+      /** @description Invalid request body (e.g., events array missing or exceeds 100 items) */
       400: {
         content: {
           "application/json": components["schemas"]["error.schema"];
         };
       };
-      /** @description Customer not found with provided identifier */
+      /** @description Store not found */
       404: {
         content: {
           "application/json": components["schemas"]["error.schema"];
@@ -2683,6 +3142,237 @@ export interface operations {
       };
     };
   };
+  /**
+   * Create Order
+   * @description Create a new order in the system with line items, customer information, and shipping details.
+   */
+  "Order create": {
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+      };
+    };
+    requestBody: {
+      content: {
+        "application/json": components["schemas"]["orders-api-create-order-request.schema"];
+      };
+    };
+    responses: {
+      /** @description Success */
+      200: {
+        content: {
+          "application/json": components["schemas"]["orders-api-create-order-response.schema"];
+        };
+      };
+      /** @description Bad Request (validation error) */
+      400: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Unauthorized (invalid or missing API token) */
+      401: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Conflict (duplicate order ID) */
+      409: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Error */
+      default: {
+        content: {
+          "application/problem+json": components["schemas"]["error.schema"];
+        };
+      };
+    };
+  };
+  /**
+   * Get Order
+   * @description Retrieve an existing order from the system, including all fulfillments. The orderId parameter can be either the external order ID you provided when creating the order, or the internal Redo order ID returned from the create order response.
+   */
+  "Order get": {
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+      };
+    };
+    responses: {
+      /** @description Success */
+      200: {
+        content: {
+          "application/json": components["schemas"]["orders-api-get-order-response.schema"];
+        };
+      };
+      /** @description Unauthorized (invalid or missing API token) */
+      401: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Order not found */
+      404: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Error */
+      default: {
+        content: {
+          "application/problem+json": components["schemas"]["error.schema"];
+        };
+      };
+    };
+  };
+  /**
+   * Delete Order
+   * @description Delete an order from the system. The orderId parameter can be either the external order ID you provided when creating the order, or the internal Redo order ID returned from the create order response.
+   */
+  "Order delete": {
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+      };
+    };
+    responses: {
+      /** @description Success */
+      200: {
+        content: {
+          "application/json": components["schemas"]["orders-api-delete-order-response.schema"];
+        };
+      };
+      /** @description Unauthorized (invalid or missing API token) */
+      401: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Order not found */
+      404: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Error */
+      default: {
+        content: {
+          "application/problem+json": components["schemas"]["error.schema"];
+        };
+      };
+    };
+  };
+  /**
+   * Create Fulfillment
+   * @description Create a fulfillment for specific line items within an order, including tracking information. The orderId parameter can be either the external order ID you provided when creating the order, or the internal Redo order ID returned from the create order response.
+   */
+  "Fulfillment create": {
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+      };
+    };
+    requestBody: {
+      content: {
+        "application/json": components["schemas"]["orders-api-create-fulfillment-request.schema"];
+      };
+    };
+    responses: {
+      /** @description Success */
+      200: {
+        content: {
+          "application/json": components["schemas"]["orders-api-fulfillment-response.schema"];
+        };
+      };
+      /** @description Bad Request (validation error) */
+      400: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Unauthorized (invalid or missing API token) */
+      401: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Order not found */
+      404: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Error */
+      default: {
+        content: {
+          "application/problem+json": components["schemas"]["error.schema"];
+        };
+      };
+    };
+  };
+  /**
+   * Update Fulfillment Status
+   * @description Post a shipment status update or trigger an automation event for a fulfillment.
+   *
+   * The status field accepts two types of values:
+   *
+   * **Statuses** (e.g., `in_transit`, `delivered`): Real carrier tracking statuses that update the shipment's current status. When you send these, the fulfillment's current status is updated to reflect the new state. Triggers any configured automations for that status.
+   *
+   * **Events** (e.g., `stalled_in_transit`, `delayed`, `arriving_early`): Special event types that trigger automations without changing the current shipment status. The status field remains unchanged, but you can still update estimated delivery date and add tracking history entries. Use these to trigger event-based automations.
+   *
+   * Both statuses and events can update other fields like estimated delivery date and tracking history.
+   */
+  "Fulfillment status update": {
+    parameters: {
+      path: {
+        storeId: components["parameters"]["store-id.param"];
+        orderId: components["parameters"]["order-id.param"];
+        fulfillmentId: components["parameters"]["fulfillment-id.param"];
+      };
+    };
+    requestBody: {
+      content: {
+        "application/json": components["schemas"]["orders-api-update-fulfillment-status-request.schema"];
+      };
+    };
+    responses: {
+      /** @description Success */
+      200: {
+        content: {
+          "application/json": components["schemas"]["orders-api-fulfillment-response.schema"];
+        };
+      };
+      /** @description Bad Request (validation error) */
+      400: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Unauthorized (invalid or missing API token) */
+      401: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Fulfillment not found */
+      404: {
+        content: {
+          "application/json": components["schemas"]["orders-api-error.schema"];
+        };
+      };
+      /** @description Error */
+      default: {
+        content: {
+          "application/problem+json": components["schemas"]["error.schema"];
+        };
+      };
+    };
+  };
   /**
    * Bulk upload products (Beta)
    * @description Bulk create or update product families and their variants.