PreHireBadge
Contact

Send a skills test

Send one person or a CSV of test runs, try a quiz yourself, and see when a real send waits for a review.

Updated 2 of 6 in Skills

Who it is for. An owner, admin, or hiring manager sending a quiz.

  1. Open Skills, then Tests, and choose Send a test.
  2. Pick the quiz. The panel names how it was reviewed.
  3. Enter a first and last name. Email is optional. Choose the work location. The quiz notice follows that city and state.
  4. Choose Try it yourself, or Send to a candidate when that button is available.

On the list, a library quiz is marked Reviewed or Test runs only. A quiz you wrote is marked Approved or Needs approval. Try it yourself stays with you. You open the link. No email or text goes out, and that attempt is left out of item statistics. Send to a candidate emails the address you entered. Until a person reviews the quiz, Send to a candidate stays off and the reason is on the panel.

Review comes before a real send

A library quiz that is not yet reviewed can be tried, and the send stays unavailable. After review, the badge says Reviewed by a subject-matter expert, or Reviewed by PreHireBadge and that an outside expert has not reviewed it yet. A quiz you wrote stays off for candidates until someone on this account approves the questions and the answer key.

CSV list takes columns firstName, lastName, and an optional email, up to 100 rows. Every row is a test run, and no mail is sent. A column for a Social Security number, a date of birth, or an address is rejected.

A New York City location shows how the quiz is scored and does not decide whether the city's automated employment decision tool rules apply. A location elsewhere in New York does not show that notice. A California location says a fixed answer key scores the quiz, the quiz does not ask medical questions, and who to contact for an accommodation. An Illinois location shows that artificial intelligence drafted the content and a person reviewed it, when that is how the quiz was made. The model does not score the answers. That Illinois sentence is not a statutory sign-off.

Developers create an invite with POST /api/v1/skills (skills:write). The body has testId, firstName, and lastName. Optional workState, workCity, and testRun choose the notice and whether the invite is a test run. A test key always creates a test run. A live key creates a real invite unless testRun is true. A real send of an unreviewed quiz is refused. GET /api/v1/skills/tests lists reviewed quizzes without the questions. The response has the link. It does not include answers. POST /api/v1/skills/invites creates an invite the same way, with test or testId. A real send emits skills_test.sent. The MCP tools list_skills_tests and send_skills_test use the same scopes and leave out the answer key. See the API overview and what the person sees.

Was this article helpful?

Related articles