> For the complete documentation index, see [llms.txt](https://docs.vida.id/identity-stack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vida.id/identity-stack/identity-operation-center/conversion-ops/api-integration.md).

# API Integration

This section provides technical instructions for integrating VIDA Identity Verification with a focus on the VIDA Conversion Ops flow. Manual Review is triggered when an identity check does not meet the automated approval threshold but still qualifies for manual review by VIDA’s verification team. This flow ensures continued user progression without immediate rejection. 

### Authentication

Authenticate API requests using your assigned API key. All requests must include the `Authorization` header using the Bearer schema.

{% hint style="info" %}
For detailed information on VIDA authentication requirements, refer to the documentation [here](https://docs.vida.id/vida-identity-platform/integration-methods/api/authentication)
{% endhint %}

### Perform Identity Verification

Submit a verification request via the identity verification endpoint. Required inputs include:

* Demographic Data (NIK, Name, Date of Birth, etc)
* Live-captured selfie image

The API processes the inputs and verify to Authorative Sources. If the result score falls within the Manual Review threshold, the request is automatically routed for manual review.

{% hint style="info" %}
Go to VIDA Identity Verification API for detailed technical guide and also [mock data ](/identity-stack/identity-operation-center/conversion-ops/mock-data.md)to test VIDA Conversion Ops flow
{% endhint %}

### Check Verification Status

To check  the current status of the verification process, you can use the response from Biometric and Demographic Verification API or Status Check API. Status transitions automatically based on review results without requiring additional input.

{% hint style="info" %}
Please refer to Verification Status page for more[ API implementation guide](broken://pages/X5znaA9snSOof1EQNdsf)
{% endhint %}

In Biometric and Demographic Verification API, If a transaction is routed to Manual Review, the response will include the verification state as `SUBMITTED` . The status will change to `COMPLETED` once the manual review is completed

#### Sample Response on Biometric and Demographic Verification API

#### Submitted - Manual Review

<details>

<summary>JSON Response</summary>

```json
{
    "data": {
        "transactionType": "FULL_FRAUD_ASSESSMENT",
        "transactionId": "82a2b8d8-3078-470a-86a2-a7d54f23ab7f",
        "fraudAssessment": "SUBMITTED",
        "assessmentResults": [
            {
                "name": "full_name",
                "result": 0.6150000000000001
            },
            {
                "name": "dob",
                "result": 1.0
            },
            {
                "name": "nik",
                "result": 1.0
            },
            {
                "name": "selfiePhoto",
                "result": 0.9
            }
        ]
    }
}
```

</details>

#### Approved/Rejected Manual Review

<details>

<summary>JSON Response</summary>

```json
{
    "data": {
        "transactionType": "FULL_FRAUD_ASSESSMENT",
        "transactionId": "82a2b8d8-3078-470a-86a2-a7d54f23ab7f",
        "fraudAssessment": "COMPLETED",
        "assessmentResults": [
            {
                "name": "full_name",
                "result": 0.6150000000000001
            },
            {
                "name": "dob",
                "result": 1.0
            },
            {
                "name": "nik",
                "result": 1.0
            },
            {
                "name": "selfiePhoto",
                "result": 0.9
            }
        ]
    }
}
```

</details>

In [Status Check API](/identity-stack/identity-operation-center/conversion-ops/status-check-api.md), If a transaction is routed to Manual Review, the response will include the status code as `002` . The status will change to `003` (Approved) or `004` (Rejected) once the manual review is completed

#### Sample Response on Status Check API

#### In Progress - Manual Review

<details>

<summary>JSON Response</summary>

```json
{
  "data": {
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": "002"
  }
}
```

</details>

#### Approved Manual Review

<details>

<summary>JSON Response</summary>

```json
{
  "data": {
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": "003"
  }
}
```

</details>

#### Rejected Manual Review

<details>

<summary>JSON Response</summary>

```json
{
  "data": {
    "partnerTrxId": "3282d003-c62c-4b7b-87e4_12112",
    "transactionType": "FULL_FRAUD_ASSESSMENT",
    "transactionId": "3282d003-c62c-4b7b-87e4-9d0a1bbf0c18",
    "status": "004"
  }
}
```

</details>

To understand the definition of each status code, please refer to [Status Check API](/identity-stack/identity-operation-center/conversion-ops/status-check-api.md)

To get the verification data, please refer to [Event Detail API](/identity-stack/identity-operation-center/conversion-ops/event-detail-api.md)

### Webhook Integration

Configure a webhook endpoint to receive asynchronous status updates. When a manual review is completed, the webhook sends a POST payload with the final decision and associated metadata.

To set up Webhooks, you will need to contact the [VIDA support team.](mailto:support@vida.id) and request for it to be enabled. Please reach out to VIDA support team for further assistance.

{% hint style="info" %}
Please go to [VIDA Webhooks page](/identity-stack/identity-operation-center/conversion-ops/webhook-notification.md) for detailed technical integration
{% endhint %}