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

# Set a verdict

> Records a human accept / reject / maybe on one candidate. Send `null` to clear a verdict.

Every call also writes a candidate feedback event — the verdict, the reason codes, the rank the candidate was shown at, its score and subscores, and a snapshot of the criteria it was judged against. That trail is what scoring quality is measured and tuned against, so reason codes are worth sending.



## OpenAPI

````yaml /openapi.json post /api/scans/{id}/candidates/{candidateId}/verdict
openapi: 3.1.0
info:
  title: Revcenter API
  description: >-
    Search, enrich, and activate people and companies. Two authentication
    surfaces share one host: the bearer-token API under `/v1` for
    server-to-server and agent use, and the workspace-session API under `/api`
    that the Revcenter app itself runs on.
  version: '2026-08-12'
servers:
  - url: https://api.revcenter.ai
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Search
    description: Web search, search runs, results, exports, and shareable shortlists.
  - name: People
    description: Person search, profile enrichment, and the workspace contact pool.
  - name: Companies
    description: Company search, company enrichment, and org-chart people.
  - name: Campaigns
    description: Plan, publish, and launch outbound sequences on Smartlead and HeyReach.
  - name: Account
    description: Health, usage totals, and cost events.
paths:
  /api/scans/{id}/candidates/{candidateId}/verdict:
    post:
      tags:
        - Search
      summary: Set a verdict
      description: >-
        Records a human accept / reject / maybe on one candidate. Send `null` to
        clear a verdict.


        Every call also writes a candidate feedback event — the verdict, the
        reason codes, the rank the candidate was shown at, its score and
        subscores, and a snapshot of the criteria it was judged against. That
        trail is what scoring quality is measured and tuned against, so reason
        codes are worth sending.
      operationId: setCandidateVerdict
      parameters:
        - $ref: '#/components/parameters/ScanId'
        - name: candidateId
          in: path
          required: true
          description: The candidate's ID, as returned in `candidates[].candidate.id`.
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                verdict:
                  type:
                    - string
                    - 'null'
                  enum:
                    - accept
                    - reject
                    - maybe
                    - null
                  description: >-
                    `null` clears the verdict and logs a `verdict_cleared`
                    event.
                reasonCodes:
                  type: array
                  items:
                    type: string
                  description: Why. `reason_codes` is accepted as an alias.
                notes:
                  type: string
                  maxLength: 4000
                  description: Free-text note. Truncated at 4000 characters.
                source:
                  type: string
                  maxLength: 120
                  default: scan_candidate_panel
                  description: >-
                    Where the verdict came from, for attribution in the feedback
                    log.
            examples:
              reject:
                summary: Reject with reasons
                value:
                  verdict: reject
                  reasonCodes:
                    - wrong_seniority
                    - geo_mismatch
                  notes: Director-level, and based in Ottawa.
              clear:
                summary: Clear a verdict
                value:
                  verdict: null
      responses:
        '200':
          description: The verdict was recorded.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ok:
                    type: boolean
                  verdict:
                    type:
                      - string
                      - 'null'
                    enum:
                      - accept
                      - reject
                      - maybe
                      - null
        '400':
          $ref: '#/components/responses/AppBadRequest'
        '401':
          $ref: '#/components/responses/AppUnauthorized'
        '404':
          $ref: '#/components/responses/AppNotFound'
        '502':
          $ref: '#/components/responses/AppUpstreamError'
      security:
        - sessionCookie: []
components:
  parameters:
    ScanId:
      name: id
      in: path
      required: true
      description: The search ID.
      schema:
        type: string
        format: uuid
  responses:
    AppBadRequest:
      description: Missing or invalid input.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            missing:
              value:
                error: criteria (CriteriaV2) is required
    AppUnauthorized:
      description: >-
        Not signed in, no active workspace, or the account lacks the role this
        action needs. A frozen account gets `403` with code `frozen`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            signIn:
              value:
                error: Sign in required
    AppNotFound:
      description: >-
        The record does not exist, or belongs to another workspace. The two are
        deliberately indistinguishable.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            notFound:
              value:
                error: Scan not found
    AppUpstreamError:
      description: A downstream service or the database failed.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/AppError'
          examples:
            upstream:
              value:
                error: Spec extraction failed
  schemas:
    AppError:
      type: object
      description: >-
        The error shape used by every `/api` endpoint. Flatter than the `/v1`
        shape, and `code` appears only where the UI branches on it.
      properties:
        error:
          type: string
        code:
          type: string
          examples:
            - search_unavailable
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        A Revcenter API key: `Authorization: Bearer rvc_live_...`. Keys are
        scoped, rate limited per key, and metered per workspace.
    sessionCookie:
      type: apiKey
      in: cookie
      name: session
      description: >-
        A signed-in workspace session, sent as a browser cookie. Requests must
        include credentials, and act on the session's active workspace.

````