Functional Capabilities

The Participant Registry provides a set of functional capabilities that enable participants and systems to retrieve, verify, and manage trusted information about organisations within a data space. These capabilities are laid out in the iSHARE Trust Framework and implemented through standardised data models and interfaces.

Participant identification & metadata

At its core, the Participant Registry maintains a structured representation of each participant. This includes identifiers (such as EORI or DID), organisational information, and metadata describing the participant’s role within the data space.

Each participant is represented as a “party”, accessible via standardised endpoints. This allows other participants to retrieve consistent and machine-readable information when initiating interactions.

Trusted lists & certificates

To support secure communication, the Participant Registry provides access to trusted technical information, such as:

• certificates and public keys
• trusted lists
• framework and data space references

This information allows systems to:

• verify digital signatures
• establish secure connections
• ensure that interactions occur within a trusted environment

Verifiable Credentials integration

The iSHARE Trust Framework enables the Participant Registry to issue Participant Credentials as Verifiable Credentials (VCs).

These credentials:

• are issued to onboarded participants
• can be stored in digital wallets
• can be presented to other parties during onboarding or service usage

When a credential is presented, the receiving party can verify:

• the issuer (Participant Registry)
• the integrity of the credential (signature)
• the schema and structure
• the current validity status

This capability complements traditional registry lookups and enables portable trust across data spaces, allowing participants to reuse verified credentials in different contexts.

APIs & endpoints (See more Here)

The Participant Registry exposes its functionality through a set of standardised APIs. These enable automated interaction and integration with other components in the ecosystem.

Key endpoints include:

• /parties — retrieve participant information
• /claims — retrieve claims associated with participants
• /capabilities — discover supported functionalities
• trusted list, data spaces and framework endpoints

Optional endpoints may support:

• creation and updating of participants and claims (typically restricted to authorised onboarding systems)

These interfaces ensure that the Participant Registry can act as a machine-readable and interoperable source of truth for participant data.