# Create a pre-adverse action

Sends a pre-adverse action notification to the subject identified by `check_id`,
giving them the opportunity to dispute the results of their background check before
a final decision is made regarding their eligibility. This ensures compliance and
fairness in the decision-making process.
This step is optional but must precede a final adverse action if used. Cannot be
submitted after an adverse action has already been taken for this check.

Endpoint: POST /regulated/pre_adverse_actions
Version: 1.0
Security: get-bearer-token-using-oauth2

## Request fields (application/json):

  - `check_id` (string, required)
    A universally unique identifier (UUID) in standard format.
    Example: 2b8313e8-4efd-45a1-b578-952b8313e890

  - `email` (string, required)
    An email address.
    Example: john.doe@example.com

  - `suppress_notice` (boolean)
    When `true`, the notice email is not sent to the subject. The `candidate_report_url`
is still populated in the response. Defaults to `false`.

  - `disqualifying_records` (array)
    The criminal records that triggered the adverse decision. Optional but recommended.

  - `disqualifying_records.record_id` (string, required)
    The ID of the criminal record within a check result.
    Example: record-7480fc7edac1a09867849999f2a2f6eec3cc37150f4ba65cbd1f46a4a1a5c15e

## Response 201 fields (application/json):

  - `id` (string)
    A universally unique identifier (UUID) in standard format.
    Example: 2b8313e8-4efd-45a1-b578-952b8313e890

  - `status` (string)
    The status associated with the pre-adverse action.
    Example: AdverseActionInitiated

  - `candidate_report_url` (string | null)
    Subject-facing URL for viewing the background check report and responding to the notice.
When a subject UI is configured this is a deep link keyed by the pre-adverse action id,
gated by a one-time code sent to the subject's email so the customer cannot open it
directly; you may still share it with the subject, and Checkr emails it to them unless
`suppress_notice` is set. Where no subject UI is configured, this is a support `mailto:`
link instead (no OTP gating).
    Example: https://subjects.checkrtrust.com/2b8313e8-4efd-45a1-b578-952b8313e890/review

  - `disqualifying_records` (array)

  - `disqualifying_records.record_id` (string, required)
    The ID of the criminal record within a check result.
    Example: record-7480fc7edac1a09867849999f2a2f6eec3cc37150f4ba65cbd1f46a4a1a5c15e

  - `created_at` (string)
    An ISO 8601 formatted date-time string.
    Example: 2020-01-01T00:00:00Z

  - `sent_at` (string | null)
    Timestamp when the notice was delivered. Null until status is `sent`.
    Example: 2024-06-01T14:00:00Z

## Response 400 fields (application/json):

  - `code` (string, required)
    A machine-readable error code.
    Example: invalid_request

  - `title` (string, required)
    A human-readable error title.
    Example: Invalid Request

  - `source` (object)
    An object containing references to the source of the error.

  - `source.pointer` (string)
    A JSON Pointer [RFC6901] to the associated entity in the request document.
    Example: /data/attributes/first_name

## Response 401 fields (application/json):

  - `code` (string, required)
    A machine-readable error code.
    Example: invalid_request

  - `title` (string, required)
    A human-readable error title.
    Example: Invalid Request

  - `source` (object)
    An object containing references to the source of the error.

  - `source.pointer` (string)
    A JSON Pointer [RFC6901] to the associated entity in the request document.
    Example: /data/attributes/first_name

## Response 403 fields (application/json):

  - `code` (string, required)
    A machine-readable error code.
    Example: invalid_request

  - `title` (string, required)
    A human-readable error title.
    Example: Invalid Request

  - `source` (object)
    An object containing references to the source of the error.

  - `source.pointer` (string)
    A JSON Pointer [RFC6901] to the associated entity in the request document.
    Example: /data/attributes/first_name

## Response 409 fields (application/json):

  - `code` (string, required)
    A machine-readable error code.
    Example: invalid_request

  - `title` (string, required)
    A human-readable error title.
    Example: Invalid Request

  - `source` (object)
    An object containing references to the source of the error.

  - `source.pointer` (string)
    A JSON Pointer [RFC6901] to the associated entity in the request document.
    Example: /data/attributes/first_name

## Response 500 fields (application/json):

  - `code` (string, required)
    A machine-readable error code.
    Example: invalid_request

  - `title` (string, required)
    A human-readable error title.
    Example: Invalid Request

  - `source` (object)
    An object containing references to the source of the error.

  - `source.pointer` (string)
    A JSON Pointer [RFC6901] to the associated entity in the request document.
    Example: /data/attributes/first_name