Skip to main content
GET
cURL

Authorizations

Authorization
string
header
required

Your API key, sent as Authorization: Bearer <key>. A key is nrk_live_ or nrk_test_, a 26-character key id, _ and a 43-character secret. Account, audit and usage data stay within the key's environment. Dedicated team scopes apply across the workspace.

assess creates and reads assessments, records outcomes and reports key usage. investigate reads accounts, assessment history and request diagnostics without export or enforcement access. The legacy history scope also permits account exports, submitted identifiers and enforcement reports. delete permits account and assessment deletion.

evidence or detailed adds detailed merged evidence and submitted identifiers where the operation permits them. Neither grants access to the underlying resource alone. exports permits exports with the underlying account or audit scope. audit reads audit events and usage reads usage. audit_manage manages audit streams and retention, and includes audit-read and export authority.

webhooks manages webhook endpoints. integrations manages hosted auth-provider integrations. management manages keys, settings, lists, reviews and policy evaluations in the key's environment. New keys cannot exceed the issuer's effective permissions.

settings reads configuration, previews policy and list changes, runs evaluations and changes retention. Publishing decision policy or changing lists requires settings and policy_publish together, or the legacy management scope.

groups creates and reads groups, adds people, starts and cancels screenings and records decisions on people, in the key's environment.

members reads the workspace directory. members_manage also administers non-owner members and invitations. These scopes require a live key issued by a current owner with access to both environments. They grant access across the workspace. management does not grant team access. API keys cannot change owners or accept invitations.

A missing, unknown, revoked or expired key answers 401. A valid key without a required scope answers 403.

Path Parameters

workspace_id
string
required

The workspace id. A workspace the acting user is not an active member of answers 404, as do another workspace than an API key's own, a malformed id and a test environment's id. The workspace id, which is also its live environment's workspace id; the test environment's is the same id with:test appended. A workspace created through the API is tnt_ and a 26-character ULID.

Pattern: ^[A-Za-z0-9][A-Za-z0-9_.-]{0,122}$
environment
enum<string>
required

The environment: live or test. Each has its own settings. Any other value answers 400. An API key reads and changes only its own environment's; the other answers 404. The environment the key belongs to. A live key assesses with live sources; a test key answers from the deterministic simulator.

Available options:
live,
test
group_id
string
required
Pattern: ^grp_[0-7][0-9A-HJKMNP-TV-Z]{25}$
person_id
string
required
Pattern: ^per_[0-7][0-9A-HJKMNP-TV-Z]{25}$

Response

The person, their matched profiles, findings and every recorded decision.

Everything known about one person, and where else in the environment they appear.

person
object
required

A person and where their screening and review stand.

profiles
object[]
required

The accounts the latest screening matched, with how each was matched.

Maximum array length: 100
findings
object[]
required

What the latest screening flagged, most severe first, each citing its evidence.

Maximum array length: 500
posts
object[]
required

The posts the findings cite.

Maximum array length: 5000
media
object[]
required

The images and videos the findings cite.

Maximum array length: 5000
reviews
object[]
required

Every recorded decision, oldest first.

Maximum array length: 1000
other_groups
object
required

The other groups of this environment where a person with the same email or phone appears, newest group first. History only: nothing in it changes this person's screening, band, match state or decision.

lookup
object

What the latest screening's lookups found, and the records the searches people started found, each match naming its search. Absent until a screening that ran lookups reaches the person.

searches
object[]

The searches people started on this person's values, newest first: each names the value, and the record and field it came from. Absent when nobody searched.

Maximum array length: 10000