GET/did-registry/v3/identifiers/:did/versions/:versionId/metadata/:metadataId
Returns the DID document metadata based on their ID.
Request
Path Parameters
- DID
- Version ID
- Metadata ID
A DID to be resolved.
Example: did:ebsi:z25F87e2MyLKF7DViuHi5b4z
A unique version ID.
Example: 0x909f8a83b0a4542e13afa30ce198234e919bffd90965f684a2491e6db70fe92a
A unique metadata ID.
Example: 0xb5ed423b79dd39df26194f708414e394eb924638a0b8e8e0a09c760dc7cdc607
Responses
- 200
- 400
- 404
- 500
Success
- application/json
- Schema
- Example (from schema)
- Success
Schema
DID document metadata as a JSON document
{}
{
"key": "value"
}
Bad Request
- application/problem+json
- Schema
- Example (from schema)
- Invalid {did} Parameter
- Invalid {versionId} Parameter
- Invalid {metadataId} Parameter
Schema
Default value: about:blank
An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.
A short summary of the problem type.
Possible values: >= 400 and <= 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"type": "about:blank",
"title": "Internal Server Error",
"status": 500,
"detail": "Connection timeout",
"instance": "string"
}
{
"title": "Bad Request",
"status": 400,
"detail": "The format of {did} parameter is not valid"
}
{
"title": "Bad Request",
"status": 400,
"detail": "The format of {versionId} parameter is not valid"
}
{
"title": "Bad Request",
"status": 400,
"detail": "The format of {metadataId} parameter is not valid"
}
Not found
- application/problem+json
- Schema
- Example (from schema)
- DID Not Found
- Version ID Not Found
- Metadata ID Not Found
Schema
Default value: about:blank
An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.
A short summary of the problem type.
Possible values: >= 400 and <= 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"type": "about:blank",
"title": "Internal Server Error",
"status": 500,
"detail": "Connection timeout",
"instance": "string"
}
{
"title": "Not found",
"status": 404,
"detail": "Not found"
}
{
"title": "Not found",
"status": 404,
"detail": "Not found"
}
{
"title": "Not found",
"status": 404,
"detail": "Not found"
}
Internal Server Error
- application/json
- Schema
- Example (from schema)
- Internal Server Error
Schema
Default value: about:blank
An absolute URI that identifies the problem type. When dereferenced, it SHOULD provide human-readable documentation for the problem type.
A short summary of the problem type.
Possible values: >= 400 and <= 600
The HTTP status code generated by the origin server for this occurrence of the problem.
A human readable explanation specific to this occurrence of the problem.
An absolute URI that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.
{
"type": "about:blank",
"title": "Internal Server Error",
"status": 500,
"detail": "Connection timeout",
"instance": "string"
}
{
"title": "Internal error",
"status": 500,
"detail": "Internal error"
}