---
title: "Create a load forecast"
method: POST
path: "/load-forecasts"
tags: ["Usage"]
---

# Create a load forecast

`POST /load-forecasts`

This endpoint is used to transmit a load forecast for a subscription. Values must be submitted by 9:00 a.m. local time on the previous day to be considered in the day-ahead auction, and at least 15 minutes before delivery to be included in continuous intraday trading. Data points must be strictly consecutive and can only be provided for full days at a time (local time of the subscription).

## Request body

- object
  - `scope` 'subscription', required — Reference point for the load forecast
  - `subscription` string, required — Required subscription ID when scope is 'subscription'
  - `resolution` '15min', required — Time resolution of the load forecast data points
  - `unit` 'KW', required — Unit of measurement for the forecast values
  - `data` object[], required — Array of load forecast data points. Must be strictly consecutive with exactly 15-minute intervals and without overlaps or gaps and can only contain one data point per 15-minute interval.
    - `start` string, date-time, required — Timestamp of the data point
    - `value` number, required — Power value at this timestamp. Must not be negative.

## Response `200`

Positive response

- LoadForecasts
  - `scope` 'subscription', required
  - `subscription` string, required
  - `start` string, date-time, required
  - `end` string, date-time, required
  - `total` number, required

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
- `401` — The client must authenticate itself to get the requested response.
- `402` — A higher pricing plan is required to access the resource.
- `403` — The client does not have the necessary permissions to access the resource.
- `404` — The server can't find the requested resource.
- `405` — The request method is not allowed.
- `409` — The request could not be completed due to a conflict mainly due to unique constraints.
- `422` — The request was well-formed but was unable to be followed due to semantic errors.
- `429` — The client has sent too many requests.
- `500` — The server has encountered a situation it doesn't know how to handle.

---

[API](https://skmtc.net/nomos/apis/nomos-api.md) · [All operations](https://skmtc.net/nomos/apis/nomos-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nomos/nomos-api/versions/da60ad83e92f/schema)