orderData array of objects with the following properties:
The types of order data to include depend on the services that are being ordered. At a minimum, the candidate’s government ID, date of birth, and current address need to be included as order data for a case:
Case order data types
Case order data structures
Below are details and examples of each type of order data.Government ID
The candidate’s government ID is always required in order data.metadata properties: govtId (string) — The candidate’s Social Security number in the format xxx-xx-xxxx. For testing purposes, use 111-22-3333.
Date of birth
The candidate’s birthdate is always required in order data.metadata properties: dob (string) — The candidate’s birthdate in the format yyyy-mm-dd.
Current candidate address
The candidate’s current address is always required in order data.metadata properties: address1, address2, city, state (two-letter abbreviation), postalCode, country (two-letter abbreviation).
Health screening scheduling address
If an occupational health or drug screening is being ordered, you must provide an address that can be used for finding nearby clinics to fulfill the screening.All OHS and drug screening services share the same
serviceCategoryId (service-cat-ohs). If you’re running logic to determine if you need to include the codt-ohs-scheduling-address order data, you should use the serviceCategoryId in your conditional logic.Education
If Education Verification is being ordered, you must provide at least one education order data item.Employment
If an employment verification service is being ordered, you must provide at least one employment order data item.metadata properties: employer, position, city, state, country, monthBegin, yearBegin, current (boolean), monthEnd, yearEnd, contact.website, contact.email, contact.phone, okToContact (boolean), staffingAgency (optional, max 100 characters).
Motor vehicle record
If a Motor Vehicle Report is being ordered, you must provide at least one MVR order data item.Aliases
Alias order data is never required. This data is optional if you’re ordering one of the services that support aliases:
When providing alias order data, you must do the following:
- Include a master list of aliases for the candidate — one
codt-aliasitem for each alias. - Include one
codt-aliasitem for each service that you want verified using the alias.serviceIdmust be specified for these items.
Jurisdictions
Jurisdiction order data is never required. This data is optional if you’re ordering one of the jurisdiction-based services:The results of an SSN Trace will inform which jurisdictions to be searched. As a result, the final list of jurisdictions might be larger than the list that is provided as order data.
- Provide one or more addresses to derive the list of specific jurisdictions:
- If
autoProcessJurisdictionsis set to false (or omitted), specify the jurisdictions for each relevant search type:
POST /jurisdiction/find/all endpoint to help populate the specific jurisdiction order data. Setting autoProcessJurisdictions to true skips the need to specify individual jurisdiction items.
Professional license and certification
If a Professional License and Certification verification (CPLC) is being ordered, you must provide at least one CPLC order data item.
To get the required fields for a specific license or certification:
- Send a GET request to
GET /service/cplc/listto retrieve all supported CPLCs and get thecplcId. - Send a GET request to
GET /service/cplc/id/{cplcId}to retrieve the required fields for thatcplcId.
Shipments
If a shipment service is being ordered, you must provide at least one shipment order data item regardless of PII flow. If you don’t include the order data when creating a case, the service will be excluded from the case order.
To get the masks available for shipment:
- Send a GET request to
GET /shipment/mask/listto retrieve a list of masks. - In the returned
listarray, get theskufor a specific mask.
Only masks with
inStock as true can be ordered. Attempting to order an out-of-stock mask results in a 422 response.Drug reason for test
If a DOT drug screening is being ordered, you can optionally provide a reason for test. If omitted, the default value ofpre-employment is used.
Supported
reasonForTest values:
Drug testing authority
If a DOT drug screening is being ordered, you can optionally provide the regulatory authority under which the test is being conducted. If omitted, the default value offmcsa is used.
Supported
testingAuthority values:
Document Processing
If document processing is being ordered, you must provide onecodt-idp order data item per document to be processed. If you don’t provide order data for a document, it will not be included in the processing order.
metadata properties: