# Get verifications by date

Get the list of verifications created on a specific date. The list also includes requests to non-doc verification services.
Our system returns verifications in the mode of your API key: a test API key returns test verifications, a live API key returns live verifications.
**Pagination**
The response contains a maximum of 1000 verifications, sorted from newest to oldest. To get the next page, send the request again and increase `offset` by `count`. When the response contains fewer items than `count`, it is the last page.
You can send a maximum of 100 requests per minute with one API key.

Endpoint: GET /verifications/report
Version: 1.0
Security: API-Key

## Security:

  - `API-Key` (unknown)
    apiKey in header API-Key

## Query parameters:

  - `date` (string, required)
    The date when the verifications were created, in the `YYYY-MM-DD` format. Our system uses the UTC time zone.

  - `offset` (integer)
    The number of verifications to skip.

  - `count` (integer)
    The maximum number of verifications in the response.

## Response 200:

  - `200` (unknown)
    **OK**
The request was successful, and our system returned the list of verifications. If there are no verifications for the date, our system returns an empty array.

## Response 200 fields (application/json):

  - `created_at` (string)
    The date and time when the verification was created, in UTC, in the `YYYY-MM-DD HH:MM:SS` format
    Example: 2026-10-01 09:15:42

  - `verification_id` (string | null)
    A unique identifier for a verification, assigned by our system after a verification is created using the “Create a verification" request
    Example: 27c5caea93ee4656881ef9a30fadd21a3768

  - `applicant_id` (string | null)
    The applicant unique identifier. `null` for a request to a non-doc verification service without an applicant.
    Example: 0a1b2c3d4e5f0a1b2c3d4e5f0a1b2c3d4e5f

  - `external_applicant_id` (string | null)
    The applicant identifier in your system
    Example: user-10045

  - `name` (string)
    For a person, the first name and the last name. For a company, the company name. For a `BR_CPF` service request, the CPF number.
    Example: Jane Sample

  - `dob` (string | null)
    The date of birth of the person, in the `DD-MM-YYYY` format
    Example: 15-04-1990

  - `country_code` (string | null)
    For a person, the country of residence. For a company, the country of registration. ISO 3166-1 alpha-2 code.
    Example: GB

  - `tax_id_number` (string | null)
    The number of the `TAX_ID_NUMBER` document
    Example: AB123456C

  - `email` (string | null)
    The email of the person or the company
    Example: jane.sample@example.com

  - `phone` (string | null)
    The phone number of the person or the company
    Example: +440000000000

  - `wallet_address` (string | null)
    The crypto wallet address of the person
    Example: null

  - `telegram_username` (string | null)
    The Telegram username of the person
    Example: null

  - `status` (string)
    The internal status of the verification:
- `PROCESSING` — our system runs the automatic checks
- `PENDING` — the verification waits for a manual review
- `VALID` — the verification is approved
- `INVALID` — the verification is declined
    Example: VALID

  - `service` (string)
    - `KYC` — verification of a person
- `KYB` — verification of a company
- `BR_CPF` — request to the Brazil CPF service
    Enum: "KYC", "KYB", "BR_CPF"

  - `method` (string)
    How the verification was completed:
- `AUTOMATION_CHECK` — by our automatic checks
- `MANUAL_CHECK` — by a manual review
- `UNKNOWN` — the method is not defined: the verification is not completed yet, or it is a request to a non-doc verification service
    Example: AUTOMATION_CHECK

  - `verification_types` (array)
    The verification types of the verification. For a request to a non-doc verification service, contains the service type, for example, `BDB_TURKISH_DOCUMENT`.
    Example: ["PROFILE","DOCUMENT","FACIAL"]

  - `decline_reasons` (array)
    The decline reason codes. See [Decline reasons](/decline-reasons). Empty array if there are no decline reasons.
    Example: []

  - `processing_time` (integer | null)
    The time from the creation of the verification to the final result, in minutes. `null` if the verification is not completed, or if it is a request to a non-doc verification service.
    Example: 3

  - `price` (string)
    The price of the verification, with two decimal places. `"0.00"` for a test verification.
    Example: 1.10

  - `mode` (string)
    The mode of the verification
    Enum: "LIVE", "TEST"

## Response 401:

  - `401` (unknown)
    **Unauthorized**
Authentication credentials are missing or invalid. The request did not include an API token, or the token provided is malformed, expired, or revoked.

## Response 401 fields (application/json):

  - `type` (string)
    Example: unauthorized

  - `errors` (array)

## Response 402:

  - `402` (unknown)
    **Payment Required**
Access to the requested resource is restricted until a payment is successfully processed. Ensure your account has a valid payment method or sufficient funds to complete this action.

## Response 402 fields (application/json):

  - `type` (string)
    Example: insufficient_funds

  - `errors` (array)

## Response 422:

  - `422` (unknown)
    **Unprocessable Content**
Our system understands the request but can’t process it due to invalid query parameters.

## Response 422 fields (application/json):

  - `type` (string)
    Example: validation

  - `errors` (array)

  - `errors.parameter` (string)
    Example: date

  - `errors.message` (string)
    Example: Date is required

## Response 429:

  - `429` (unknown)
    **Too Many Requests**
You sent more than 100 requests in one minute with this API key. Wait the number of seconds in the `Retry-After` header and try again.

## Response 429 fields (application/json):

  - `status` (integer)
    Example: 0

  - `data` (null)
    Example: null

  - `errors` (array)

  - `errors.code` (string)
    Example: rate_limit

  - `errors.message` (string)
    Example: Too many requests. Please try again later.

## Response 429 headers (application/json):

  - `Retry-After` (integer)
    The number of seconds before you can send the request again
    Example: 42

## Response 500:

  - `500` (unknown)
    **Internal Server Error**
This response indicates that our system encountered an unexpected condition that prevented it from fulfilling the request.

## Response 500 fields (application/json):

  - `type` (string)
    Example: internal_server

  - `errors` (array)

## Response 200 examples:

  - `Verifications for the date` (unknown)

  - `No verifications for the date` (unknown)