APEX Transaction Usage

Production-ready JSON transaction usages demonstrating dataset management, row operations, option models, and selection groups.
Published: 7/10/2026

Live E-Commerce Configuration Setup

This section compiles realistic, multi-step APEX transaction payloads for setting up 3D product configurators.

Rather than using test indices, these scenarios demonstrate how to structure live transactions for a high-end customizable sneaker experience.

Browse the configuration payload guides:

Dataset & Row APEX Payloads#

APEX transaction payloads for creating and editing datasets. Note: CLI Sync (.airpds files) is the preferred pattern.

> [!IMPORTANT] > Deprecation Notice: For creating and managing datasets in Aircada projects, write local .airpds dataset files to the datasets/ workspace directory rather than dispatching APEX transactions. APEX transaction dispatches are reserved for internal runtime mutations or legacy systems.

Creating a Custom Materials Dataset

To establish a new list of selectable materials for the sneaker model, the agent dispatches an atomic ADD transaction for a DATASET domain. This declares a schema mapping custom texture values and variant prices:

json
[
  {
    "operation": "ADD",
    "domain": "DATASET",
    "targetId": "dataset_sneaker_materials",
    "payload": {
      "name": "Premium Sneaker Materials",
      "schema": {
        "materialName": "STRING",
        "additionalCost": "FLOAT",
        "textureQuality": "STRING"
      }
    }
  }
]

Modifying the Dataset Schema

To expand the dataset with a new parameter (e.g. adding a durability score rating), the agent applies an EDIT operation using the dataset's server UUID returned from the creation step:

json
[
  {
    "operation": "EDIT",
    "domain": "DATASET",
    "targetId": "dataset_sneaker_materials_uuid_12345",
    "payload": {
      "name": "Premium Sneaker Materials (Upgraded)",
      "schema": {
        "materialName": "STRING",
        "additionalCost": "FLOAT",
        "textureQuality": "STRING",
        "durabilityScore": "FLOAT"
      }
    }
  }
]

Adding Granular Row Records

Decoupled from parent schemas, records are populated independently. The agent adds row items (e.g. Premium Suede) targeting the dataset UUID:

json
[
  {
    "operation": "ADD",
    "domain": "DATASET_ROW",
    "targetId": "temp_row_suede_blue",
    "payload": {
      "datasetId": "dataset_sneaker_materials_uuid_12345",
      "values": {
        "materialName": "Vibrant Blue Suede",
        "additionalCost": 15.00,
        "textureQuality": "4K_HIGH",
        "durabilityScore": 8.5
      }
    }
  }
]

Modifying a Row Record

To change a variant's pricing or metadata, the agent targets the row's specific ID directly within a flat edit payload:

json
[
  {
    "operation": "EDIT",
    "domain": "DATASET_ROW",
    "targetId": "temp_row_suede_blue_uuid_67890",
    "payload": {
      "datasetId": "dataset_sneaker_materials_uuid_12345",
      "values": {
        "additionalCost": 22.50,
        "durabilityScore": 9.0
      }
    }
  }
]

Option Model & Set APEX Payloads#

APEX transaction payloads for option models. Note: CLI Sync (.airpm files) is the preferred pattern.

> [!IMPORTANT] > Deprecation Notice: For creating and managing product configuration and pricing models in Aircada projects, write local .airpm stripped manifest files to the option-models/ workspace directory rather than dispatching APEX transactions. APEX transaction dispatches are reserved for internal runtime mutations or legacy systems.

Creating an Option Model

To group diverse customizable sets (e.g. shoelaces, side panels, soles) under a unified product model, the agent dispatches an ADD transaction for an OPTION_MODEL:

json
[
  {
    "operation": "ADD",
    "domain": "OPTION_MODEL",
    "targetId": "temp_option_model_sneaker",
    "payload": {
      "name": "Customizable Sneaker Configurator"
    }
  }
]

Modifying the Option Model Name

Modifying option model parameters directly references its UUID:

json
[
  {
    "operation": "EDIT",
    "domain": "OPTION_MODEL",
    "targetId": "option_model_sneaker_uuid_abcde",
    "payload": {
      "name": "Customizable Sneaker Configurator (Premium Edition)"
    }
  }
]

Linking a Dataset via an Option Set

To link the materials dataset to a specific visual section of the 3D model (e.g. Side Panels), the agent creates an OPTION_SET linking the option model UUID with the target materials dataset UUID:

json
[
  {
    "operation": "ADD",
    "domain": "OPTION_SET",
    "targetId": "temp_option_set_panels",
    "payload": {
      "name": "Suede Panels Selection",
      "optionModelId": "option_model_sneaker_uuid_abcde",
      "datasetId": "dataset_sneaker_materials_uuid_12345"
    }
  }
]