Skip to main content

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.

An Activity represents the actual flow of materials through the system. Activities are a quantity of a Product or Material, with a resulting CO2e value.

Attributes

AttributeTypeDescriptionExample
uuidstringThe unique identifier123e4567-e89b-12d3-a456-426614174000
descriptionstringA description of the activitySteel purchased
directionstringThe direction of the activityin
supplierSupplierThe supplier of the activity{ uuid: "...", name: "Steel Co" }
customerCustomerThe customer of the activity{ uuid: "...", name: "My Company" }
quantitynumberThe amount of the activity100
unitUnitThe unit of measurekg
startDatedateThe date the activity is valid from2021-01-01T00:00:00.000Z
endDatedateThe date the activity is valid until2021-12-31T00:00:00.000Z
timezonestringIANA timezone used to anchor the datesEurope/Oslo
productProductThe product for the activity{ uuid: "...", name: "Steel" }
scopeScopeThe scope of the activity{ uuid: "...", name: "Scope 2: Electricity" }
taxonomyTaxonomyThe category of the activity{ uuid: "...", name: "Steel" }
orgOrgThe 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