Access Roles

Each access key is granted one or more of nine permissions — grant only what an integration actually needs, since every key can be scoped independently.

Published 2026/08/26

Every access key is granted one or more of the following permissions. An endpoint returns 403 Forbidden if the key used doesn't have the permission it needs — see Errors.

Permission	Unlocks
List tasks	Listing, fetching, and searching Tasks
Update tasks	Updating a Task (beta)
List tests	Listing, fetching, and searching Tests
List users	Listing, fetching, and searching Users
Write users	Reserved — no user-creation or user-update endpoint is available yet
List tickets	Listing, fetching, and searching Candidates, and listing/fetching/searching Test Sessions & Results
Write tickets	Creating, updating, and deleting Candidates
Query test results	Reading a Test Session's result and score breakdown
Fetch monitoring assets	Fetching Proctoring Evidences and Answers of a Test Session

“Ticket” here is the internal name for what the REST API calls a Candidate — the permission names haven't caught up to the current terminology, but List tickets / Write tickets are exactly the permissions that gate the Candidates endpoints.

Go back