Skip to main content
This guide walks you through administering a cognitive roadmap: a multi-test package that collects answers from several psychological tests and produces a single AI-powered combined analysis. You will list roadmaps, authenticate all role profiles (using either SMS verification or the instant path), complete each test, trigger AI generation, and retrieve the final report.
Prerequisites
  • A valid API key from the organizer panel, sent in the API-KEY header
  • At least one roadmap with status: 2 (ready) available in your account
Do not use /record/{token}/auth/ for test records that belong to a roadmap. Roadmap profiles must be authenticated through /roadmap/{token}/auth/ instead, which registers all participants across every test in the package.

Two authentication paths

Every roadmap payload (and each nested item in test_records) includes an organizer-level flag named tests_auth_required that controls how authentication works: Read tests_auth_required from the roadmap before choosing the next step.
1

List your roadmaps

Fetch your available roadmaps and filter for unfinished packages.
Look for a roadmap with status: 2 (ready). The response includes the token you need and tests_auth_required which tells you whether SMS verification is on.
2

Inspect the roadmap

Retrieve the full roadmap details to understand its structure, roles, and test records.
Key fields to review:
  • roles: array of role definitions, each with an id, title, min_age, max_age, and gender
  • test_records: array of individual test records included in the package (each also carries tests_auth_required)
  • status: must be 2 (ready)
  • auth_required: indicates whether profiles still need to be linked
  • tests_auth_required: selects the auth path
3

Start authentication for all roles

Post every role profile in a single call. This registers all participants across every test in the package.Single-role roadmap example
Two-role roadmap example (couple)
  • mobile: shared contact number for the roadmap. When SMS verification is on, the code is sent here.
  • roles: array where each object contains the role id and a profile object with the same fields used in standalone tests.
The response echoes tests_auth_required. Branch on it to decide the next step.SMS path (tests_auth_required: true)
An SMS code is sent to the shared mobile. Keep the draft_token for the verify step. It expires after 5 minutes.Instant path (tests_auth_required: false)
All profiles are created and linked to every record in the package. Skip the next step.
4

Verify the SMS code (SMS path only)

Ask for the code sent to the shared mobile and submit it with the draft_token.
Success response
Common errorsSkip this step entirely when tests_auth_required is false.
5

Complete each test record

For every test record inside the roadmap, fetch its questions and submit answers. The order does not matter, but all records must be finished before you can generate the AI analysis.Pseudocode for looping through records
Example curl for one record
Never call POST /record/{token}/auth/ or PUT /record/{token}/auth/verify/ for roadmap records. Authentication was already completed at the roadmap level.
6

Request AI generation

Once every test record in the roadmap is finished, queue the AI analysis.
The roadmap status changes to 4 (AI processing). Generation typically takes 5 to 10 minutes.
7

Poll for generation status

Check the generation status periodically until it completes or fails.
Polling logic example
Stop polling when the response returns state: "completed" or state: "failed".
8

Retrieve the results

After the AI analysis completes, fetch the combined report.
The JSON response contains structured AI analysis, scores from all tests, and combined interpretations. The HTML response is a ready-to-render report page.

Flow summary

SMS enabled (tests_auth_required: true, default)
SMS disabled (tests_auth_required: false)

What to do next