Skip to main content
Once you have an interview (interview_def_set_id from Create an interview), there are two ways to get candidates in:
Interview role-plays — the interview-portal variant of a role-play persona — are invited exactly the same way. Pass their interview_def_set_id as the interview_id below; nothing else changes.
POST /job-interview-register-users handles both, switched by type:
  • type: "url" — generates a public interview URL (with an embedded JWT) per user. You redirect/send it yourself. No email is sent.
  • type: "invitation" — also subscribes the user to JobMojito’s email chain (invitation, reminders, and completion notifications).
1

Build the user list

Each user needs name and email; external_id is optional (your own id, echoed back).
2

Call the endpoint

Required fields: interview_id, type, hide_menu, and users.
3

Read the per-user result

The response is an array mirroring your input, with an interview_url, profile_interview_id, and a result per user (ok or Error: …).

Fields

Candidate invitations consume merchant interview credits. Each user is processed independently — one failing user returns an Error: … result for that row while the others still succeed.

Alternative: invite to the merchant

POST /invite-users invites people to the merchant and can attach candidates to an interview. It also supports mentor, merchant, and merchant_owner types.
For type: "candidate", interview_id is required. Optional: force_invite (resend pending invites), mojito_language_code (defaults en), and message_from_recruiter. Each user comes back with a result such as Invited, Activated, Skipped, or Error: ….

Next steps

Review results

Track who finished and read their scored transcripts.

Pre-screen candidates

Score résumés before spending interview credits.