# Retrieve a KYC acceptance summary report

Retrieves a Know Your Customer (KYC) acceptance summary report.

Endpoint: GET /experimental/reports/kyc-acceptance-summary
Version: latest
Security: SecretApiKey, JWT

## Query parameters:

  - `periodStart` (string, required)
    Date and time when the report starts.

  - `periodEnd` (string, required)
    Date and time when the report ends.

## Response 200 fields (application/json):

  - `data` (array)
    KYC acceptance data.

  - `data.documentType` (string)
    Type of KYC document.
    Enum: "identity-proof", "address-proof", "funds-proof", "purchase-proof", "credit-file-proof"

  - `data.statusStatistics` (object)
    Statistics for each status.

  - `data.statusStatistics.accepted` (object)
    Statistics for the  status.

  - `data.statusStatistics.accepted.total` (integer)
    Total amount of accepted documents.
    Example: 6

  - `data.statusStatistics.accepted.automatically` (integer)
    Amount of documents that have been accepted automatically.
    Example: 4

  - `data.statusStatistics.accepted.manually` (integer)
    Amount of documents that have been accepted by reviewer.
    Example: 2

  - `data.statusStatistics.accepted.afterAutoRejected` (integer)
    Amount of documents that have been rejected automatically and then accepted by reviewer.
    Example: 2

  - `data.statusStatistics.rejected` (object)
    Statistics for the  status.

  - `data.statusStatistics.rejected.total` (integer)
    Total amount of rejected documents.
    Example: 2

  - `data.statusStatistics.rejected.automatically` (integer)
    Amount of documents that have been rejected automatically.
    Example: 1

  - `data.statusStatistics.rejected.manually` (integer)
    Amount of documents that have been rejected by reviewer.
    Example: 1

  - `data.statusStatistics.rejected.afterAutoAccepted` (integer)
    Amount of documents that have been accepted automatically and then rejected by reviewer.
    Example: 1

  - `data.statusStatistics.pending` (object)
    Statistics for the  status.

  - `data.statusStatistics.pending.total` (integer)
    Total amount of pending documents.

  - `data.statusStatistics.archived` (object)
    Statistics for the  status.

  - `data.statusStatistics.archived.total` (integer)
    Total amount of archived documents.

  - `data.total` (integer)
    Total amount of documents.
    Example: 8

  - `data.accuracyRate` (number)
    Percentage of automatically accepted and rejected documents that remain in the same status after review.
Calculated based on the following: .
    Example: 62.5

  - `data.acceptanceRate` (number)
    Percentage of accepted documents from the total number of KYC documents.
Calculated based on the following: .
    Example: 75

  - `data.manualReviewTime` (number)
    Median duration in minutes between review and created time for manually reviewed documents.

## Response 401 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.

## Response 403 fields (application/json):

  - `status` (integer)
    HTTP status code.

  - `type` (string)
    Problem type in the form of a [URI](https://tools.ietf.org/html/rfc3986) reference.
It should provide human-readable documentation for the problem type.
When this member is not present, its value is assumed to be "about:blank".

  - `title` (string)
    Short, human-readable summary of the problem type.
Other than for the purposes of localization, this should not change from occurrence to occurrence of the problem.

  - `detail` (string)
    Human-readable explanation that is specific to this occurrence of the problem.

  - `instance` (string)
    URI reference that identifies the specific occurrence of the problem.
It may or may not yield further information if dereferenced.