> For the complete documentation index, see [llms.txt](https://docs.customer-alliance.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.customer-alliance.com/property-attributes.md).

# Property attributes

Property attributes are the account's own groupings of its properties, such as brand, operating model, region or theme. An administrator defines each attribute and its values under **Settings → Properties**, and gives each property one value per attribute, or none. Custom reports group and filter by them, and scheduled reports can be limited to them. The API exposes them so a BI tool can reproduce the same groups.

Two reads, both with `nodes:read`:

* `GET /property-attributes` lists the attributes and their values, in the order the account set them.
* `GET /nodes` gives each property an `attributes` list with one entry per attribute.

```bash
curl https://app.customer-alliance.com/api/v4/nodes \
  -H "Authorization: Bearer ca_live_your_key_here"
```

```json
{
  "data": [
    {
      "id": "3fa85f64-…", "name": "Hotel Berlin", "parent_id": "9b1c…", "type": "property",
      "attributes": [
        { "attribute_id": "c2e1…", "attribute": "Brand", "value_id": "7d40…", "value": "Dorint" },
        { "attribute_id": "e8a3…", "attribute": "Operating model", "value_id": null, "value": null }
      ]
    }
  ]
}
```

#### How the reports group properties

To match the reports exactly:

* **None is a group.** A property with no value of an attribute is listed with `value_id: null`. The reports show those properties as their own None row, so keep them rather than drop them.
* **A property inside another takes its value.** A property nested in another property (a hotel's spa, say) that holds no value of its own is grouped with the nearest property above it, and `GET /nodes` returns that inherited value.
* **Groups hold no attributes.** Regions and other groups in the hierarchy have an empty `attributes` list. Group properties by their attribute values, not by where they sit in the tree.
* **Join on ids, not names.** An attribute or value can be renamed and keeps its id. A value removed from an attribute no longer appears on any property.

A key reads the values of the properties in its own subtree only. The attribute definitions are the account's, so every key with `nodes:read` lists them all.
