---
title: Bolivia National ID Verification
slug: us-apis/bolivia-national-id-verification
createdAt: 2024-04-12T04:01:54.142Z
---

# Overview and Purpose

## Overview

The **Bolivia National ID Verification API** enables businesses to verify the identity of individuals in Bolivia using official government-issued **Cédula de Identidad (CI)** records. The API securely validates the provided identity information by cross-checking it against authoritative government data sources.

It is designed to help organizations streamline customer onboarding, minimize identity fraud, and meet regulatory compliance requirements while operating in the Bolivian market. By integrating this API, businesses can perform reliable identity verification without requiring direct integrations with local Bolivian verification providers.

This service is particularly valuable for industries that require robust identity verification processes, including fintech, banking, insurance, HR platforms, gaming, and cryptocurrency businesses.

## Key Features and Functionalities

### Identity Verification

The API validates a citizen's **Cédula de Identidad (CI)** number and **date of birth** against official government records to confirm the identity of Bolivian individuals during onboarding, KYC, and customer verification workflows.

### Verified Identity Information

Upon successful verification, the API returns verified identity attributes such as **first name**, **last name**, **full name**, and **date of birth**, enabling businesses to confidently verify customer identities using trusted government records.

### Fraud Prevention and Identity Protection

By validating identity information against authoritative government databases, the API helps mitigate risks associated with identity fraud, impersonation, and fraudulent account creation, ensuring that only legitimate users can access services.

# API Details

## Sample cURL

:::CodeblockTabs
PreProduction

```json
curl --location 'https://api-preproduction.signzy.app/api/v3/bolivia-ci-verification' \
--header 'Authorization: <kong_auth>' \
--header 'Content-Type: application/json' \
--data '{
    "documentNumber": "<document_number>",
    "dob": "<date_of_birth>"
}'
```

Production

```json
curl --location 'https://api.signzy.app/api/v3/colombia-cc-verification' \
--header 'Content-Type: application/json' \
--header 'Authorization: ' \
--data '{
  "documentNumber": "123456",
  "issueDate": "2020-10-10"
}'
```
:::

## Request Body Parameters



| Parameter      | Type   | Description                                                                                                                                             | Required |
| -------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| documentNumber | String | Bolivian CI (Cédula de Identidad) number.<br />5–10 characters.<br />Alphanumeric only (letters & numbers, no special characters).<br />Cannot be empty | Yes      |
| dob            | String | Date of birth of the CI holder.<br />Format YYYY-MM-DD.<br />Must be a valid calendar date.                                                             | Yes      |

## Response'

:::CodeblockTabs
Verified - Record Found

```json
{
    "result": {
        "documentNumber": "1234567",
        "firstName": "JUAN",
        "lastName": "PEREZ",
        "fullName": "JUAN PEREZ GARCIA",
        "dob": "1990-05-15"
    },
    "reason": "Request Successful",
    "code": "S001"
}
```

Record Not Found

```json
{
    "result": {},
    "reason": "Data not Found",
    "code": "S003"
}
```
:::

## Response Body Parameters

**Top-Level Fields**

| Field  | Type   | Description                                                                                 |
| ------ | ------ | ------------------------------------------------------------------------------------------- |
| result | Object | Container for the verified identity details.<br />Empty object \{} when no record is found. |
| reason | String | High-level status message for the outcome.                                                  |
| code   | String | Signzy response code (S001 = success, S003 = data not found).                               |

**Result Details (present on S001)**

| Field          | Type   | Description                                                      |
| -------------- | ------ | ---------------------------------------------------------------- |
| documentNumber | String | The verified CI number.                                          |
| firstName      | String | Registered first (given) name.<br />Empty string if unavailable. |
| lastName       | String | Registered last (family) name.<br />Empty string if unavailable. |
| fullName       | String | Full registered name.<br />Empty string if unavailable.          |
| dob            | String | Registered date of birth, normalized to YYYY-MM-DD.              |

## Error Code and Mapping

| Scenario                                                        | HTTP | code | reason                               |
| --------------------------------------------------------------- | ---- | ---- | ------------------------------------ |
| Request successful (record found)                               | 200  | S001 | Request Successful                   |
| No matching record / no usable data / record not found          | 200  | S003 | Data not Found                       |
| Field validation failed (missing/invalid documentNumber or dob) | 400  | E002 | *validation message* (see below)     |
| Upstream failure                                                | 409  | E401 | Error in fetching data from Upstream |

### Sample Error

:::CodeblockTabs
Validation error 400 (E002)

```json
{
    "result": {},
    "reason": "documentNumber must be at least 5 character",
    "code": "E002"
}
```

Upstream error 409 (E401)

```json
{
    "result": {},
    "reason": "Error in fetching data from Upstream",
    "code": "E401"
}
```
:::

### Error Response Parameters

| Parameter | Description                                                                                                  |
| --------- | ------------------------------------------------------------------------------------------------------------ |
| result    | Always an empty object \{} for error responses, as no verification data is available when the request fails. |
| reason    | Description of why the request failed (validation detail or upstream error message).                         |
| code      | Standardized Signzy code identifying the failure category.                                                   |

:::hint{type="info"}
### Getting help

Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.

You can reach out to us at [help@signzy.com](#). We strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively.

We value your feedback and are committed to making your experience smooth and enjoyable. Our team is dedicated to assisting you with any needs you may have. Thank you for choosing our services. We look forward to helping you!
:::



