Every endpoint, parameter and response here is extracted programmatically from
the Postman collection — nothing is retyped. Quotes are verbatim; values are
labelled Tier A · source-verbatim or
Tier B · authored illustration.
How this was built →
The bulk screening lifecycle — a 6-step state machine
The collection names these endpoints "Step 1" through "Step 6"
in the requests themselves, and the server enforces the order — run Step 3
before Step 2 and you get a real 403. Try it below: the simulator
replays the collection's own saved responses, in and out of order.
How to read this simulator
Response bodies marked
Tier A · source-verbatim are the
collection's saved examples, exactly as shipped. Where a coherent narrative
needs values the collection doesn't provide (consistent row counts, a
processed status body — none exists in the file), the simulator
uses Tier B · authored illustration data,
which has no source and is labelled so you can never mistake it for the
API's word. Details: Lesson 5.
Project state: no project yet.
Start with Step 1 — or deliberately start with Step 3 to see the server say no.
One shot to load records. "Only one list of individuals
can be added to a project" — assemble your complete list before Step 2.
Poll, don't assume. Step 5 returns 202
("The requested project is still being processed.") until Step 4 reports
processed. A 202 on a GET means come back later.
Reconcile. If Step 4's validRows <
totalRows, Step 6 tells you which rows failed and why — per row
number, possibly multiple errors per row.