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

# Update round



## OpenAPI

````yaml /api-reference/openapi.json patch /api/v1/rounds/{id}
openapi: 3.1.0
info:
  title: intervyo.ai REST API
  version: 1.0.0
  description: >-
    Programmatic access to participants, sessions, roles, rounds, interviewers,
    and code execution.


    **Authentication.** Pass your API key in the `x-api-key` header (`x-api-key:
    iv_live_...`). Keys are created in the team dashboard under **Developer →
    API Keys**. Session (cookie) auth also works from the dashboard; for those
    calls pass `accountSlug` as a query parameter.
servers:
  - url: https://www.intervyo.ai
    description: Production
security:
  - apiKey: []
tags:
  - name: Participants
    description: >-
      Participants (candidates, applicants, trainees) are the people being
      evaluated. Create them first, then schedule sessions.
  - name: Sessions
    description: >-
      A session is one AI interview instance for one participant. Create a
      participant first, then schedule a session — the invite email is sent
      automatically.
  - name: Roles
    description: >-
      Templates define what the AI should assess — the role, skills, objective,
      and pass bar. Every session and stage belongs to a template.
  - name: Rounds
    description: >-
      Stages are the individual interview steps within a template — e.g. Phone
      Screen → Technical → Final. Each stage can have a different AI agent,
      duration, and pass threshold.
  - name: Interviewers
    description: >-
      Interviewers define the AI persona, evaluation dimensions, scoring logic,
      and tone. Assign an Interviewer to a Round to customise how the AI
      conducts that interview.
  - name: Code Execution
    description: >-
      Run candidate code against test cases. Currently supports python,
      javascript, and typescript via the OneCompiler runner. This endpoint is
      also exposed as the execute_code MCP tool — same engine, different
      transport.
  - name: Remote MCP Server
    description: >-
      Expose problem generation and code execution to any MCP-compatible client
      (Claude Desktop, Claude Code, Cursor). Speaks JSON-RPC 2.0 over HTTP.
      Requires an API key — session cookies are NOT accepted on this surface.
      Usage is metered against your plan (mcp_problem_generations and
      mcp_code_executions).
paths:
  /api/v1/rounds/{id}:
    patch:
      tags:
        - Rounds
      summary: Update round
      operationId: patch_api_v1_rounds_id
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
            format: uuid
          description: id identifier
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                stage_name:
                  type: string
                  description: Display name
                stage_type:
                  type: string
                  description: Interview format
                duration_minutes:
                  type: integer
                  description: Session length
                interviewer_id:
                  type: string
                  format: uuid
                  description: AI persona
                stage_order:
                  type: integer
                  description: Position in pipeline
                difficulty:
                  type: string
                  description: Question depth
                pass_threshold:
                  type: number
                  description: Min score to pass
                automation_rule:
                  type: string
                  description: Post-completion automation
                status:
                  type: string
                  enum:
                    - draft
                    - active
                    - archived
                  description: Stage status
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request — Validation error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized — Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: Forbidden — Insufficient permissions
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Not Found — Round not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message
        issues:
          type: array
          items:
            type: object
          description: Field-level validation issues (present on 400 responses)
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        API key with the `iv_live_` prefix. Create one under Developer → API
        Keys.

````