Skip to main content
Test education verification in sandbox by choosing which student record comes back. The last four digits of the applicant’s SSN select the scenario, so you can cover completed degrees, current enrollment, past enrollment, and empty records without waiting on a real school.
Education verification takes no login credentials. The applicant is matched on identity, so what you set on the user decides the report — the SSN, or the date of birth when you have no SSN to send.

Quick start

Create an education order for an applicant whose SSN ends in the scenario’s four digits. Either route works. In the Dashboard — go to Activity > Orders and click Create Order. Enter a nine-digit SSN whose last four digits are the scenario you want, so 666-09-9916 selects 9916, then pick Education as the product. See Create an order for the full walkthrough. Through the API — call Create Order:
Open the share_url from the response to run the flow and pick a school. To switch scenarios, order again with a different SSN.
To select a scenario by date of birth instead, create the user first and place the order against it. The order request has no date_of_birth field, so it is the one identifier you cannot set this way.
The student’s name in the report always comes from the applicant — the scenario supplies the schools, degrees, and enrollment history.

How a scenario is selected

Truv compares the last four digits of the SSN against each scenario and serves the first match. The default covers an applicant you have no SSN for: Truv stamps that scenario’s digits on them so the order returns a record instead of nothing. Which scenario is the default is set per environment, so confirm it before relying on the value above. The same SSN returns the same record every time. Refreshing a verification moves the term dates forward on a few scenarios, but never changes the enrollment status it reports. The school comes from the education provider the applicant picks, so you never pass a school code yourself.
To reach these scenarios under a production API key, select the Truv College (Sandbox) provider (truv_college). It is flagged as a sandbox provider, so any order against it is served the records below with no call to the Clearinghouse.

Completed degrees, no enrollment

A former student. The Clearinghouse confirms the degree but reports no enrollment, so nothing is currently in progress. Use these to check how your integration renders a graduate. Every degree here comes back confirmed and graduated, with an award date. Degree records carry no school name, major, or honors.

Current enrollment

This is the only scenario that returns a current enrollment, and the only one where a self-certification requirement based on full-time study is met.
The Clearinghouse answers with every enrollment it holds for a student, not only the school you ordered against. 9916 returns two schools from one order, so expect a report to describe more than one institution.

Past enrollment

Enrollment the school has confirmed and closed. The enrollment type is what the school reported for the most recent term, which is what a community-engagement or full-time-study requirement is judged on.

Empty and unconfirmed records

All six finish the order with no data, for two different reasons. Use them to check that your integration handles a verification that returns nothing. See Task lifecycle for how a no-data outcome surfaces and how to handle it.

Enrollment type

The Clearinghouse reports how heavily a student was enrolled for each term, not a credit-hour count. Truv returns it as enrollment_type on the enrollment, taken from the most recent term. An enrollment type the school withheld is not the same as a student below the bar. Scenarios 9914, 9916 and 9921 each return a withheld enrollment type so you can tell the two apart in your own logic.