# Create regulated criminal report

Create a new regulated criminal report with legal annotation.

This endpoint creates an asynchronous criminal report that applies legal rules based on
the provided jurisdiction context. Results include legal annotation checks at the
record, case, and charge levels indicating whether items should be included,
investigated, or removed based on applicable regulations.

A permissible purpose must be provided to comply with Fair Credit Reporting Act (FCRA) requirements.

Important Notes:
- Results are NOT returned in the HTTP response (returns 202 Accepted)
- Full results are delivered asynchronously via webhook once processing is complete

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

## Response 202 fields (application/json):

  - `id` (string)
    A universally unique identifier (UUID) in standard format.

  - `status` (string)
    The current status of the report.
    Enum: "pending", "complete", "failed"

## 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 429 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"