Skip to main content
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 or a hosted enrollment session.

Which way to onboard a person

For the first two, see Verifying an Identity.

Add the individual

See the API reference.

Attestations

Each attestation names a check you ran. It needs the values it covers in the same request: 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} returns it:
  • individual_ref: use it to mint a credential.
  • reference_id: the one you sent.
  • active_keys and available_disclosure_paths.
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

Next: Mint a credential with the individual_ref.