Skip to main content
POST
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

Body

application/json

Creates a group.

name
string
required

The group's name.

Required string length: 1 - 200
starts_at
string<date-time>
required

When the group starts.

ends_at
string<date-time>

When the group ends, at or after its start; the start when omitted.

venue
string

Where the group is held.

Maximum string length: 300
host
string

The organisation hosting the group.

Maximum string length: 200
principals
object[]

The people the group protects, at most 20.

Maximum array length: 20
topics
string[]

Sensitive topics the screening reads posts against, at most 50.

Maximum array length: 50
Required string length: 1 - 100

Response

The group is created.

A group and its screening context.

id
string
required
Pattern: ^grp_[0-7][0-9A-HJKMNP-TV-Z]{25}$
environment
enum<string>
required
Available options:
live,
test
name
string
required

The group's name.

Required string length: 1 - 200
starts_at
string<date-time>
required

When the group starts.

ends_at
string<date-time>
required

When the group ends, at or after its start; the start when omitted.

principals
object[]
required

The people the group protects.

Maximum array length: 20
topics
string[]
required

Sensitive topics.

Maximum array length: 50
Required string length: 1 - 100
people
integer
required

How many people the group holds.

Required range: 0 <= x <= 20000
version
integer
required

Goes up by one with every change.

Required range: 1 <= x <= 2147483647
purge_after
string<date-time>
required

When raw collected items and unmatched candidate profiles are purged: 30 days after the group ends.

created_by
string
required

The member or key label that created the group.

Required string length: 1 - 256
created_at
string<date-time>
required
updated_at
string<date-time>
required
venue
string

Where the group is held.

Maximum string length: 300
host
string

The organisation hosting the group.

Maximum string length: 200