Skip to main content

Enabling Ecosystems

This page explains how to make ecosystems available to your organization.

Enabling an ecosystem​

To enable an ecosystem, update your organization with one or more selections from the ecosystem configuration:

PATCH /api/organisations/v1/{id}

{
  "configuration": {
    "selectedEcosystems": [
      "EUDI"
    ]
  }
}
info

In mobile devices, use the corresponding upsertOrganisation method.

A successful call returns 204.

This gives the organization the ability to:

  • Issuing — Constrain issuance according to the rules of a selected ecosystem
  • Holding — Auto-detect an ecosystem and constrain the interaction according to the rules of a selected ecosystem
  • Verifying — Constrain verification according to the rules of a selected ecosystem

Enforcing an ecosystem​

Selecting ecosystems for an organization makes the constraints available for use in interactions. For how to use the constraints as an issuer or verifier, see:

Wallets can behave differently depending on whether they are managed instances registered with a Wallet Provider or standalone. For standalone wallet enforcement behavior, see:

Providers of managed instances of wallets and verifiers can control ecosystem selection and enforcement behavior of those instances. See:

Removing ecosystems​

To remove an ecosystem, update the organization. Pass an empty selectedEcosystems array to remove all ecosystems, or pass a new array containing only the desired ecosystems.

Creating trust collections​

In addition to making ecosystems available for use, you must also create the necessary trust collections for each ecosystem. See Subscribing to Trust Lists.