Checkr International Motor Vehicle Report API

openapi: 3.2.0
info:
  version: v1
  title: Checkr.com API Docs International Motor Vehicle Report API
  license:
    name: Proprietary
    url: https://www.checkr.com
  contact:
    name: Checkr
    email: clients@checkr.com
    url: https://checkr.com
  description: '# Introduction


    Checkr is a modern, RESTful API-driven background screening service. The Checkr API uses resource-oriented URLs, supports HTTPS authentication and HTTPS verbs, and leverages JSON in all responses passed back to customers. Checkr is used by over 10,000 customers in a wide variety of industries, and supports a range of screening products and candidate workflows. For a full list of our screenings, please see the Checkr Screenings section below or read the Checkr Help Center articles on Screening Types. This Programming Guide is designed to help customers get up-and-running with Checkr''s background screening services, both by providing the necessary context to understand the background screening industry and its regulations, and by giving technical guidance on how to work with the Checkr API. **Note:** The cURL command is used for all examples in the Checkr API documentation. ### Other resources


    For information about using the Checkr Dashboard, and compliance and regulatory aspects of background checks, visit the Checkr Help Center. For a more targeted set of Checkr Dashboard learning paths for talent sourcing roles like Recruiters, Adjudicators, or Program Administrators, please see the Checkr Learning Center. ## Understand the screening process


    Checkr follows a standardized screening process:


    1. Customer requests a background check. 2. Candidate is presented with and signs the necessary disclosures and authorizations, and submits the requested Personally Identifiable Information (PII). - With the Checkr-Hosted Apply Flow, the candidate signs disclosures and authorizations and enters their own PII. - With a custom self-hosted flow, the Checkr customer collects the required authorizations, and passes Checkr candidate PII using the Checkr API. 3. Checkr conducts an SSN Trace, and collects associated addresses. 4. Checkr runs searches or verifications based on the screening Packages requested. 5. Checkr applies appropriate compliance filters based on the customer’s settings and candidate’s provided residence to determine which records to show, and returns a finalized report to the customer. 6. If there is a record on the report, the customer Engages or Adverse Actions the Candidate, based on an individualized assessment of the candidate''s report. ### 1. Request a background check


    To initiate a background check, a customer provides Checkr their candidate''s email address (for a Checkr-Hosted Apply Flow) or the candidate''s PII (for a self-hosted flow). For more information on ways to achieve this, please see Designing your workflow. ### 2. Candidate signs disclosures and authorizations


    Under the U.S. Fair Credit Reporting Act (FCRA), customers are obligated to collect consent from their candidates when running background checks through Checkr or any other Consumer Reporting Agency (CRA). The Checkr-Hosted Apply Flow presents candidates with fields in which the requested PII may be entered, and collects candidate information on behalf of the customer. Checkr will also present disclosures and authorizations to the candidate, and enable eSignature to capture consent, on behalf of customers using this flow with the Checkr Dashboard or email invitation flow. Custom self-hosted flows collect candidate PII, and pass the information to Checkr using the Checkr API. Customers creating a self-hosted flow will receive guidance from the Checkr team on setting up a similar process as required. ### 3. Checkr runs an SSN Trace


    Checkr runs an SSN Trace to match the candidate’s provided PII with existing credit header data mapped to the SSN. This process yields a list of names and addresses associated with the entered SSN, which can be used to supplement the background check process. At this point Checkr also conducts some initial data comparisons to check that critical pieces of information, like a candidate''s submitted Date of Birth (DOB) and SSN, align with information held on file by the credit bureaus.'
servers:
- url: https://api.checkr.com/v1
  description: Main server
tags:
- name: International Motor Vehicle Report
  description: 'Checks the validity of a driver license and where available, may include a detailed history of the candidate’s driving violations or license conditions. Canada only at this time.

    Refer to International Screenings for more details.'
paths:
  /international_motor_vehicle_reports/{id}:
    parameters:
    - name: id
      in: path
      description: ID of the International Motor Vehicle Report to retrieve.
      required: true
      schema:
        type: string
    get:
      tags:
      - International Motor Vehicle Report
      summary: Retrieve an existing International Motor Vehicle Report
      description: Returns an existing International Motor Vehicle Report with the input ID.
      operationId: getInternationalMotorVehicleReport
      security:
      - basic_auth: []
      responses:
        '200':
          $ref: '#/components/responses/InternationalMotorVehicleReport'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
      x-codeSamples:
      - lang: curl
        source: "$ curl -X GET https://api.checkr.com/v1/international_motor_vehicle_reports/41007cffefb435cf7d701f75d8b86d \\\n    -u 83ebeabdec09f6670863766f792ead24d61fe3f9:\n"
