Home > DTI Registry Overview
The DTI Foundation offers a free web portal as part of its commitment as a Registration Authority (RA) under the ISO 24165 standard. This portal provides users with open access to all data elements under the DTI standard, supporting transparency, accessibility, and the wider adoption of standardized digital asset identification.
DTI Foundation offers a free service to download a historical snapshot of the DTI registry in JSON format with the following fields available under a perpetual open license:
The DTI Foundation recognizes that under the open license, data within this file may be freely reproduced, used, transmitted, or built upon by anyone for any purpose, commercial or non-commercial.
While the free web portal is ideal for quick lookups and basic access, the DTI APIs offer far greater functionality for professional and enterprise users. Through direct integration with internal systems, the API enables automated data retrieval, seamless alignment with trading, compliance, and analytics workflows. It reduces manual effort, enhances data accuracy, and supports large-scale operations that require reliable, continuous access to DTI data. There are three types of the API:
DTI Standard API for access requests to the Registry, in line with its commitment to ISO:
More information on the APIs are available on the DTI webpage: https://dtif.org/dti-api/
The DTI Registry supports identification of three different record types: tokens, ledgers and assets.
Ledgers (DLTs) are identified with a DLI and Distributed ledger technology type = 1 (blockchain) or 0 (other). Ledgers can be public or private, and most have at least one protocol, auxiliary or NFT token assigned to them to be added to the registry.
Tokens are identified with a DTI and Digital Token Identifier Type = 0 (Auxiliary), 1 (Protocol), or 4 (NFT).
Auxiliary token is defined as “non-protocol digital token created as an application on an existing blockchain or other distributed ledger technology”. Auxiliary tokens are assumed to be fungible on the DLT that they have been created on. Examples include (but not limited to) stablecoins, memecoins, security tokens, assets referenced tokens.
Protocol token is defined as “single digital token that can be transacted on a distributed ledger with no further protocol-level identification required”. Protocol tokens (previously defined in the standard as native tokens) are mostly commonly used to power the DLT through gas fees and usually known as utility tokens. Examples include BTC, ETH, SOL, DOT.
NFT tokens are similar to auxiliary, but are defined separately as they have different meta data elements. NFT tokens can be defined directly or together as an NFT group.
Assets are identified with a DTI and Digital Token Identifier Type = 3 (equivalent digital token group). The group can contain one or more auxiliary or protocol DTI that represent the same asset if they meet two or more of the following criteria: Architectural, Organisational, Technical.
Considerations: Are the tokens implemented with consistent design principles and architectural specifications? Are they backed by the same asset and pegged to the same value?
Considerations: Are the tokens created and maintained by the same organisation?
Considerations: Do the tokens share technical implementation? Are the DLTs on which tokens are implemented linked without a third party? Can transactions in one token be settled by another token?
Each DTI and DLI record has a status a status update date associated with it.
The record has been created and validated.
The record certified by issuer, issuer information is recorded against the record. Certification lasts 12 months, after which time the record is marked as LAPSED.
The record certification not been renewed on time.
The record has ceased operations.
In addition to the status, each record has information class indicator.
All data elements that are verified according to the guidelines and can be independently verified by the general public. The level of validation required for each data element varies as described in the DTI Validation Guide.
One or more data elements are not yet available. The provisional record will either become validated once all the individual data elements have been validated, or deleted from the registry.
Data elements are verified by the DTIF but cannot be independently verified by the general public.
Data elements are available but either not specified in the request and not known, or known but have not yet been verified.
DTIs and DLIs are displayed using capital letters.
DTIs and DLIs are nine characters in length, consisting of eight character (alphanumeric) basic number and a check character computed using the method specified in Annex A of ISO standard 24165.
The alphanumeric basic number excludes vowels (A, E, I, O, U) and the letter Y. DTIs and DLIs do not start with zero.
The basic number of a DTI or DLI is randomly generated and intended to be semantically meaningless. In a case where a randomly generated identifier may inadvertently appear to be semantically meaningful, that identifier may be discarded at the discretion of the DTIF and a new identifier assigned.
Registrant shall notify DTIF if they become aware that the basic number of the DTI or DLI allocated and registered to the Digital Token is semantically meaningful in any language.
| Cookie | Duration | Description |
|---|---|---|
| dtif.cookie.necessary | 11 months | Necessary cookies needed for the site to function as needed. |
| dtif.cookie.viewed_policy | 1 year | Cookie which determines if we can drop our cookies into the user’s browser. |
