Building ESG API - Carbon, Energy and Certifications

Pull a real estate portfolio's ESG reporting data out of the platform it lives in and into your own systems.

What it collects

• Portfolios and funds an account can see, which is where the identifiers everything else needs come from.
• Buildings with name, full address, primary property type, gross floor area in square feet, year built, ownership percentage, single tenant flag, purchase and disposal dates, and whether the asset is still active.
• Meters for energy, water and waste, and their readings period by period with the unit each consumption figure is measured in.
• Certifications and ratings: the green building certifications held across a portfolio, the certification types relevant to it, and the energy and performance ratings on individual buildings and spaces.
• Modelled asset level data: carbon estimates, energy estimates, certification lookups and ordinance lookups, plus the building performance ordinance catalogue behind them.
• Securities level reports for listed real estate, and the partner views for portfolios and monthly utility data.

FAQ

What building ESG data can I export?

Portfolios and funds, buildings with floor area and property type, energy, water and waste meters with their readings, green building certifications and ratings, and modelled carbon and energy estimates per building. The building performance ordinance catalogue and per-building ordinance lookups come through the same run.

How do I get a portfolio ID?

Run the portfolios dataset first. It needs no identifier and returns every portfolio the account can see, each with the UUID that the buildings, meters, certifications and ratings datasets take. A fund ID works anywhere a portfolio ID does.

Can this actor change data in my ESG account?

No. Every route it calls is a GET. This provider's write endpoints add buildings, meters and readings to a customer's own regulatory reporting, and a data collector has no business touching those, so the actor is read only by construction rather than by configuration. A scheduled run cannot create, change or delete anything.

What authentication does this API use?

A key and secret pair, issued together by the provider to your organisation, exchanged at the start of the run for a bearer token that lasts twenty four hours. One exchange serves a whole run. Both halves of the pair are required, and both are stored encrypted and never written into the dataset.

Why do I only get one page of results?

You should not, and the reason this is worth mentioning is that this API spells its page size two different ways. The portfolio endpoints take size and the asset level and partner endpoints take pageSize, and sending the wrong one is not an error: the provider ignores it and returns its default page. The actor sends whichever spelling the dataset you chose accepts, so a run collects everything rather than looking like it did.

Does it drop buildings that were sold?

No. Inactive buildings are collected and flagged with an active indicator you can filter on. A portfolio total that quietly lost its disposed assets would be a different number from the one the platform reports, so the decision to exclude them is left to you.

Can I collect only what changed since last week?

Yes, on the portfolio datasets. The filter input passes the provider's own expression straight through, so updatedAt=ge=2026-09-01 returns only records changed on or after that date. On datasets that do not accept a filter, the actor says so in the log rather than sending one the provider would silently ignore.

What does it cost?

Pay per result. Modelled estimates cost the most, buildings and meters less, readings and monthly utility rows least because they are high volume by nature, and portfolios, funds and catalogues are priced near zero so you can find your identifiers before committing to a real run. Platform usage is included.

Example output

{
  "recordType": "building",
  "requested": "buildings portfolioId=134b372e-34e7-49bf-a45a-acf452bf4fd2",
  "found": true,
  "recordId": "702e7fdf-1b3a-451e-9dfe-3b408c6fff80",
  "resourceType": "buildings",
  "portfolioId": "134b372e-34e7-49bf-a45a-acf452bf4fd2",
  "name": "Warehouse Distribution Center",
  "addressLine1": "123 Warehouse Dr",
  "addressCity": "San Diego",
  "addressState": "CA",
  "addressZip": "92120",
  "addressCountry": "United States",
  "primaryPropertyType": "Distribution Center",
  "floorAreaSqFt": 1111,
  "yearBuilt": 1969,
  "percentOwned": 100.0,
  "isSingleTenant": true,
  "isActive": true,
  "updatedAt": "2026-05-18 00:00:00"
}

Keyword map

building ESG data API, carbon emissions data API, real estate decarbonisation data, energy and water meter readings API, utility data API, green building certification data, LEED BREEAM certification lookup, ENERGY STAR rating data, building performance ordinance data, CRREM pathway data, GRESB reporting data export, portfolio ESG reporting API, Scope 1 2 3 building emissions, asset level carbon estimates.

Notes

Bring your own key. Read only by construction: every route is a GET. Rate limiting, retries, token exchange and per-product pagination are handled for you, and missing or refused credentials end the run cleanly with an explanation rather than failing it. Floor areas are square feet and readings carry their own unit, as the provider publishes them.