List candidates

List the workspace's candidates, newest first (default 100, at most 200), each with their applications (id, roleId, stageId, status). Filter by q (name contains, or an exact email), roleId, stageId, tag, or status (active by default; archived). An email query also returns job-board records flagged as possible duplicates of that candidate (duplicateOf set). Hiring managers see only candidates on their roles; interviewers only candidates they interview.

Outcome

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.candidates.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.candidates.list --detail --json
topolo actions get app_topolo_recruit.roles.list --detail --json
topolo actions get app_topolo_recruit.roles.get --detail --json

Request

GET /api/candidates

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
`q`	Optional	string	{"maxLength":120}
`roleId`	Optional	string	Role id from roles.list. Hiring managers must select a role they manage when creating a candidate. {"minLength":1,"maxLength":64}
`stageId`	Optional	string	Stage id from roles.get or applications.get for the intended role. {"minLength":1,"maxLength":64}
`tag`	Optional	string	{"maxLength":40}
`status`	Optional	string	{"enum":["active","archived"]}
`limit`	Optional	integer	{"minimum":1,"maximum":200}

Exact input schema:

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 120
    },
    "roleId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64
    },
    "stageId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 64
    },
    "tag": {
      "type": "string",
      "maxLength": 40
    },
    "status": {
      "type": "string",
      "enum": [
        "active",
        "archived"
      ]
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 200
    }
  },
  "additionalProperties": false
}

Effects

Reads candidates without changing state.

Interpret the response

Confirm each candidate matches the filters given.

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

Exact success schema:

