Skip to main content

List eligible delegates for delegated verification (external integration)​

External-integration twin of GetHelpdeskVerifyDelegateCandidates. Returns the delegates the operator may pick for a given subject and mode. global_approved → approved-list members eligible for the chosen verification_method; line_manager → the subject's line manager (HRIS graph); unconstrained → empty.

For unconstrained the integration should collect the delegate email as free text: enumerating every user is intentionally unsupported, and the console fills that case from a sensor-authenticated peer search that is not reachable from an integration. Note that under unconstrained the delegate-initiate call validates only that the delegate is reachable (has an active sensor / is present in the verification source), not that they are on any eligibility list — which is what the mode means.

Query Parameters
  • subject_email email
  • delegation_mode string required

    Possible values: [global_approved, line_manager, unconstrained]

  • connection_id string required
  • identity_id string

    The subject's identity id from the external verification-candidates list. Required when verification_method is email_otp.

  • verification_method string

    Possible values: [sensor_totp, email_otp]

    Which verification method the delegate will participate in. Controls delegate eligibility: sensor_totp (default) requires an active device; email_otp requires an IdP-resolvable email. sensor_totp requires subject_email; email_otp requires identity_id.

  • operator_email email required

    The human operating the integration. MUST be derived server-side by the integration, never supplied by its own client. Resolved to a SlashID console person holding a verifier role.

  • operator_assertion string required

    Possible values: [integration_asserted, idp_verified]

    How the operator identity was established.

Header Parameters
  • SlashID-OrgID string required

    The organization ID

    Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
Responses

Eligible delegates

Schema
  • meta object
  • pagination object
  • limit integer
  • offset integer
  • total_count int64
  • cursor_pagination object

    Cursors are opaque. Follow the tokens the server returns; never construct, parse or modify one.

  • limit integer
  • next_cursor string

    Opaque token addressing the next page. Absent on the last page.

  • prev_cursor string

    Opaque token addressing the previous page. Absent on the first page.

  • last_cursor string

    Opaque token addressing the final page directly, so a client can jump to the end without a total count.

  • total_count int64

    Total number of matching items. Returned on the FIRST page only; clients cache it for the remainder of the walk.

  • errors object[]
  • httpcode integer
  • message string
  • result object
  • delegation_mode string

    Possible values: [global_approved, line_manager, unconstrained]

    How a delegate is selected for delegated verification. global_approved — pick from the org's approved delegate list. line_manager — the subject's line manager, resolved via the HRIS graph. unconstrained — any user eligible for the chosen verification method.

  • candidates object[]

    Eligible delegates for the subject under the given mode. Empty for unconstrained (the client picks any user via peer search). Eligibility depends on verification_method.

  • email string

    A delegate email eligible for the requested mode and verification method