> ## Documentation Index
> Fetch the complete documentation index at: https://docs.variable.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Activity

An `Activity` represents the actual flow of materials through the system. Activities are a quantity of a `Product` or `Material`, with a resulting CO<sub>2</sub>e value.

<Info icon="code">
  [Activity API documentation <Icon icon="square-arrow-up-right" iconType="light" />](/api-reference/v1/activity)
</Info>

### Attributes

| Attribute   | Type     | Description                               | Example                                         |
| :---------- | :------- | :---------------------------------------- | :---------------------------------------------- |
| uuid        | string   | The unique identifier                     | 123e4567-e89b-12d3-a456-426614174000            |
| description | string   | A description of the activity             | Steel purchased                                 |
| direction   | string   | The direction of the activity             | in                                              |
| supplier    | Supplier | The supplier of the activity              | `{ uuid: "...", name: "Steel Co" }`             |
| customer    | Customer | The customer of the activity              | `{ uuid: "...", name: "My Company" }`           |
| quantity    | number   | The amount of the activity                | 100                                             |
| unit        | Unit     | The unit of measure                       | kg                                              |
| startDate   | date     | The date the activity is valid from       | 2021-01-01T00:00:00.000Z                        |
| endDate     | date     | The date the activity is valid until      | 2021-12-31T00:00:00.000Z                        |
| timezone    | string   | IANA timezone used to anchor the dates    | Europe/Oslo                                     |
| product     | Product  | The product for the activity              | `{ uuid: "...", name: "Steel" }`                |
| scope       | Scope    | The scope of the activity                 | `{ uuid: "...", name: "Scope 2: Electricity" }` |
| taxonomy    | Taxonomy | The category of the activity              | `{ uuid: "...", name: "Steel" }`                |
| org         | Org      | The org unit responsible for the activity | `{ uuid: "...", name: "Procurement" }`          |

### Date anchoring

Under-specified date inputs (`"2026"`, `"2026-03"`, `"2026-03-15"`) are anchored
to your company's IANA timezone, set on the `Company` resource and defaulting to
`Europe/Oslo`. `"2026-03"` from a company in `America/Los_Angeles` resolves to
the start of March 2026 in LA, not UTC. Each `Activity` records the timezone
that was used on `Activity.timezone` for provenance; period filters (YTD, MTD,
specific years) bucket from your company's timezone.

To avoid start/end snapping, supply a full ISO-8601 timestamp
(`2026-03-01T00:00:00`). The wall-clock time is interpreted in the company's
timezone — an offset in the input (`…-08:00`, `…Z`) does not override it.

### Diagram

```mermaid theme={"system"}
erDiagram
    Activity ||--|| Product : "for"
    Activity ||--|| Taxonomy : "in"
    Activity ||--|| Org : "in"
    Activity ||--|| Scope : "in"
    Activity ||--|| Supplier : "from"
    Activity ||--|| Customer : "to"

    Activity {
        quantity number
        unit Unit
        CO2e decimal
        startDate date
        endDate date
    }
```