Checkr Professional Licenses API

openapi: 3.2.0
info:
  version: v1
  title: Checkr.com API Docs Professional Licenses 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: Professional Licenses
  description: The professional license resource represents a single certification or license issued to a candidate for qualification in a professional field. Candidates may have two existing professional license resources at a time.
paths:
  /candidates/{candidate_id}/professional_licenses:
    parameters:
    - name: candidate_id
      in: path
      description: The Candidate's ID
      required: true
      schema:
        type: string
    post:
      tags:
      - Professional Licenses
      summary: Create a new Professional License
      description: Creates a new Professional License for a given candidate. A maximum of two licenses may exist for each candidate. When a report is run with Professional License Verification, all candidate licenses existing at the time of report creation will be included for verification.
      operationId: createProfessionalLicense
      security:
      - basic_auth: []
      requestBody:
        $ref: '#/components/requestBodies/ProfessionalLicenseCreate'
      responses:
        '200':
          $ref: '#/components/responses/ProfessionalLicenseCreate'
        '400':
          $ref: '#/components/responses/BadProfessionalLicenseCreateRequestError'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '404':
          $ref: '#/components/responses/CandidateNotFoundError'
      x-codeSamples:
      - lang: curl
        source: "$ curl -X POST https://api.checkr.com/v1/candidates/5fb31d36bc2e7f4609aba03d/professional_licenses \\\n     -u 83ebeabdec09f6670863766f792ead24d61fe3f9: \\\n     -d expiration_date=2033-01-30 \\\n     -d issuer_name='Medical Board of California' \\\n     -d issuer_region=CA \\\n     -d license_number=A12345 \\\n     -d license_type=Physician \\\n     -d certification_document_id=4a3e270ccecdd1455d9f4685"
    get:
      tags:
      - Professional Licenses
      summary: List existing Professional Licenses
      description: Returns a list of existing Professional Licenses for the given Candidate ID.
      operationId: listOfProfessionalLicenses
      security:
      - basic_auth: []
      responses:
        '200':
          $ref: '#/components/responses/ProfessionalLicenseList'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '404':
          $ref: '#/components/responses/CandidateNotFoundError'
      x-codeSamples:
      - lang: curl
        source: "$ curl https://api.checkr.com/v1/candidates/5fb31d36bc2e7f4609aba03d/professional_licenses \\\n     -u 83ebeabdec09f6670863766f792ead24d61fe3f9:\n"
  /candidates/{candidate_id}/professional_licenses/{license_id}:
    parameters:
    - name: candidate_id
      in: path
      description: The Candidate's ID
      required: true
      schema:
        type: string
    delete:
      parameters:
      - name: license_id
        in: path
        description: The ID of the license to delete.
        required: true
        schema:
          type: string
      tags:
      - Professional Licenses
      summary: Delete an existing Professional License
      description: Deletes an existing Professional License
      operationId: deleteProfessionalLicenses
      security:
      - basic_auth: []
      responses:
        '200':
          $ref: '#/components/responses/ProfessionalLicenseDelete'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '404':
          $ref: '#/components/responses/ResourceNotFoundError'
      x-codeSamples:
      - lang: curl
        source: "$ curl -X DELETE https://api.checkr.com/v1/candidates/5fb31d36bc2e7f4609aba03d/professional_licenses/de613d6925a27235fc1b64a6 \\\n     -u 83ebeabdec09f6670863766f792ead24d61fe3f9: \\\n"
components:
  schemas:
    CandidateNotFoundError:
      type: object
      properties:
        error:
          type: string
          example: Candidate not found
    ProfessionalLicense:
      type: object
      properties:
        id:
          $ref: '#/components/schemas/ResourceId'
        expiration_date:
          type: string
          format: date
          description: Expiration date of the professional license
          example: '2033-01-30'
        issuer_name:
          type: string
          description: Name of the organization that issued the professional license
          example: Medical Board of California
        issuer_region:
          type: string
          description: 2-letter abbreviation of US state where license was issued. For licenses not issued for a specific state, use "United States".
          example: CA
        license_type:
          type: string
          description: Category or industry of professional license
          example: Physician
        license_number:
          type: string
          description: Unique identifier assigned to license by issuer. Format may vary
          example: A 12345
    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
    ResourceNotFoundError:
      type: object
      properties:
        error:
          type: string
          example: Resource not found
    BadProfessionalLicenseCreateRequestError:
      type: object
      properties:
        error:
          type: string
          example: license_type is missing
  responses:
    ProfessionalLicenseCreate:
      description: Professional License was successfully created
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ProfessionalLicense'
    ForbiddenError:
      description: Forbidden
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ForbiddenError'
    ProfessionalLicenseDelete:
      description: Professional License was successfully deleted
      content:
        application/json:
          schema:
            allOf:
            - $ref: '#/components/schemas/ProfessionalLicense'
            - properties:
                deleted_at:
                  type: string
                  format: datetime
                  description: Timestamp of record deletion
                  example: 2023-10-10 01:16:27+00:00
    UnauthorizedError:
      description: Unauthorized
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/UnauthorizedError'
    ResourceNotFoundError:
      description: Not Found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ResourceNotFoundError'
    CandidateNotFoundError:
      description: Not Found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/CandidateNotFoundError'
    ProfessionalLicenseList:
      description: List of existing Professional Licenses for candidate
      content:
        application/json:
          schema:
            properties:
              object:
                type: string
                enum:
                - list
              count:
                type: integer
                example: 1
              data:
                type: array
                items:
                  $ref: '#/components/schemas/ProfessionalLicense'
    BadProfessionalLicenseCreateRequestError:
      description: Bad Request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/BadProfessionalLicenseCreateRequestError'
  requestBodies:
    ProfessionalLicenseCreate:
      content:
        application/json:
          schema:
            allOf:
            - $ref: '#/components/schemas/ProfessionalLicense'
            - type: object
              required:
              - expiration_date
              - issuer_name
              - issuer_region
              - license_type
              - certification_document_id
              properties:
                certification_document_id:
                  type: string
                  description: ID of document previously created with the [uploadDocument](/#operation/uploadDocument) endpoint. Document must be of `type` `professional_license_certification_image` and should contain an image proof of professional license to be verified.
  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)