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

# List Simple Scheduler configs

> Scheduler configurations for the team. Team is resolved from `x-team-id` or the optional `team_id` query parameter (multi-team keys must have access to that team). Requires the `read:scheduler_analytics` permission.



## OpenAPI

````yaml /api-reference/openapi.json get /api/simple_scheduler_config
openapi: 3.1.0
info:
  title: Avoca Enterprise API
  description: >-
    Read-only programmatic access to Avoca data: calls, transcripts, leads,
    coach evaluations, Simple Scheduler sessions and analytics, and outbound
    texting activity.
  version: 1.3.0
servers:
  - url: https://enterprise-api.avoca.ai
security:
  - bearerAuth: []
tags:
  - name: Calls
    description: Call records, transcripts, and pre-call transfers
  - name: Leads
    description: Unified leads (v0) and the canonical leads feed (v1)
  - name: Teams
    description: Teams accessible to the API key
  - name: Coach
    description: Coach (QA) call evaluations and rubrics
  - name: Scheduler Analytics (v0)
    description: Simple Scheduler analytics — legacy flat endpoints
  - name: Sessions & Bookings
    description: v1 scheduling-widget sessions and completed bookings
  - name: Analytics (v1)
    description: v1 funnel, UTM, service-area, and issue-type analytics
  - name: Outbound Texting
    description: Campaign text and subscription-event feeds for BI ingestion
paths:
  /api/simple_scheduler_config:
    get:
      tags:
        - Scheduler Analytics (v0)
      summary: List Simple Scheduler configs
      description: >-
        Scheduler configurations for the team. Team is resolved from `x-team-id`
        or the optional `team_id` query parameter (multi-team keys must have
        access to that team). Requires the `read:scheduler_analytics`
        permission.
      operationId: listSimpleSchedulerConfigs
      parameters:
        - $ref: '#/components/parameters/xTeamId'
        - name: team_id
          in: query
          description: >-
            Target team (alternative to the x-team-id header for multi-team
            keys)
          schema:
            type: integer
      responses:
        '200':
          description: Scheduler configs
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/SchedulerConfig'
        '403':
          $ref: '#/components/responses/Forbidden'
components:
  parameters:
    xTeamId:
      name: x-team-id
      in: header
      description: >-
        Target team ID. Required for multi-team (`enterprise_all_teams` /
        `portfolio_all_teams`) keys on v0 endpoints; single-team keys are locked
        to their team and omit it.
      schema:
        type: integer
  schemas:
    SchedulerConfig:
      type: object
      properties:
        id:
          type: integer
        team_id:
          type: integer
        name:
          type: string
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    Error:
      type: object
      properties:
        error:
          type: string
          description: Error type
        message:
          type: string
          description: Human-readable description (newer endpoints)
      required:
        - error
  responses:
    Forbidden:
      description: API key lacks the required permission or team access
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: API key in the format `avoca_<64 hex characters>`

````