Get an interview

Read one interview with the candidate's name, the role title, the interviewers' display names and the scorecard criteria the interview stage defines.

Outcome

Read one interview with the candidate's name, the role title, the interviewers' display names and the scorecard criteria the interview stage defines.

Before you start

Verify identity and the pinned organization context, then discover the exact action and a granted Recruit workspace.
The required application permission is workspace:read. Hiring-team roles and record visibility are enforced separately; a workspace grant alone does not grant every Recruit action.
Organization and workspace identity come from verified context. Pass the workspace as resourceType/resourceId, separate from action input; request-body organizationId/workspaceId values cannot select an authorized scope.
The first authorized action can initialize an identity-only workspace mirror and invoke the configured workspace-created callback. It does not create an Auth workspace or grant new access.

Recruiters can perform the full hiring workflow. Hiring managers see their managed roles and candidates; interviewers see assigned interviews and their candidates. Workspace owners and organization administrators act as recruiters. Use team.me to read the caller's effective role and allowed actions.

Discover the target

topolo whoami --json
topolo actions get app_topolo_recruit.interviews.get --detail --json
topolo resources topolo-recruit --json
topolo workspaces list topolo-recruit --json
topolo actions get app_topolo_recruit.team.me --detail --json
topolo actions get app_topolo_recruit.interviews.list --detail --json

Request

GET /api/interviews/{id}

Save input as payload.json. CLI and MCP action input includes path identifiers. The reviewed plan separates path/query fields from the HTTP body. Set RECRUIT_WORKSPACE_ID from granted resource discovery.

Inspect and test this action in the signed action console. Use its discovered schema and plan; a test response still requires the verification described below.

Input fields

Field	Required	Type	Constraints
`id`	Required	string	Interview id from interviews.list; this is not a scorecard id. {"minLength":1,"maxLength":64}

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Effects

Reads one interview without changing state.

Interpret the response

Confirm $.interview.id equals the requested id.

The response identifier path is $.interview.id for interview. Lists may be empty; an empty list is not a discovered target.

Exact success schema:

{
  "type": "object",
  "required": [
    "interview"
  ],
  "properties": {
    "interview": {
      "type": "object",
      "properties": {
        "id": {
          "type": "string"
        },
        "applicationId": {
          "type": "string"
        },
        "candidateId": {
          "type": "string"
        },
        "roleId": {
          "type": "string"
        },
        "stageId": {
          "type": "string"
        },
        "title": {
          "type": "string"
        },
        "startsAt": {
          "type": "string"
        },
        "endsAt": {
          "type": "string"
        },
        "timezone": {
          "type": [
            "string",
            "null"
          ]
        },
        "location": {
          "type": [
            "string",
            "null"
          ]
        },
        "meetingUrl": {
          "type": [
            "string",
            "null"
          ]
        },
        "status": {
          "enum": [
            "scheduled",
            "completed",
            "cancelled"
          ]
        },
        "interviewerUserIds": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "candidateName": {
          "type": "string"
        },
        "roleTitle": {
          "type": "string"
        },
        "interviewers": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "userId": {
                "type": "string"
              },
              "displayName": {
                "type": [
                  "string",
                  "null"
                ]
              }
            }
          }
        }
      }
    },
    "candidate": {
      "type": "object"
    },
    "scorecardCriteria": {
      "type": "array",
      "items": {
        "type": "object"
      }
    }
  }
}

Worked examples

Actual dispatcher and migration-created SQLite or Worker handlers; Auth/workspace identity, object storage, mail and Notify dependencies are simulated. These synthetic fixtures establish no live authorization or delivery. A synthetic fixture identifier grants no access. Validate and inspect the planned request before executing. Commands with --confirm or MCP confirm:true assume the intended effect or data export has already been authorized.

Successful request

Actual dispatcher and migration-created SQLite; verified Auth/workspace context, object storage, mail and Notify dependencies are simulated. No live delivery or credential authorization is established. This complete response is a local fixture, not a deployed or delivered result.

Input · payload.json:

{
  "id": "int_44770559bb994ca298bf23ea18d281fd"
}

CLI:

topolo actions validate app_topolo_recruit.interviews.get --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.get --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.interviews.get --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_recruit.interviews.get",
    "input": {
      "id": "int_44770559bb994ca298bf23ea18d281fd"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "interview": {
    "id": "int_44770559bb994ca298bf23ea18d281fd",
    "applicationId": "apl_4699f5f032cd46a29d8ce62ac984f94e",
    "candidateId": "cand_ae90b4a5b1264c07bf198988f73f2b6c",
    "roleId": "role_f70eadb49e934aef92f972f25efbe64b",
    "stageId": "stg_fe59f1242ab9477caef151318b104c2f",
    "title": "Technical interview",
    "startsAt": "2026-10-06T09:00:00+01:00",
    "endsAt": "2026-10-06T10:00:00+01:00",
    "timezone": null,
    "location": null,
    "meetingUrl": null,
    "status": "scheduled",
    "interviewerUserIds": [
      "u_int",
      "u_int2"
    ],
    "candidateName": "Ada Lovelace",
    "createdBy": "u_admin",
    "createdAt": "2026-10-05T09:00:00.000Z",
    "updatedAt": "2026-10-05T09:00:00.000Z",
    "roleTitle": "Engineer",
    "interviewers": [
      {
        "userId": "u_int",
        "displayName": "Name u_int"
      },
      {
        "userId": "u_int2",
        "displayName": null
      }
    ]
  },
  "candidate": {
    "id": "cand_ae90b4a5b1264c07bf198988f73f2b6c",
    "firstName": "Ada",
    "lastName": "Lovelace"
  },
  "scorecardCriteria": []
}

