v2 One API key for every Edgecom product

Build on your energy data

Pull site telemetry, Ontario and Alberta market data and forecasts, and your demand response results straight into your own systems.

Get an API key Browse the APIs
8APIs
330+Endpoints
2 minTo your first call
~ / edgecom
# Hourly Ontario demand, from pTrack
curl "https://api.edgecom.ai/ptrack/v2/hourly\
  ?start=2026-10-01T00:00:00&end=2026-10-02T00:00:00" \
  -H "Authorization: Bearer $EDGECOM_API_KEY"

{
  "result": [{
    "date": "2026-10-01",
    "values": [
      { "time": "00:00", "value": 13980 },
      { "time": "01:00", "value": 13744 },
      …
    ]
  }]
}

Step 1

Create an API key

An API key lets your scripts and systems call Edgecom as you. You create it yourself in the Edgecom portal in about a minute, and you choose exactly what it can do.

  1. Open your API keys

    Sign in to portal.edgecom.ai and go to SettingsAPI KeysPersonal Keys.

  2. Click New API key

    Give the key a name you'll recognize later, such as Billing export, and choose when it expires: 30, 90, 180 or 365 days.

  3. Choose its access

    Under Access, pick what the key can do, for example pTrack · Dashboard, read. Only what your own role allows is listed. Also pick List locations so the key can look up your location IDs.

  4. Copy the key now

    Click Create key. The key is shown only once, so copy it into a password manager or secret store, tick I've stored this key somewhere safe, and click Done.

The key can never do more than you can. If your role in the portal changes, or you leave your company's account, the key changes with you.

Don't see Personal Keys, or can't create one? Your company's administrators may have limited API keys to certain roles. Ask them, or email support@edgecom.ai.

Step 2

Authenticate your requests

Send the key as a bearer token in the Authorization header of every request.

HTTP header
Authorization: Bearer authx_production_usr_v1_<id>.<secret>

Keep it secret

Load the key from an environment variable or secret manager. Never put it in source code, URLs or logs.

Same key everywhere

One key works across dataTrack, pTrack and demand response, for whatever access you gave it.

Moving from v1?

The v2 APIs ignore the old X-API-Key header. Create a new key and send it as a bearer token.

Step 3

Find your locations

Most routes take a location or organization ID. List your locations once and keep their IDs.

Shell
export EDGECOM_API_KEY="authx_production_usr_v1_…"

curl https://api.edgecom.ai/x/organizations/me/locations \
  -H "Authorization: Bearer $EDGECOM_API_KEY"

Each item in result[] has the location's id, name, organization_id, address, market and zone. Use that id wherever a route asks for a location {id}, and organization_id where it asks for an organization.

This call needs the key to include List locations. On dataTrack you can also call GET https://api.edgecom.ai/core/v2/location, which lists every dataTrack site you can see, across all your organizations.

Reference

APIs

Every reference is interactive. Paste your key under Authentication and send real requests from the browser.

Site data

dataTrack

Your sites, assets and sensor series, live and historical, plus alarms, production analytics, planning and reports.

/core/v2

Market data and forecasts

pTrack Ontario

IESO demand, prices, peaks and weather, with pTrack peak predictions and peak-call history.

/ptrack/v2 · /pivot/v2/ontario
pTrack Alberta

AESO internal load, pool price, supply and demand, with pTrack predictions and your alert thresholds.

alberta.edgecom.ai · /pivot/v2/alberta

Demand response

Ontario

Events, season standing, revenue, settlement, LMP, curtailment plans and reports.

/ondr/v2
Alberta

Seasons, events, participation, curtailment plans, baseline requests, demand and revenue.

/dr-alberta/v2
Nova Scotia

Seasons, events, participation, curtailment plans, baseline requests, demand and revenue.

/nsdr/v2
Prince Edward Island

Seasons, events, participation, curtailment plans, baseline requests, demand and revenue.

/dr-pei/v2
Québec

Seasons, events, participation, curtailment plans, baseline requests, demand and revenue.

/dr-quebec/v2

Keys over time

Rotate and revoke keys

Keys expire. Rotate yours before it does, and revoke it the moment it might have leaked.

Expiry

A key lasts up to 365 days; your company may set a shorter limit. The portal warns you 14 days before.

Rotate

Choose Rotate on the key. You get a new key with the same access, and the old one keeps working for up to 24 hours while you switch.

Revoke

Choose Revoke to stop a key immediately. A revoked key can't be restored.

Troubleshooting

Errors

All the APIs use the same status codes, and error bodies carry a readable message.

StatusMeaningWhat to check
400The request is malformed.Date formats, IDs and required parameters, as documented in each reference.
401The key is missing, malformed, expired or revoked.The Authorization: Bearer header, and the key's status in the portal.
403The key works, but its access doesn't cover this product, location or action.The key's Access in the portal, and your own role. If the message says your email isn't verified, verify it first.
404The location or record doesn't exist, or your key can't see it.The ID. Use the IDs from your location list.
503An Edgecom service is briefly unavailable.Retry with exponential backoff.

Contacting support about a 403? Include the X-AuthX-Decision-ID response header if one was returned. It points to the exact access decision.

Need a hand?

Questions about your key, your access or an API? We're happy to help. Never send the key itself; its name is enough.

Email support@edgecom.ai