---
title: "Retrieve a price time series"
method: GET
path: "/subscriptions/{id}/prices"
tags: ["Prices"]
---

# Retrieve a price time series

`GET /subscriptions/{id}/prices`

Retrieve a price object for a given subscription. For a consumption subscription this is the variable price time series the customer pays and can optimize consumption against; for a feed-in subscription it is the payout the customer is credited per kWh, based on EPEX day-ahead spot prices and without grid fees. All prices are inclusive of VAT, except feed-in payouts to a VAT-exempt customer.

## Path parameters

- `id` string, required

## Query parameters

- `start` string, required — Start date of the period at 00:00:00 in local time of the customer (format yyyy-mm-dd)
- `end` string, required — End date of the period at 23:59:59 in local time of the customer (format yyyy-mm-dd)

## Response `200`

Retrieve the price details

- Price
  - `object` 'price', required
  - `subscription` string, required — The id of the subscription
  - `period` object, required
    - `start` string, required — Start date of the period at 00:00:00 local time in UTC.
    - `end` string, required — End date of the period at 23:59:59 local time in UTC.
  - `unit` string, required — The unit of the price
  - `currency` string, required — The currency of the price
  - `resolution` 'hourly' | '15min', required — The time resolution of the price data points
  - `reference` string, required — Reference market for electricity prices
  - `items` object[], nullable, required — List of price data points. Null if subscription is not active (either hasn't started yet or has ended).
    - `timestamp` string, required — Timestamp for the price point in UTC
    - `amount` number, nullable, required — Total price per unit. In rare cases, the price might be null if parts of the price information is currently not available.
    - `components` object[], required — Breakdown of price components
      - `type` 'electricity' | 'grid' | 'levies', required — Type of price component
      - `amount` number, nullable, required — Amount for this component

## 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.dev/nomos/apis/nomos-api.md) · [All operations](https://skmtc.dev/nomos/apis/nomos-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/nomos/nomos-api/revisions/da60ad83e92f/schema)