> ## Documentation Index
> Fetch the complete documentation index at: https://docs.engrate.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Schedule Series

> List all [Schedule Series](/api-reference/schedule-management/models/schedule-series) within a schedule version.



## OpenAPI

````yaml /openapi.json get /schedule-management/v1/schedule-series/{version_uid}
openapi: 3.1.0
info:
  title: Engrate API
  version: 1.0.0
servers:
  - url: https://api.engrate.io
security:
  - apiKeyAuth: []
paths:
  /schedule-management/v1/schedule-series/{version_uid}:
    get:
      tags:
        - schedules
      summary: Get Schedule Series
      description: >-
        List all [Schedule
        Series](/api-reference/schedule-management/models/schedule-series)
        within a schedule version.
      operationId: >-
        get_schedule_series_schedule_management_v1_schedule_series__version_uid__get
      parameters:
        - description: Schedule version unique identifier.
          in: path
          name: version_uid
          required: true
          schema:
            description: Schedule version unique identifier.
            format: uuid
            title: Version Uid
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                items:
                  $ref: '#/components/schemas/ScheduleSeriesResponse'
                title: >-
                  Response Get Schedule Series Schedule Management V1 Schedule
                  Series  Version Uid  Get
                type: array
          description: Successful Response
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
components:
  schemas:
    ScheduleSeriesResponse:
      description: >-
        A [Schedule
        Series](/api-reference/schedule-management/models/schedule-series)
        representing one time series within a schedule version (e.g. one
        internal or external trade).
      example:
        acceptance_level: cnf
        created_ts: '2026-03-25T14:00:00+00:00'
        last_modified_ts: '2026-03-25T14:05:00+00:00'
        spec:
          data:
            - amount: 10.5
              ts: '2026-03-25T23:00:00+00:00'
          ids:
            in_area: 10YDE-VE-------2
            in_party: 11XDE-EXAMPLE--A
            out_area: 10YDE-VE-------2
            out_party: 11XDE-EXAMPLE--B
          type: internal
        status: cnf
        time_series_uid: TS-001
        uid: d1e2f3a4-b5c6-4d7e-8f9a-0b1c2d3e4f5a
        version: 1
      properties:
        acceptance_level:
          description: >-
            Highest acceptance level reached by the parent version: empty
            string, `ack`, `ano`, `par`, or `cnf`.
          examples:
            - cnf
            - ack
            - ''
          title: Acceptance Level
          type: string
        created_ts:
          description: ISO 8601 datetime when the parent version was created.
          examples:
            - '2026-03-25T14:00:00+00:00'
          title: Created Ts
          type: string
        interval_statuses:
          anyOf:
            - additionalProperties:
                type: string
              type: object
            - type: 'null'
          description: >-
            Per-interval status map. Always `null` — market-access tracks status
            at version granularity, not per interval.
          title: Interval Statuses
        last_modified_ts:
          description: ISO 8601 datetime of the parent version's most recent status change.
          examples:
            - '2026-03-25T14:05:00+00:00'
          title: Last Modified Ts
          type: string
        spec:
          $ref: '#/components/schemas/ScheduleSeriesSpec'
          description: >-
            Full series specification including identifiers, type, and interval
            data.
        status:
          description: >-
            Processing status of the parent version. `created` before
            submission, then the verbatim market status: `submitted`,
            `ack_positive`, `ack_negative`, `ack_partial`, `icnf`, `dacnf`,
            `cnf`, `cnf_partial`, or `fcnf`.
          examples:
            - cnf
            - submitted
            - ack_negative
          title: Status
          type: string
        time_series_uid:
          description: Time series identifier used in the ESS/CIM document.
          examples:
            - TS-001
          title: Time Series Uid
          type: string
        uid:
          description: Unique identifier for this series record.
          examples:
            - d1e2f3a4-b5c6-4d7e-8f9a-0b1c2d3e4f5a
          title: Uid
          type: string
        version:
          description: Version number of the parent schedule version.
          examples:
            - 1
            - 2
          title: Version
          type: integer
      required:
        - acceptance_level
        - created_ts
        - last_modified_ts
        - spec
        - status
        - time_series_uid
        - uid
        - version
      title: ScheduleSeriesResponse
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      type: object
    ScheduleSeriesSpec:
      description: 'Full series specification: identifiers, type, and interval data.'
      properties:
        data:
          description: >-
            Interval data points, one per slot, ordered from the start of the
            delivery day.
          items:
            $ref: '#/components/schemas/ScheduleSeriesDataPoint'
          title: Data
          type: array
        ids:
          $ref: '#/components/schemas/ScheduleSeriesIds'
          description: EIC identifiers for the series exchange.
        type:
          description: >-
            Series type: `internal`, `external`, `foreign`, `production`, or
            `consumption`.
          examples:
            - internal
            - external
            - production
          title: Type
          type: string
      required:
        - data
        - ids
        - type
      title: ScheduleSeriesSpec
      type: object
    ValidationError:
      properties:
        ctx:
          title: Context
          type: object
        input:
          title: Input
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          title: Location
          type: array
        msg:
          title: Message
          type: string
        type:
          title: Error Type
          type: string
      required:
        - loc
        - msg
        - type
      title: ValidationError
      type: object
    ScheduleSeriesDataPoint:
      description: 'One interval of a schedule series: a timestamp and its power amount.'
      properties:
        amount:
          description: Power value for the interval, in MW.
          examples:
            - 10.5
          title: Amount
          type: number
        ts:
          description: ISO 8601 UTC start of the interval.
          examples:
            - '2026-03-25T23:00:00+00:00'
          title: Ts
          type: string
      required:
        - amount
        - ts
      title: ScheduleSeriesDataPoint
      type: object
    ScheduleSeriesIds:
      description: EIC identifiers locating a series in the area/party exchange.
      properties:
        in_area:
          description: EIC Y code of the receiving control area.
          examples:
            - 10YDE-VE-------2
          title: In Area
          type: string
        in_party:
          description: EIC X code of the receiving party (balance responsible party).
          examples:
            - 11XDE-EXAMPLE--A
          title: In Party
          type: string
        out_area:
          description: EIC Y code of the sending control area.
          examples:
            - 10YDE-VE-------2
          title: Out Area
          type: string
        out_party:
          description: EIC X code of the sending party (balance responsible party).
          examples:
            - 11XDE-EXAMPLE--B
          title: Out Party
          type: string
      required:
        - in_area
        - in_party
        - out_area
        - out_party
      title: ScheduleSeriesIds
      type: object
  securitySchemes:
    apiKeyAuth:
      in: header
      name: Authorization
      type: apiKey

````