# Certn API Documentation

> Source: https://centric-api-docs.certn.co/#check-REFERENCE_1

### Reference

**Reference**

**Identifier:** `REFERENCE_1`

A reference check verifies information about an applicant by contacting referees who can provide insight into their character, conduct, or past interactions. This check collects feedback from individuals who know the applicant in a professional, personal, or other relevant capacity. Using contact details provided by the applicant, an analyst reaches out to the referee to confirm key information and gather responses about the individual's relationship with the referee, the duration of that relationship, and relevant observations about the individual's reliability, behaviour, or performance. The results are documented and shared in a report to provide additional context that may support background screening and decision-making processes.

**Ordering methods:** Invite, Quickscreen

### Child Checks

| Check | Description | Via parent only | Docs |
|-------|-------------|------------------|------|
| `PROFESSIONAL_REFERENCE_1` | Professional Reference | No | [Open](https://centric-api-docs.certn.co/#check-PROFESSIONAL_REFERENCE_1) |
| `PERSONAL_REFERENCE_1` | Personal Reference | No | [Open](https://centric-api-docs.certn.co/#check-PERSONAL_REFERENCE_1) |

Full details and **Try it** for each child: [`PROFESSIONAL_REFERENCE_1`](https://centric-api-docs.certn.co/#check-PROFESSIONAL_REFERENCE_1), [`PERSONAL_REFERENCE_1`](https://centric-api-docs.certn.co/#check-PERSONAL_REFERENCE_1)

### Response

**201 Created** — Successfully ordered. Use the returned `id` to retrieve the full case via `GET /api/public/cases/{id}/`.

### Error codes

| Status | Type | Description |
|--------|------|-------------|
| 400 | `validation_error` | Invalid request data |
| 401 | `client_error` | Authentication failed |
| 403 | `client_error` | Permission denied |
| 422 | `validation_error` | Request validation failed (e.g. missing required fields) |