> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baselayer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding an Individual You Verified

> Record a person you verified yourself, so you can issue credentials for them without a Baselayer check.

This page is for platforms that already verify people in their own onboarding and want Baselayer to hold those people as they verified them.

Adding an individual records the person you send, under your own `reference_id`, and gives you an `individual_ref` to mint credentials with. Baselayer runs no check. Each check you say you ran is recorded as `attested`, or as `verified` where Baselayer has already verified the same values.

This is for individuals only. A business is always verified by Baselayer, through a [direct verification](https://docs.baselayer.com/docs/verifying-an-identity.md#path-a-submit-an-identity-you-already-collected) or a [hosted enrollment session](https://docs.baselayer.com/hosted-enrollment/sessions.md).

## Which way to onboard a person

| Way | Who checks the person | Start with |
| - | - | - |
| Hosted enrollment | Baselayer, on its own page | `POST /onboarding/sessions` |
| Direct verification | Baselayer, from details you collected | `POST /issuance/identities/verifications` |
| Add an individual you verified | You | `POST /issuance/identities/individuals` |

For the first two, see [Verifying an Identity](https://docs.baselayer.com/docs/verifying-an-identity.md).

## Add the individual

```http theme={null}
POST /issuance/identities/individuals
```

See the [API reference](https://docs.baselayer.com/api-reference/identities/push-an-individual-you-verified.md).

```json theme={null}
{
  "reference_id": "customer-123",
  "individual": {
    "given_name": "Jordan",
    "family_name": "Lee",
    "birthdate": "1990-04-12",
    "phone_number": "+14155550123",
    "email": "jordan@example.com",
    "address": "123 Main St, San Francisco, CA 94105",
    "national_id": { "type": "us_ssn", "value": "123-45-6789" },
    "attestations": [
      { "key": "phone_possession" },
      { "key": "ssn_identity_match" }
    ]
  }
}
```

| Field | Notes |
| - | - |
| `reference_id` | Your own ID for the person. Required. |
| `individual` | The person as you verified them. Every field is optional, but send at least one of `email`, `phone_number` or `national_id`. |
| `individual.address` | One line. Baselayer normalizes it, and doesn't store an address it can't match to a deliverable one. |
| `individual.national_id` | Typed: `{ "type": "us_ssn", "value": "..." }`. US SSNs only today. |
| `individual.attestations` | The checks you ran on these values. See below. |

### Attestations

Each attestation names a check you ran. It needs the values it covers in the same request:

| `key` | What you checked | Needs |
| - | - | - |
| `phone_possession` | The person controls the phone number. | `phone_number` |
| `email_possession` | The person controls the email address. | `email` |
| `ssn_identity_match` | The SSN belongs to the person. | `given_name`, `family_name`, `national_id` |
| `dob_identity_match` | The date of birth belongs to the person. | `given_name`, `family_name`, `birthdate` |

`watchlist_clear` can't be attested. A request that names the same key twice, or a key without its values, is refused with `422`.

The attestations decide which fields a credential for this person can share. Read them back as `active_keys`, each with its `basis` and `time`, and the fields a mint can share as `available_disclosure_paths`.

## Read the response

The response is the individual, as [`GET /issuance/identities/individuals/{individual_ref}`](https://docs.baselayer.com/api-reference/identities/look-up-an-individual-by-pairwise-reference) returns it:

* `individual_ref`: use it to [mint a credential](https://docs.baselayer.com/docs/minting-credentials.md).
* `reference_id`: the one you sent.
* `active_keys` and `available_disclosure_paths`.

| Status | Meaning |
| - | - |
| `201` | The `reference_id` is new to your application. |
| `200` | You sent this `reference_id` before. The new request replaces what you said about that person. |

A new `reference_id` can still name a person you already hold. The `individual_ref` tells you which person it is.

## Send it again

Send the whole person again under the same `reference_id` to replace what you said before. Each request is recorded as a new record, so `updated_at` moves. There is no `Idempotency-Key`: retrying the same request records the same statement again.

A `reference_id` you sent here, or with a direct verification, names one person. A `reference_id` that a hosted enrollment session carried belongs to the person that session verified.

## Troubleshooting

| Problem | Fix |
| - | - |
| `422` with code `7112` (`validation_failed`) | Check the field each error names. The most common misses are an attestation without the values it covers, and a request with none of `email`, `phone_number` and `national_id`. |
| `409` with code `6202` (`identity_national_id_changed`) | You hold a different `national_id` for this person, under this or another of your references. A national ID on file can't be changed. Check that the `reference_id` is the right person. |
| `409` (`request_conflict`) | Another request for the same person crossed this one. Wait for the `Retry-After` delay, then send it again. |
| `502` | The address service failed and nothing was written. Send it again after the `Retry-After` delay. |
| A mint is refused with `422` code `6333` (`credential_field_not_backed`) | The person doesn't hold the checks behind a field you asked to share. Attest the check, or ask for fewer fields. See [Minting Credentials](https://docs.baselayer.com/docs/minting-credentials.md). |

Next: [Mint a credential](https://docs.baselayer.com/docs/minting-credentials.md) with the `individual_ref`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.