components:
  schemas:
    LicenseInfo:
      type: object
      properties:
        license_number:
          type: string
          description: Candidate’s driver license number; Format varies by subdivision (i.e. province)
          example: ABC12345
        country:
          type: string
          description: Candidate’s driver license country of issue. **Format:** ISO 3166-2 2 letter alpha2 country code. **Example:** `CA`
          example: CA
        subdivision:
          type: string
          description: Candidate's driver license subdivision of issue country. **Format:** ISO 3166-2 subdivision code. **Example:** `CA-AB`
          example: CA-AB
        license_class:
          type: string
          description: Candidate’s driver license class
          example: G1
        expiration_date:
          type: string
          description: Candidate’s driver license expiration date. **Date format:** "YYYY-MM-DD”
          format: date
          example: 2030-01-01 00:00:00+00:00
        is_current:
          type: boolean
          description: Boolean that represents if it is the candidate’s current driver license
          example: true
    ResourceURI:
      type: string
      description: URI of the resource.
      readOnly: true
    LicenseReport:
      type: object
      properties:
        license_status:
          type: string
          description: Final result of the search
          example: VALID
        actual_license_class:
          type: string
          description: The actual, verified license class this driver is eligible for. **Example:** G, G1, G2
          example: 1
        is_valid_license_class:
          type: boolean
          description: Boolean check to confirm if the License Classes match
          example: true
        license_infos:
          type: array
          description: Array of LicenseInfo objects
          items:
            $ref: '#/components/schemas/LicenseInfo'
        violations:
          type: array
          description: 'Array of Violation objects.


            **Note:** The violations, if any, will show up only if `include_driver_history` is set to `true`. Otherwise, it will return an empty violation array.

            '
          items:
            $ref: '#/components/schemas/Violation'
    ScreeningsGenericPayloadInternational:
      type: object
      properties:
        id:
          $ref: '#/components/schemas/ResourceId'
          example: 41007cffefb435cf7d701f75d8b86f
        object:
          type: string
        uri:
          allOf:
          - $ref: '#/components/schemas/ResourceURI'
        status:
          type: string
          description: 'Status of the screening.

            '
          enum:
          - pending
          - complete
          - canceled
          - suspended
          example: complete
        result:
          type:
          - string
          - 'null'
          description: Result of the screening.
          enum:
          - clear
          - consider
          example: clear
        created_at:
          type: string
          description: Time at which the screening was created.
          format: date-time
          example: '2014-01-18T12:34:00Z'
        completed_at:
          type: string
          description: Time at which the screening was completed.
          format: date-time
          example: '2014-01-18T12:35:30Z'
        turnaround_time:
          type: integer
          example: 90
          description: Number of seconds the screening took to complete, calculated from `created_at` to `completed_at`.
        cancellation_reason:
          type: string
          description: See [cancellation reasons](#section/Reference/Cancellation-Reasons) section for possible values.
          example: complete_now_customer_requested
        cancellation_reason_description:
          type: string
          description: See [cancellation reasons](#section/Reference/Cancellation-Reasons) section for possible values.
          example: Customer requested Complete Now prior to screening completion
    Violation:
      type: object
      properties:
        issued_date:
          type: string
          description: Violation issuance date. <b>Date format:</b> "YYYY-MM-DD”
          format: date
          example: 2050-01-01 00:00:00+00:00
        description:
          type: string
          description: Description of the violation
          example: HIT AND RUN
    ForbiddenError:
      type: object
      properties:
        error:
          type: string
          example: You do not have permission to access the requested resource
    ResourceId:
      type: string
      example: e44aa283528e6fde7d542194
      readOnly: true
      description: ID of the resource.
    UnauthorizedError:
      type: object
      properties:
        error:
          type: string
          example: Bad authentication error
    InternationalMotorVehicleReport:
      allOf:
      - $ref: '#/components/schemas/ScreeningsGenericPayloadInternational'
      - type: object
        properties:
          id:
            example: 41007cffefb435cf7d701f75d8b86d
          object:
            enum:
            - international_motor_vehicle_report
          uri:
            example: /v1/international_motor_vehicle_reports/41007cffefb435cf7d701f75d8b86d
          country:
            type: string
            description: ISO 3166-2 country code of the jurisdiction where the search was run
            example: CA
          pdf_url:
            type: string
            description: URL to PDF document containing screening result details
            example: https://eu-west-1-checkr-staging.s3.eu-west-1.amazonaws.com/document.pdf
          license_reports:
            type: array
            description: Array of LicenseReport objects
            items:
              allOf:
              - $ref: '#/components/schemas/LicenseReport'
  responses:
    ForbiddenError:
      description: Forbidden
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ForbiddenError'
    InternationalMotorVehicleReport:
      description: International Motor Vehicle Report details
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/InternationalMotorVehicleReport'
    UnauthorizedError:
      description: Unauthorized
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/UnauthorizedError'
  securitySchemes:
    basic_auth:
      type: http
      scheme: basic
x-tagGroups:
- name: Resources
  tags:
  - Account
  - Users
  - Hierarchy (Enabled by request)
  - Nodes
  - Candidates
  - Reports
  - Packages
  - Invitations
  - Geos
  - Programs
  - Assessments
  - Subscriptions
  - Continuous Checks
  - Adverse Actions
  - Adverse Items
  - Verifications
  - Documents
  - Driver Licenses
  - Professional Licenses
  - Schools
  - Employers
  - Counties
  - Report Tags
  - Report Addresses
  - Report ETA
  - Candidate Stories
  - SSN
  - Webhooks
  - Candidate Postal Address
- name: Screenings
  tags:
  - SSN Trace
  - Sex Offender Registry Search
  - Global Watchlist Search
  - National Criminal Search
  - Federal Criminal Search
  - Federal District Criminal Search
  - Federal Civil Search
  - Federal District Civil Search
  - County Criminal Search
  - State Criminal Search
  - Motor Vehicle Report
  - Drug & Alcohol Clearinghouse Search
  - Education Verification
  - Employment Verification
  - Personal Reference Verification
  - Professional Reference Verification
  - Professional License Verification
  - International Adverse Media Search
  - International Criminal Search
  - International Education Verification
  - International Employment Verification
  - International Global Watchlist Search
  - International Identity Document Validation
  - International Motor Vehicle Report
  - FACIS Search
- name: Form I-9
  tags:
  - Getting Started
  - Forms I-9
  - Worksites
x-provenance:
  method: harvested
  publisher: Checkr
  source: https://api.redocly.com/registry/bundle/checkr/Checkr%20Public%20API/v1/openapi.yaml
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)