HTTP 200. Confirm $.interview.id equals the requested id.

Another supported request

Input · payload.json:

{
  "id": "int_4d51b68d95094ff78cc4eab85e9a018b"
}

CLI:

topolo actions validate app_topolo_recruit.interviews.get --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.get --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.interviews.get --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json

MCP tool and arguments:

{
  "tool": "topolo_read_action",
  "arguments": {
    "actionId": "app_topolo_recruit.interviews.get",
    "input": {
      "id": "int_4d51b68d95094ff78cc4eab85e9a018b"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "interview": {
    "id": "int_4d51b68d95094ff78cc4eab85e9a018b",
    "applicationId": "apl_51a27597eb0a4130aeb5f74136af7d9d",
    "candidateId": "cand_25bfd0790b994884bf377f5be2331ebf",
    "roleId": "role_f8999bb39e954d4a821cbcc04e32f337",
    "stageId": "stg_e9853144fcff4354be1e75144f0c0418",
    "title": "Technical interview",
    "startsAt": "2026-10-06T09:00:00+01:00",
    "endsAt": "2026-10-06T10:00:00+01:00",
    "timezone": "Europe/London",
    "location": null,
    "meetingUrl": "https://meet.example.com/abc",
    "status": "completed",
    "interviewerUserIds": [
      "u_int",
      "u_int2"
    ],
    "candidateName": "Ada Lovelace",
    "createdBy": "u_admin",
    "createdAt": "2026-10-05T09:00:00.000Z",
    "updatedAt": "2026-10-05T09:00:00.000Z",
    "roleTitle": "Engineer",
    "interviewers": [
      {
        "userId": "u_int",
        "displayName": null
      },
      {
        "userId": "u_int2",
        "displayName": null
      }
    ]
  },
  "candidate": {
    "id": "cand_25bfd0790b994884bf377f5be2331ebf",
    "firstName": "Ada",
    "lastName": "Lovelace"
  },
  "scorecardCriteria": [
    {
      "id": "design",
      "label": "System design"
    },
    {
      "id": "code",
      "label": "Coding"
    }
  ]
}

HTTP 200. Confirm $.interview.id equals the requested id.

Refused request · not_found

Input · payload.json:

{
  "id": "int_09d7450809b14ac3ad25e0bb1ae590b1"
}

CLI:

topolo actions validate app_topolo_recruit.interviews.get --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.get --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 404:

{
  "error": {
    "code": "not_found",
    "message": "Interview was not found in this workspace."
  }
}

HTTP 404. Preserve the exact response code and details. Do not claim success.

Refused request · hiring_team_role_required

Input · payload.json:

{
  "id": "int_example"
}

CLI:

topolo actions validate app_topolo_recruit.interviews.get --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.get --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json

Captured local response · HTTP 403:

{
  "error": {
    "code": "hiring_team_role_required",
    "message": "Your hiring-team role in this workspace does not allow this action.",
    "details": {
      "teamRole": null,
      "allowedRoles": [
        "recruiter",
        "hiring_manager",
        "interviewer"
      ]
    }
  }
}

HTTP 403. Preserve the exact response code and details. Do not claim success.

Verify the result

Confirm $.interview.id equals the requested id.

Errors and recovery

organization_context_required (HTTP 403): Select the organization authorized by the credential; do not send an organization id in the action input.
permission_denied (HTTP 403): Grant the credential the required Recruit workspace permission.
hiring_team_role_required (HTTP 403): Ask a recruiter to give the caller a hiring-team role that allows this action (team.members.set); error.details lists the allowed roles.
workspace_required (HTTP 409): Create a Recruit workspace, or pass the workspace resource context.
invalid_input (HTTP 422): Correct the fields named in error.details using inputSchema, then retry.
not_found (HTTP 404): List interviews to find a valid id. Records outside the caller's hiring-team view also answer 404.

Authentication or gateway failures may occur before the Recruit handler. Preserve the exact discovered service error, request id and credential context. The local fixtures do not establish live credential authorization.

Recovery boundary

This action does not change service state.

Evidence

Actual dispatcher and migration-created SQLite or Worker handlers; Auth/workspace identity, object storage, mail and Notify dependencies are simulated. These synthetic fixtures establish no live authorization or delivery. Test capture provenance is retained with each fixture. API, database and integration outcomes require separate verification in the target environment.