Skip to main content

Before you start

You need your API key and the service URL, both provided by n:lead. The key goes into the X-API-Key header of every request.

Send a forecast

1

Prepare the day's series

One value per quarter-hour, from local midnight to local midnight (Europe/Berlin): 96 values on a normal day, 92 on the spring-forward day, 100 on the fall-back day. Production and consumption are separate series, tagged per control area.
2

POST it

3

Check the acknowledgment

The daily totals are a quick plausibility check — if they look wrong, the submitted series are wrong. The input_hash identifies exactly this submission; quote it if you need to ask about a delivery day.

When to send

Send the forecast for delivery day D day-ahead, in time for the EPEX day-ahead auction (gate closure 12:00 CET on D-1; agree your cut-off with n:lead). Re-send whenever your forecast improves — the latest submission for a delivery day wins and everything downstream re-runs automatically.

No forecast to send?

If you only have master data and metered data per customer, the bridge can build the consumption forecast for you — see Data delivery.
Sending an identical payload twice changes nothing (same input_hash), so retries are safe.