Skip to main content
POST
/
v1
/
did
/
register
cURL
curl --request POST \
  --url https://staging.terminal3.io/v1/did/register \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'x-api-token: <x-api-token>' \
  --data '
{
  "did": "<string>",
  "wallet_address": "<string>"
}
'
{
  "data": {
    "did": "<string>",
    "success": true
  }
}
This API takes the DID generated from the client and registers it to the T3 DID Registry. E.g of a payload:
JSON
{
  "did": "did:key:zUC7JcS7aXAmShxRSMA5RuBnT6nv2rBhnKve2hRTWtoaz7EfXT4SxTdbLa22fmpyr41GJDkuC4fngNuLPofpqLSagNkLxG9Ffcu9xw25NPJavMuGQR2BA7sqzacraTYNST79jZw",
  "wallet_address": "0x379d552d1B2615F4De8a03c96f2ff4890646236c"
}
  • Only did:key is supported for now.
  • The header X-API-SubClient-ID must be provided when registering DID for a sub-client. If omitted, the request is treated as coming from the master client.
Please refer to our VC SDK for more details on how to generate DID from a public key.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
x-api-token
string
required
​
x-api-subclient-id
string

Body

application/json
​
did
string
required
Minimum string length: 1
​
wallet_address
string
required
Minimum string length: 1

Response

Success

​
data
object
required