Outcome
List interviews by start time, optionally for one application, by status, or only the caller's own (mine=true). Interviewers always see only interviews they are on; hiring managers only those for roles they manage. Each interview carries candidateName, roleTitle and interviewers[] with display names, so no further reads are needed to show it.
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.list --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
topolo actions get app_topolo_recruit.applications.list --detail --json
Request
GET /api/interviews
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 |
|---|---|---|---|
applicationId | Optional | string | Application id from applications.list in the same workspace. {"minLength":1,"maxLength":64} |
mine | Optional | string | {"enum":["true","false"]} |
status | Optional | string | {"enum":["scheduled","completed","cancelled"]} |
Exact input schema:
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"applicationId": {
"type": "string",
"minLength": 1,
"maxLength": 64
},
"mine": {
"type": "string",
"enum": [
"true",
"false"
]
},
"status": {
"type": "string",
"enum": [
"scheduled",
"completed",
"cancelled"
]
}
},
"additionalProperties": false
}
Effects
- Reads interviews without changing state.
Interpret the response
With mine=true, confirm every interviewerUserIds contains the caller.
The response identifier path is $.interviews[].id for interview. Lists may be empty; an empty list is not a discovered target.
Exact success schema:
{
"type": "object",
"required": [
"interviews"
],
"properties": {
"interviews": {
"type": "array",
"items": {
"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"
]
}
}
}
}
}
}
}
}
}
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:
{}
CLI:
topolo actions validate app_topolo_recruit.interviews.list --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.list --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.interviews.list --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.list",
"input": {},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>"
}
}
Captured local response · HTTP 200:
{
"interviews": []
}
HTTP 200. With mine=true, confirm every interviewerUserIds contains the caller.
Another supported 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:
{}
CLI:
topolo actions validate app_topolo_recruit.interviews.list --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.list --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.interviews.list --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.list",
"input": {},
"resourceType": "workspace",
"resourceId": "<identifier returned by resource discovery>"
}
}
Captured local response · HTTP 200:
{
"interviews": [
{
"id": "int_09d7450809b14ac3ad25e0bb1ae590b1",
"applicationId": "apl_46e7f4f8f8374f7e8eb3903fc1982c2c",
"candidateId": "cand_54ffc82037794474b7c9c2862379f600",
"roleId": "role_c62e11c5727b43728db0491a197aec51",
"stageId": "stg_0d33b2fd26004bf1931d36a8f1e27b30",
"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": "scheduled",
"interviewerUserIds": [
"u_int"
],
"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"
}
]
}
]
}
HTTP 200. With mine=true, confirm every interviewerUserIds contains the caller.
Refused request · hiring_team_role_required
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 is a refused request; diagnose it before retrying.
Input · payload.json:
{
"mine": "true",
"status": "scheduled"
}
CLI:
topolo actions validate app_topolo_recruit.interviews.list --data @payload.json --json
topolo actions plan app_topolo_recruit.interviews.list --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
- With mine=true, confirm every interviewerUserIds contains the caller.
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.
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.
Related actions
- 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.
- Get my scorecard: Read the caller's own scorecard for an interview they are on (null before they save one) and the criteria to rate. A scorecard is private to its author until submitted.
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.