Tenant Setup

Onboarding with your Tenant

Our customers are set up with the MATTR Platform via an out-of-band onboarding process. By the time you start using our platform, a few key components have been pre-configured for your convenience.

Each user of our platform will have:

  • Dedicated Platform Tenant
  • API keys
  • Default Decentralized Identifier (DID) configured
  • Basic claim mappings from OIDC to JSON-LD

If you are missing any of these components or have questions, contact us before proceeding.

Try it out

A good first test to check everything is working is to obtain your Access token, then make a call to the Retrive a list of DIDs endpoint and make sure you have a default DID setup.


Take a look at the Authorization section of the API Reference. Use the client ID and secret to make a call to the authorization provider and obtain the API access token.

This will be used as a bearer token for all requests to protected resources.


Using your newly acquired access token make a GET request to:


This is an example in cURL:

curl --request GET \
--url https://tenant.platform.mattr.global/v1/dids \
--header 'Accept: application/json' \
--header 'Authorization: Bearer REPLACE_ACCESS_TOKEN'


This response shows a single DID returned in an array:

"did": "did:key:z6MkejNs6Xp8ZQimw1yqhtLk2MCD9EsW2wopVpVPrqRM1K",
"metadata": {
"keys": [
"kmsKeyId": "H7pWHZhDsEJpX9EuAUziFDLFdsPTcnb7oatf7tpW8Dw",
"didDocumentKeyId": "did:key:z6MkejNs6Xp8ZQimw1yqhtLk2MCD9EsW2wopVpVPrqRM1K#z6MkejNs6Xp8ZQimw1ywajSqZLmL5D9EsW2wopVpVPrqRM1K"
"kmsKeyId": "BX55nzBfN15ExB7PNuePR6pdMLfErn3X4sgqnMdXfpgX",
"didDocumentKeyId": "did:key:z6MkejNs6Xp8ZQimw1yqhtLk2MCD9EsW2wopVpVPrqRM1K#z6LSnCFFKHzXTTnz3ZV9uZALjh37CVCMZPDfwrQXGpH4PCTH"
"registered": 1591168882617

This lets you know that your access is valid and that a DID has been configured in the tenant, this can be used onwards for Issuing Credentials and validating messages to holders during the Verify credential flows.