> ## 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

> Get a specific [Schedule](/api-reference/schedule-management/models/schedule) by UID.

Returns the schedule header (market, TSO, delivery date). Use `GET /schedules/{uid}/versions` to retrieve submitted [Schedule Versions](/api-reference/schedule-management/models/schedule-version).



## OpenAPI

````yaml /openapi.json get /schedule-management/v1/schedules/{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/schedules/{uid}:
    get:
      tags:
        - schedules
      summary: Get Schedule
      description: >-
        Get a specific
        [Schedule](/api-reference/schedule-management/models/schedule) by UID.


        Returns the schedule header (market, TSO, delivery date). Use `GET
        /schedules/{uid}/versions` to retrieve submitted [Schedule
        Versions](/api-reference/schedule-management/models/schedule-version).
      operationId: get_schedule_schedule_management_v1_schedules__uid__get
      parameters:
        - description: Schedule unique identifier.
          in: path
          name: uid
          required: true
          schema:
            description: Schedule unique identifier.
            format: uuid
            title: Uid
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ScheduleResponse'
          description: Successful Response
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
          description: Validation Error
components:
  schemas:
    ScheduleResponse:
      description: >-
        A [Schedule](/api-reference/schedule-management/models/schedule) header
        representing a single delivery-date submission to a TSO.
      example:
        created_ts: '2026-03-25T14:00:00+00:00'
        date: '2026-03-26'
        last_modified_ts: '2026-03-25T16:30:00+00:00'
        market: DE
        org_uid: 9b2e4d8f-1c3a-4f5e-8d7b-6a9e0f2c1b3d
        tso: 50HERTZ_DE_TSO
        uid: f47ac10b-58cc-4372-a567-0e02b2c3d479
      properties:
        created_ts:
          description: ISO 8601 datetime when the schedule was created.
          examples:
            - '2026-03-25T14:00:00+00:00'
          title: Created Ts
          type: string
        date:
          description: Delivery date in ISO 8601 format (`YYYY-MM-DD`).
          examples:
            - '2026-03-26'
          title: Date
          type: string
        last_modified_ts:
          description: ISO 8601 datetime of the most recent modification.
          examples:
            - '2026-03-25T16:30:00+00:00'
          title: Last Modified Ts
          type: string
        market:
          description: Target market. `DE` for Germany, `NL` for the Netherlands.
          examples:
            - DE
            - NL
          title: Market
          type: string
        org_uid:
          description: Organization that owns this schedule.
          examples:
            - 9b2e4d8f-1c3a-4f5e-8d7b-6a9e0f2c1b3d
          title: Org Uid
          type: string
        tso:
          description: Transmission System Operator identifier.
          examples:
            - 50HERTZ_DE_TSO
            - DE-AMPRION-TSO
            - TTG_DE
            - DE-TRANSNETBWTSO
            - TENNET_TSO
          title: Tso
          type: string
        uid:
          description: Unique identifier for this schedule.
          examples:
            - f47ac10b-58cc-4372-a567-0e02b2c3d479
          title: Uid
          type: string
      required:
        - created_ts
        - date
        - last_modified_ts
        - market
        - org_uid
        - tso
        - uid
      title: ScheduleResponse
      type: object
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          title: Detail
          type: array
      title: HTTPValidationError
      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
  securitySchemes:
    apiKeyAuth:
      in: header
      name: Authorization
      type: apiKey

````