Participant endpoints
POST /participants — Create a participant
POST /participants — Create a participant
POST /participants/batch — Create or update participants in batch
POST /participants/batch — Create or update participants in batch
Participants are matched by email. The format of every row is validated first: a single invalid row rejects the whole request with status
422, and the error key points to that row (for example participants.3.email). Once validation passes, each row is processed separately and the outcome is reported per row:created— a new participant was created, or a previously deleted participant was restored.updated— the participant already exists andupdate_existingistrue.skipped— the participant already exists andupdate_existingisfalse. The item includes areason.failed— the row could not be processed. The item includes areasonand noparticipant_id.
Parameters
Example request
Example response
PATCH /participants/{id} — Update a participant
PATCH /participants/{id} — Update a participant
DELETE /participants/{id} — Delete a participant
DELETE /participants/{id} — Delete a participant
GET /participants/{id}/exams — List a participant's exams
GET /participants/{id}/exams — List a participant's exams
Sorted from the most recent registration.
results contains one item for each test in the exam, with the same structure as in the Exam Results API.
