Verified First provides an API that allows access to client data for full or partial integrations with various partner systems. We also provide standard request and response formats that can be used to:
- Place orders and retrieve order information
- Retrieve account information and product information
- Create, modify, or delete packages and users
Verified First provides endpoints for both production and staging/test environments:
Production Environment:
Verified First Production Portal: https://portal.verifiedfirst.com/
Associated API: https://api1.verifiedfirst.com/external/verified-first/
Staging/Test Environment:
Verified First Staging/Test Portal: https://staging.verifiedfirst.com
Associated API: https://api2.verifiedfirst.com/external/verified-first/
All new integrations and API connections must first be implemented and reviewed in the Staging/Test Environment. In order to successfuly implement and review in Staging/Test environment, you must meet the following requirements:
- There must be a user account in both the Verified First Production and Staging Portals
- You must coordinate with the Verified First Integrations team to configure, setup, and activate the formats. You can contact our Integrations Team at integrations@verifiedfirst.com to request a partial or full API integration with the Verified First platform.
- Verified First will need to whitelist external domains and/or IP addresses. Please contact our Integrations Team at integrations@verifiedfirst.com to request additions to our whitelist.
Here are some examples of common API operations and the standard formats utilized by our partners.
Create Order - Used to place an order
Method: | POST |
Endpoints: |
Production: https://api1.verifiedfirst.com/external/verified-first/order |
HTTP Header: |
Content Type: application/json |
HTTP Status Codes: |
Success 200 |
Request Body: |
{
|
Response Body: |
{
|
Note: the field "mvrlicensenumber", "mvrduration", and "mvrstate" can only be added for an instant order and will be proceeded if the selected package contains an MVR product. In addition, the field "urine_test_purpose" can only be added for "app_invitation" orders and will be proceeded if the selected package contains a Drug Screening product.
Get Package List - Retrieve list of defined packages in Verified First
Method: | GET |
Endpoints: |
Production: https://api1.verifiedfirst.com/external/verified-first/package/list |
HTTP Header: |
Content Type: application/json |
HTTP Status Codes: |
Success 200 Error 400, 403, 500 |
Request Body: |
None |
Response Body: |
{ |
POST Back Request
The Verified First API provides a method to send order results to an external platform if the following items are provided from the external system:
- API Endpoint
- Authorization header or credentials to authenticate the message
The data sent from Verified First does not contain any Personally Identifiable Information (PII) and can be stored in external platforms without the worry of inadvertently releasing access to sensitive information.
Example of Standard Verified First Request: |
{ |
Field Definitions:
- partner_applicant_ids - Unique identifier of applicant from external system (received from value(s) defined in "Create Order" API call)
- account_number - Account number assigned by Verified First
- order_id - Internal Verified First order identifier
- order_number - Order number created by Verified First
- flagged - Indicates if the order is flagged (Yes/No)
- package_name - Package name used for the order
- products_ordered - The list of products contained in the selected package for the order
- reference_code - Reference code associated with the order (optional)
- status - The latest status of the order
- Canceled - Order has been canceled by the vendor
- Error - An error was generated when an order for a report was placed
- Waiting on Applicant - Order has been created by the vendor
- Invitation Sent - Invitation has been sent to applicant
- Draft Orders - Verified First Portal user has performed Pre-Pull tasks and has developed jurisdictions for the applicant, but has not completed the order
- Ready to Order - Applicant has finished the invitation and the order is ready for review. Requires Account settings (Gear > Admin > Account > Review Process) to be set to either "Allow Both" or "Manual Order Only"
- File Ordered - Background check file has been ordered
- Partially Complete - At least one selected product has been completed for the file
- Complete - The file has been completed and returned
- Applicant Refused the invitation - this means the applicant has refused to complete the applicant invite
- User withdrew the invite - the applicant invite has been withdrawn
- Applicant invitation expired - the applicant failed to complete the applicant invite within the allotted time
- state - The activation state of the order. Orders that are archived (either manually or by scheduled expiration) move from "Active" state to "Inactive" state. (Active/Inactive)
- adjudication - Adjudication status of the order (this field will only have values populated if "status" is "Complete")
- In Need of Review
- Approved
- Pre-Adverse Action
- Adverse Action
- url - Link to view order
- order_completed_date - Date that the order was completed (will be filled when "status" is "Complete")
- last_status_date - Date of the most up-to-date status
Generate Pre-Signed URL for Upload Attachments
Method: | GET |
Endpoint: |
Production: https://api1.verifiedfirst.com/external/verified-first/signed-url Test: https://api2.verifiedfirst.com/external/verified-first/signed-url |
HTTP Header: |
Content Type: application/json Authorization: Basic *********** -Type: Basic Authorization |
HTTP Status Codes: |
Success 200 Error 400, 403, 500 |
Request Body: |
None |
Request Parameters |
file_name: file.png |
Response Body: |
{ |
Description |
The link will expire after 15 minutes; The file_url field should be used for create order; The upload file should be used for upload file in temporary; Available next file types: pdf, txt, rtf, doc, docx, xls, xlsx, odt, ods, jpg, png, gif, tif, tiff |
Upload Attachments
Method: | GET |
Endpoint: |
The pre-signed URL should be from get pre-signed URL |
HTTP Header: |
Content Type: {The content type of uploading file} |
HTTP Status Codes: |
Success 200 Error 400, 403, 500 |
Request Body: |
{binary of files}
|
Response Body |
|
If you have any further questions, or need a product enabled on your account,
please contact Verified First Client Services for assistance.
Call 844-709-2708 or email ClientServices@VerifiedFirst.com
Comments
0 comments
Article is closed for comments.