# Retrieve an office hours schedule

You can fetch the details of a single office hours schedule.

Endpoint: GET /office_hours_schedules/{id}
Version: Preview
Security: bearerAuth

## Header parameters:

  - `Intercom-Version` (string)
    Intercom API version.By default, it's equal to the version set in the app package.
    Enum: "1.0", "1.1", "1.2", "1.3", "1.4", "2.0", "2.1", "2.2", "2.3", "2.4", "2.5", "2.6", "2.7", "2.8", "2.9", "2.10", "2.11", "2.12", "2.13", "2.14", "2.15", "Preview"

## Path parameters:

  - `id` (string, required)
    The unique identifier for the office hours schedule.
    Example: "123"

## Response 200 fields (application/json):

  - `type` (string)
    The type of the object - always office_hours_schedule.
    Example: "office_hours_schedule"

  - `id` (string)
    The unique identifier for the office hours schedule.
    Example: "123"

  - `name` (string)
    The name of the office hours schedule.
    Example: "Standard Support Hours"

  - `time_zone_name` (string)
    The IANA time zone the schedule's hours are evaluated in.
    Example: "America/New_York"

  - `time_intervals` (array)
    The open intervals that make up the weekly schedule.

  - `time_intervals.start_minute` (integer)
    Minute the interval starts. For schedules, offset from the start of the week (Monday 00:00 = 0); for exceptions, offset from midnight on exception_date.
    Example: 540

  - `time_intervals.end_minute` (integer)
    Minute the interval ends. For schedules, offset from the start of the week (Monday 00:00 = 0); for exceptions, offset from midnight on exception_date.
    Example: 1020

  - `time_intervals.day_of_week` (integer)
    Derived day of the week the interval falls on (0 = Monday … 6 = Sunday). For exceptions, this is derived from exception_date.

  - `twenty_four_seven` (boolean)
    Whether the schedule is open 24/7.

  - `created_at` (integer)
    The time the schedule was created as a Unix timestamp.
    Example: 1717200000

  - `updated_at` (integer)
    The time the schedule was last updated as a Unix timestamp.
    Example: 1717200000

## Response 401 fields (application/json):

  - `type` (string, required)
    The type is error.list
    Example: "error.list"

  - `request_id` (string,null)
    Example: "f93ecfa8-d08a-4325-8694-89aeb89c8f85"

  - `errors` (array, required)
    An array of one or more error objects

  - `errors.code` (string, required)
    A string indicating the kind of error, used to further qualify the HTTP response code
    Example: "unauthorized"

  - `errors.message` (string,null)
    Optional. Human readable description of the error.
    Example: "Access Token Invalid"

  - `errors.field` (string,null)
    Optional. Used to identify a particular field or query parameter that was in error.
    Example: "email"