Skip to main content
An assessment is a timed (or untimed) test: tasks, a passing score, and optional proctoring.

If you are recruiting / ops

1

Create the assessment

In the dashboard, create a new assessment. Give it a clear title hiring managers will recognise.
2

Add tasks

Attach platform tasks and/or your org’s custom tasks. Order them the way candidates should see them.
3

Set rules

Time limit, passing score (default 70%), and proctoring options. See Proctoring.
4

Set status to Active

Drafts cannot receive invites. Activate when you are ready to send candidates.
5

Invite

Continue on Invitations (UI or API).
Archive assessments you no longer use instead of deleting them (there is no Public API delete).

For engineers

Path ids accept slug or UUID — never the human title alone.

Lifecycle

Endpoints

List query: status (active | draft | archived | all), search, team_slug / team_id, cursor, page_size.

Create → attach → activate

Always starts as draft. Then attach tasks (source: platform or org):
After candidates have started, the lineup locks → 409 TASKS_LOCKED. Activate:
Send only fields you mean to change on PATCH. Duplicate: POST /assessments/{slug}/duplicate/ → new draft (201). Candidates/results are not copied. SDK helpers: SDKs.

Next

Invitations

Send candidate links.

Custom tasks

Build your own question library.
Last modified on August 24, 2026