---
title: Attribute catalog
description: The public catalog of document types Human Plugin accepts in credential.type — its format, how Human Plugin loads it and why startup fails when it cannot.
canonical: https://developer.unico.io/human-plugin/additional-resources/attribute-catalog
locale: en
generated_by: markdown-export
---

# Attribute catalog

The list of document types accepted in credential.type.

The catalog is a public JSON file published by Unico at `https://human-token-assets.unico.app/attribute-catalog.json`. Check it for the codes you can use.

```json
{
  "schema_version": 1,
  "version": "2026-10-29.1",
  "attributes": [
    { "code": "DUI_TYPE_BR_CPF", "country_code": "BRA" },
    { "code": "DUI_TYPE_NG_BVN", "country_code": "NGA" }
  ]
}
```

- `code` is what you send in `credential.type`. Matching is **exact and case-sensitive**.
- `country_code` is the ISO 3166-1 alpha-3 country that issues the document. Human Plugin answers it as `countryCode` in `data.ndocs`.

## How Human Plugin uses it

- Downloaded **once at startup** and kept in memory. A new catalog reaches Human Plugin on its next restart.
- Human Plugin does **not start** if it cannot download a valid catalog within 10 seconds. Allow outbound HTTPS to `human-token-assets.unico.app`.
- No client data is sent to the catalog host.
- A create with a `credential.type` outside the catalog is refused with `422 ATTRIBUTE_TYPE_NOT_SUPPORTED`, before anything is stored or sent.