> For the complete documentation index, see [llms.txt](https://docs.vcheckglobal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vcheckglobal.com/api-reference/background-check.md).

# Background Check

### What is the BGC API?

The VCheck Background Check (BGC) API lets you submit due-diligence investigations on individuals or on entities (companies) directly from your platform. Each order is processed asynchronously - you receive a structured report and a downloadable PDF when the investigation completes.

### Integration Steps

| Step | Action                                        | Outcome                                                                           |
| ---- | --------------------------------------------- | --------------------------------------------------------------------------------- |
| 1    | Authenticate via OAuth 2.0                    | Bearer token received (valid 1 hour)                                              |
| 2    | List products (GET /backgroundcheck/products) | Valid product codes for your account                                              |
| 3    | Submit order (POST /backgroundcheck/request)  | Order queued, 202 Accepted                                                        |
| 4    | Receive result                                | Webhook event fired or poll GET /backgroundcheck/reference/{reference\_id}/report |

### Scopes

| Scope                                     | Access                                                                           |
| ----------------------------------------- | -------------------------------------------------------------------------------- |
| `api-platform/backgroundcheck-read`       | List products, list subjects, list reports, retrieve reports, get webhook config |
| `api-platform/backgroundcheck-read-write` | All read operations plus submit orders, register/manage webhook                  |

### Finding Levels

Findings in the report are grouped by `risk_level`. The `by_risk_level` and `by_search_level` summary fields use the first three values. Individual findings inside `sections` may also carry `Clear`, indicating the record was found but raised no concern.

| risk\_level     | Where it appears                               | Meaning                                                             |
| --------------- | ---------------------------------------------- | ------------------------------------------------------------------- |
| `High Risk`     | `by_risk_level`, `by_search_level`, `sections` | Active adverse records — tax liens, criminal convictions, sanctions |
| `Moderate Risk` | `by_risk_level`, `by_search_level`, `sections` | Elevated risk indicators — discharged liens, older civil matters    |
| `Informational` | `by_risk_level`, `by_search_level`, `sections` | Records present but not adverse                                     |
| `Clear`         | `sections` only                                | Record found but no adverse finding                                 |

### Changes to an Existing Order

Orders cannot be modified through the API once submitted. Contact VCheck Client Services at <support@vcheckglobal.com> and include the order's `reference_id`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vcheckglobal.com/api-reference/background-check.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.