API Update - May 2026

Overview of changes

We have recently updated the core trading system to support multiple parallel markets.

Previously, the platform represented only a single market: the Australian Electricity Market. That could be simply visualised like this:

Open

A simple mud-map of the original ‘single market’ system object hierarchy.

Now, after this update, we can support multiple discrete OTC markets in the same platform, with isolated products and credit matrices, while preserving the original functionality and permissions.

Open

A simple mud-map of the new ‘multi-market’ system object hierarchy.

This update has forced us to reconsider the naming conventions used in the original design. Previously, ‘Market’ represented the Australian NEM regional reference nodes, which are identified by the codes N, Q, S, T & V. With this change, ‘Market’ now represents any discrete OTC market in which the products and credit matrices are meaningfully distinct. For example, the Australian Electricity Market would be distinct from the New Zealand Electricity Market.

Within each market are ‘Regions’, which now represent the Australian NEM regional reference nodes.

In a previous update, we have already added the ‘regions’ request parameters and response properties, allowing you to migrate your system over now.

What is changing?

In this update, we are changing how the ‘markets’ parameters and response properties are handled, replacing ‘market’ with ‘region’. So you will need to update any API integration with some small changes, detailed below.

After the rollout date, any integration that uses the old ‘market’ to indicate the regional reference node (region) will fail requests.

When is it changing?

The rollout date is planned for the weekend beforeMay 4, 2026, with changes live as of that date.

The new ‘regions’ paradigm is already available on live, so any update to your system can implement the change in production environments without waiting for the rollout date.

The additional multi-market changes are already on our staging environment now, so additional testing against the new update is available against that environment.

What should I update?

There are more specific details below, but these are the 2 quick steps to update your API consuming applications:

Get the latest v03 of the example spreadsheet

If you only interact with our API through our example spreadsheet (or the VBA code within), then go download the latest version of that spreadsheet here: API DocumentationPreview

The official Excel Add-in already supports this update; the ‘Market’ column in live prices has been replaced with 'Region'.

Open

The TOD Markets Excel Add-In

Change ‘markets=’ to ‘regions=’

If you have built any integrations that hit the /api/assets or /api/assets/prices endpoints, you only need to change the name of the ‘markets’ parameter to ‘regions’.

[domain]/api/assets?markets=V+Q+N should become [domain]/api/assets?regions=V+Q+N

[domain]/api/assets/prices?markets=V+Q+N -> [domain]/api/assets/prices?regions=V+Q+N

Update your consuming code

When you parse the response from /api/assets/prices, your code might expect a ‘market’ property to indicate the regional node. If your code relies on the ‘market’ property indicating the node, simply change it to look for the ‘region’ property in each asset price.

A similar change has happened in the /api/assets endpoint; we have added a ‘region_code’ and ‘region_name’ property to the ‘prices’ array items. If your code relies on the ‘market_code’ and ‘market_name’ properties to interpret the regional node, simply change it to look for that value in the ‘region_code’ and ‘region_name’.

Endpoint: GET /api/assets/prices

New request parameter

• “regions”: optional | string | the region codes for the asset, separated with a '+'. Options are the same as the old market code. [N, Q, S, T & V]

Modified request parameter

• “markets”: optional | string | the region codes for the asset, separated with a ‘+'. This will default to the only option available at the time of writing: 'AUEL’ for the Australian Electricity Market.

New response properties added:

Added to items in the ‘prices’ array in the response body.

• "region": string | the region code for the asset

Modified property:

Added to items in the ‘prices’ array in the response body.

• “market”: string | Now returns the 4-character market code ('AUEL' for Australian Electricity)

Endpoint: GET /api/assets

New request parameter

• “regions”: string | the region codes for the asset, separated with a '+'. Options are the same as the old market code. [N, Q, S, T & V]

Modified request parameter

• “markets”: optional | string | the region codes for the asset, separated with a ‘+'. This will default to the only option available at the time of writing: 'AUEL’ for the Australian Electricity Market.

New response properties added:

These are added to items in the ‘assets’ array in the response body.

• "region_code": string | the region code for the asset, indicating the state regional node [N, Q, S, T & V]

• "region_name": string | the name of the region (Queensland, New South Wales, etc..)

Modified property:

These are added to items in the ‘assets’ array in the response body.

• “market_code”: string | Now returns the 4-character market code ('AUEL' for Australian Electricity)

• “market_name”: string | Will return the full name of the market for the asset, all current assets are under the ‘Australian Electricity’ market.

Further Documentation

The official Postman Documentation has been updated for these endpoints.

Postman Documentation: TOD Markets

We are also able to provide any integration support!