Overview
The Scope3 Emissions API provides programmatic access to organisational carbon footprint and sustainability data, specifically focusing on Scope 3 emissions, which represent indirect emissions across a company’s value chain (e.g., purchased goods, transportation, waste, and use of sold products). The connector enables businesses to integrate environmental impact data into dashboards, reporting systems, and sustainability analytics workflows.
Data handled by the integration:
Organisational & Account Data
Company accounts and IDs
Business units, departments, or subsidiaries
Reporting period definitions (monthly, quarterly, yearly)
Emission Sources
Purchased goods and services
Capital goods
Fuel- and energy-related activities
Upstream transportation and distribution
Waste generated in operations
Business travel
Employee commuting
Use of sold products
End-of-life treatment of sold products
Performance & Measurement Metrics
CO₂e emissions (kg, tonnes)
Emission intensity per activity or product category
Scope 1, Scope 2, and Scope 3 breakdowns
Activity data supporting emissions calculations (e.g., fuel consumed, distance travelled, energy used)
GHG Protocol alignment metadata
Metadata & Reference Tables
Emission factors and calculation methodologies
Product or service categories
Geography / country-specific factors
Business unit and organisational hierarchy
Granularity:
The Scope3 integration supports reporting at multiple levels:
Organisational-level totals
Business unit-level breakdowns
Emission source-level detail (e.g., purchased goods, transportation)
Time-based granularity:
Daily, monthly, quarterly, or yearly depending on activity data availability
Purpose:
Track and analyse Scope 3 emissions across the value chain
Support ESG and sustainability reporting requirements
Benchmark environmental performance over time
Identify key emission sources for reduction initiatives
Integrate carbon footprint data into broader business intelligence dashboards
Aid compliance with regulations and voluntary reporting frameworks
Refresh Cadence:
Data is refreshed daily.
Update Modes:
Append (for data table), Refresh (for metadata)
Jobs Configuration
Job: Scope3 Emissions Data Import
Field | Value |
Feed |
|
Status |
|
Label |
|
Lookback | 1 day |
First Run Hour | 4 AM |
Poll Frequency | 24 hours |
Lookback Window | 0 |
Target
Priority | Table | Description | Update Mode | Create Target |
1 |
| Scope3 Emissions Import | refresh | true |
Connection Settings
Key | Description | Type | Required | Notes |
| Scope3 Access Client ID | text | Yes | Used for API authentication |
| Scope3 Access Client Secret | text | Yes | Confidential API credential |
Host: (Empty — assumed predefined in connector)
Token / Secret / Password / Username: (Not used in this integration)
Connection Description:
Scope 3 Emissions Connection
Dimensions & Metrics
None declared at this stage. The structure is handled entirely via the refresh operation of scope3_data_emissions.
Datasource Joins
None required for this job. The emissions data appears to be self-contained and does not join to any metadata or reference tables in the starting configuration.