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

# Get Schedule Job

> Retrieve a scheduled job by id



## OpenAPI

````yaml get /schedules/v1/cron-jobs/{id}/
openapi: 3.1.0
info:
  title: Cekura API
  version: v1
  description: >-
    Complete API documentation for the Cekura platform. This API provides
    endpoints for testing, observing, and evaluating AI voice agents — including
    managing agents, running evaluators, defining metrics, and analyzing call
    quality.
servers:
  - url: https://api.cekura.ai
security: []
paths:
  /schedules/v1/cron-jobs/{id}/:
    get:
      tags:
        - schedules
      description: Retrieve a scheduled job by id
      operationId: cron-jobs-retrieve
      parameters:
        - in: path
          name: id
          schema:
            type: integer
          description: A unique integer value identifying this cron job.
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CronJob'
          description: ''
      security:
        - api_key: []
components:
  schemas:
    CronJob:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        agent:
          type: integer
          description: |

            Agent ID for the cron job
            Example: `123`
        name:
          type: string
          description: Name for the cronjob
          maxLength: 255
        crontab_expression:
          type: string
          description: |

            Crontab expression for the cron job
            Example: 
            - `"0 9 * * 1-5"`
            - `"0 0 * * 0"`
          maxLength: 255
        timezone:
          type: string
          description: |

            Timezone for the cron job
            Example: `"America/Los_Angeles"`
        scenarios:
          writeOnly: true
          description: |

            List of scenario IDs for the cron job
            Example: `[123, 456, 789]`
        scenario_ids:
          type: array
          items:
            type: integer
          readOnly: true
          description: |

            List of scenario IDs for the cron job
            Example: `[123, 456, 789]`
        scenarios_data:
          type: array
          items:
            $ref: '#/components/schemas/ScenarioInline'
          readOnly: true
        personality:
          type:
            - integer
            - 'null'
          description: |

            (Deprecated) Use personalities field instead.
            Example: `1` (personality ID)
        personalities:
          type: array
          items:
            type: integer
          description: >

            List of personalities to use for test execution. Multiple
            personalities can be assigned to run tests with different
            configurations.

            Example: `[1, 2, 3]` (personality IDs)
        tags:
          type: array
          items:
            type: string
          description: |

            List of tags for the cron job
            Example: `["tag1", "tag2", "tag3"]`
        frequency:
          type: integer
          maximum: 100
          minimum: 1
          description: |

            Frequency for the cron job
            Example: `1`
        run_as_text:
          type: boolean
          description: >

            DEPRECATED: Use execution_mode instead. Kept for backward
            compatibility.

            Run the cron job as text

            Example: `true` or `false`
        execution_mode:
          enum:
            - voice
            - text
            - sip
            - vapi_webrtc
            - retell_webrtc
            - elevenlabs
            - ello
            - livekit_v2
            - pipecat_v2
          type: string
          x-spec-enum-id: 6e5503f819d0efa7
          description: >-

            Execution mode for the cron job

            Choices: voice, text, sip, vapi_webrtc, elevenlabs, pipecat_v2,
            livekit_v2, retell_webrtc, ello

            Example: `"voice"`, `"text"`, `"sip"`, `"pipecat_v2"`,
            `"elevenlabs"`, or `"livekit_v2"`



            * `voice` - Voice

            * `text` - Text

            * `sip` - SIP

            * `vapi_webrtc` - VAPI WebRTC

            * `retell_webrtc` - Retell WebRTC

            * `elevenlabs` - ElevenLabs

            * `ello` - Ello

            * `livekit_v2` - LiveKit

            * `pipecat_v2` - Pipecat
        notify_on:
          enum:
            - never
            - success
            - failure
            - both
          type: string
          x-spec-enum-id: d06ae6855e4121c0
          description: |-

            Select when to notify 


            * `never` - Never
            * `success` - Success
            * `failure` - Failure
            * `both` - Both
        is_active:
          type: boolean
        created_by:
          type: integer
          readOnly: true
        created_via:
          enum:
            - user
            - api
            - mcp
            - cli
            - sdk
            - null
          type:
            - string
            - 'null'
          x-spec-enum-id: 360ac7f2b69a95cc
          readOnly: true
          description: >-
            How the cron job was created: user (UI), api (API key), or mcp (MCP
            client)


            * `user` - User

            * `api` - API

            * `mcp` - MCP

            * `cli` - CLI

            * `sdk` - SDK
        created_at:
          type: string
          format: date-time
          readOnly: true
          description: |

            Timestamp when the cron job was created
            Example: `2021-01-01 00:00:00`
        updated_at:
          type: string
          format: date-time
          readOnly: true
          description: |

            Timestamp when the cron job was last updated
            Example: `2021-01-01 00:00:00`
      required:
        - crontab_expression
    ScenarioInline:
      type: object
      properties:
        id:
          type: integer
          readOnly: true
        agent:
          type:
            - integer
            - 'null'
        name:
          type: string
          description: Name of the scenario
          maxLength: 80
        personality:
          type:
            - integer
            - 'null'
        personality_name:
          type: string
          readOnly: true
  securitySchemes:
    api_key:
      type: apiKey
      name: X-CEKURA-API-KEY
      in: header
      description: >-
        API Key Authentication. It should be included in the header of each
        request.

````