{
  "type": "object",
  "required": [
    "candidates"
  ],
  "properties": {
    "candidates": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id"
        ],
        "properties": {
          "id": {
            "type": "string"
          },
          "firstName": {
            "type": "string"
          },
          "lastName": {
            "type": "string"
          },
          "email": {
            "type": "string"
          },
          "phone": {
            "type": [
              "string",
              "null"
            ]
          },
          "location": {
            "type": [
              "string",
              "null"
            ]
          },
          "profileUrl": {
            "type": [
              "string",
              "null"
            ]
          },
          "source": {
            "enum": [
              "job_board",
              "manual",
              "sourced",
              "referral",
              "imported",
              "agency"
            ]
          },
          "sourceDetail": {
            "type": [
              "string",
              "null"
            ]
          },
          "tags": {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          "status": {
            "enum": [
              "active",
              "archived"
            ]
          },
          "consentAt": {
            "type": [
              "string",
              "null"
            ]
          },
          "retainUntil": {
            "type": [
              "string",
              "null"
            ]
          },
          "createdAt": {
            "type": "string"
          },
          "updatedAt": {
            "type": "string"
          },
          "duplicateOf": {
            "type": [
              "string",
              "null"
            ],
            "description": "Set on a job-board record whose email belongs to this existing candidate id; merge it with candidates.merge once a recruiter has checked it is the same person."
          },
          "locale": {
            "type": [
              "string",
              "null"
            ],
            "description": "The language the candidate applied in on the job board (en, ar, es, fr, de, pt-BR, ja or hi); Recruit's default emails to them use it. Null when unknown: those emails follow the sender's language."
          },
          "applications": {
            "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:

{
  "q": "ADA@example.com"
}

CLI:

topolo actions validate app_topolo_recruit.candidates.list --data @payload.json --json
topolo actions plan app_topolo_recruit.candidates.list --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.candidates.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.candidates.list",
    "input": {
      "q": "ADA@example.com"
    },
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "candidates": [
    {
      "id": "cand_38ac335ce27a401ebc33f301c75e4aa7",
      "firstName": "Ada",
      "lastName": "Lovelace",
      "email": "ada@example.com",
      "phone": "+44 2",
      "location": null,
      "profileUrl": null,
      "source": "manual",
      "sourceDetail": null,
      "tags": [],
      "status": "active",
      "consentAt": null,
      "consentNotice": null,
      "retainUntil": "2027-10-05T09:00:00.000Z",
      "createdBy": "u_admin",
      "createdAt": "2026-10-05T09:00:00.000Z",
      "updatedAt": "2026-10-05T09:00:00.000Z",
      "duplicateOf": null,
      "applications": [
        {
          "id": "apl_ac8b3e893b8f4c57a65cd88d1ff60740",
          "roleId": "role_8f00120a183a4ebaa59c0c88e48134d5",
          "stageId": "stg_cfc11805806a4822942ca3fcb2ad5605",
          "status": "active",
          "appliedAt": "2026-10-05T09:00:00.000Z",
          "roleTitle": "Engineer",
          "stageName": "Applied"
        }
      ]
    }
  ]
}

HTTP 200. Confirm each candidate matches the filters given.

Another supported request

Input · payload.json:

{}

CLI:

topolo actions validate app_topolo_recruit.candidates.list --data @payload.json --json
topolo actions plan app_topolo_recruit.candidates.list --resource-type workspace --resource-id "$RECRUIT_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_recruit.candidates.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.candidates.list",
    "input": {},
    "resourceType": "workspace",
    "resourceId": "<identifier returned by resource discovery>"
  }
}

Captured local response · HTTP 200:

{
  "candidates": []
}

HTTP 200. Confirm each candidate matches the filters given.

Refused request · hiring_team_role_required

Input · payload.json:

{
  "q": "smith",
  "roleId": "role_example"
}

CLI:

topolo actions validate app_topolo_recruit.candidates.list --data @payload.json --json
topolo actions plan app_topolo_recruit.candidates.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

Confirm each candidate matches the filters given.

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): Inspect the required Recruit permission and the credential’s granted workspace access. Use an already authorized credential/scope or request the missing access from its owner. Change credentials or grants only under separate explicit authorization; do not expand permissions automatically to clear this refusal.
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.
api_key_workspace_binding_required (HTTP 403): Use a key explicitly bound to the intended granted workspace. Inspect Auth api_keys.options before creating or changing a key, and obtain approval for any credential or access change; do not widen bindings automatically.
workspace_required (HTTP 400): Send the workspace the key is bound to with --resource-type workspace --resource-id <workspace id> (or the X-Topolo-Resource-Type and X-Topolo-Resource-Id headers).
workspace_forbidden (HTTP 403): Use a workspace the key is bound to; read the key's bindings in API key management.
workspace_access_insufficient (HTTP 403): The required workspace permission is workspace:read for reads or workspace:write for changes, including deletion. Inspect the authorized key options and resource access; request any missing access from its owner rather than granting it automatically.
api_key_scope_required (HTTP 403): Read requiredScope in the refusal and inspect Auth api_keys.options for the authorized operation. Request any needed access from its owner; create or update a key only with explicit approval. Do not retry an unchanged 403 or widen scopes automatically.

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.

Get a candidate: Read one candidate's profile: contact details, source, tags, consent and retention date, their applications (with answers and cover letter), documents (metadata; fetch content with candidates.documents.get) and activity timeline, newest first. Only applications on roles the caller may see are included. candidate.duplicateOf is set on a job-board record that used this existing candidate's email; possibleDuplicates lists such records pointing at this candidate (id, name, createdAt) for a recruiter to compare and merge.

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.

Documentation history

2026-10-18

Updated the precise candidate response records and current request/response examples.
Updated this guide from source revision 63171ed7c08aa066adb44cc01e64011e465302e1; retained 3 source-captured request/response examples and their simulated-dependency limitations.
Clarified authorized API-key/resource recovery without automatic permission expansion. This documentation update does not establish deployment, live hiring operations or notification delivery.

List candidates

Outcome

Before you start

Discover the target

Request

Input fields

Effects

Interpret the response

Worked examples

Successful request

Another supported request

Refused request · hiring_team_role_required

Verify the result

Errors and recovery

Recovery boundary

Related actions

Evidence

Documentation history

2026-10-18