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

# Get Resolved Schedule

> ### Overview
Resolves one or more entities' schedules over a date range into concrete daily availability windows (`bounds`), any blackout `blocks`, and — when `include_rules=true` — the raw underlying rules and config each schedule was resolved from. Also returns each entity's `schedule_id`.



## OpenAPI

````yaml get /schedule/resolved
openapi: 3.0.0
info:
  title: Ekacare API & Webhook Documentation
  contact: {}
  version: '1.0'
servers:
  - description: Production
    url: https://api.eka.care
  - description: Stage/Sandbox
    url: https://api.dev.eka.care
security: []
paths:
  /schedule/resolved:
    get:
      tags:
        - Appointment API
      summary: Get Resolved Schedule
      description: >-
        ### Overview

        Resolves one or more entities' schedules over a date range into concrete
        daily availability windows (`bounds`), any blackout `blocks`, and — when
        `include_rules=true` — the raw underlying rules and config each schedule
        was resolved from. Also returns each entity's `schedule_id`.
      operationId: GetBusinessResolvedSchedule
      parameters:
        - name: auth
          in: header
          description: ''
          required: true
          style: simple
          schema:
            type: string
            example: auth
        - name: time-zone
          in: header
          description: >-
            IANA timezone for the returned ISO timestamps. Defaults to
            `Asia/Kolkata`.
          required: false
          style: simple
          schema:
            type: string
            example: Asia/Kolkata
        - name: entity_id
          in: query
          description: Comma-separated entity ids to resolve. Deduplicated; max 20 values.
          required: true
          style: form
          explode: true
          schema:
            type: string
            example: doc_12345,doc_67890
        - name: location_id
          in: query
          description: Location/clinic id to resolve against.
          required: true
          style: form
          explode: true
          schema:
            type: string
            example: c-98765
        - name: product_id
          in: query
          description: One of `product-emr`, `product-widget`. Defaults to `product-emr`.
          required: false
          style: form
          explode: true
          schema:
            type: string
            enum:
              - product-emr
              - product-widget
        - name: startTime
          in: query
          description: >-
            Range start, ISO datetime. Must be before `endTime`; range capped at
            400 days.
          required: true
          style: form
          explode: true
          schema:
            type: string
            example: '2026-09-22T00:00:00.000Z'
        - name: endTime
          in: query
          description: Range end, ISO datetime.
          required: true
          style: form
          explode: true
          schema:
            type: string
            example: '2026-09-29T00:00:00.000Z'
        - name: applyBlock
          in: query
          description: Whether to apply blackout blocks when resolving bounds.
          required: false
          style: form
          explode: true
          schema:
            type: string
            enum:
              - 'true'
              - 'false'
        - name: include_rules
          in: query
          description: >-
            When `true`, includes `rules` and `config` per schedule alongside
            the resolved bounds.
          required: false
          style: form
          explode: true
          schema:
            type: string
            enum:
              - 'true'
              - 'false'
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  status:
                    type: integer
                    example: 200
                  data:
                    type: object
                    description: >-
                      Keyed by `entity_id`; each value is a list because an
                      entity may resolve to more than one schedule (e.g. across
                      products).
                    additionalProperties:
                      type: array
                      items:
                        type: object
                        properties:
                          schedule_id:
                            type: string
                          name:
                            type: string
                          schedule_slot_config_enabled:
                            type: boolean
                          slot_durations:
                            type: array
                            items:
                              type: integer
                          schedule:
                            type: object
                            description: >-
                              Keyed by ISO date. Each value has the resolved
                              `bounds` for that day and any `blocks`.
                            additionalProperties:
                              type: object
                              properties:
                                bounds:
                                  type: array
                                  items:
                                    type: object
                                    properties:
                                      s:
                                        type: string
                                        description: Window start, ISO.
                                      e:
                                        type: string
                                        description: Window end, ISO.
                                      source:
                                        type: string
                                        description: >-
                                          Which rule type this window was resolved
                                          from
                                          (weekly/daily/repeat-weekly/repeat-daily).
                                      services:
                                        type: array
                                        items:
                                          type: object
                                          properties:
                                            conf_id:
                                              type: string
                                            name:
                                              type: string
                                            modes:
                                              type: array
                                              items:
                                                type: string
                                            duration:
                                              type: integer
                                              nullable: true
                                blocks:
                                  type: array
                                  items:
                                    type: object
                                    properties:
                                      block_id:
                                        type: string
                                      s:
                                        type: string
                                      e:
                                        type: string
                          config:
                            type: object
                            description: Only present when `include_rules=true`.
                          rules:
                            type: object
                            description: >-
                              Only present when `include_rules=true`. Raw stored
                              rule rows: `weekly`, `daily`, `repeat-weekly`,
                              `repeat-daily`, `block`. Only "live" recurring
                              rows are included (no `end_date`, or `end_date` in
                              the future).
              example:
                success: true
                status: 200
                data:
                  doc_12345:
                    - schedule_id: 651f0c2b8e4a2d1a2c3b4d5e
                      name: Dr. Sharma - OPD
                      schedule_slot_config_enabled: false
                      slot_durations: []
                      schedule:
                        '2026-09-22':
                          bounds:
                            - s: '2026-09-22T09:00:00.000+05:30'
                              e: '2026-09-22T13:00:00.000+05:30'
                              source: weekly
                              services:
                                - conf_id: conf_abc123
                                  name: OPD Consultation
                                  modes:
                                    - clinic
                                  duration: 15
                          blocks: []
                      config:
                        overbooking_limit: 2
                        schedule_slot_config_enabled: false
                        slot_durations: []
                      rules:
                        weekly:
                          '1':
                            is_enabled: true
                            bounds:
                              - s: 900
                                e: 1300
                                conf_ids:
                                  - conf_abc123
                        daily: {}
                        repeat-weekly: []
                        repeat-daily: []
                        block: []
        '400':
          description: >-
            Bad Request — missing/invalid `entity_id`, `location_id`,
            `product_id`, date range, or range exceeding 400 days
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: false
                  error:
                    type: string
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: false
                  error:
                    type: string
                    example: failed to resolve schedules
      deprecated: false

````