create Digital Twin
POST/api/gemini/v1/digital-twin
create a Digital Twin for an entity using the registry provided within the body
Request
- application/json
Body
required
The object identifier and optional service endpoints, which provides additional information to the physical object
Array [
]
the unique identifier of the physical / real item
the kind / object of the physical / real item.
could although be used to cluster objects into groups like bottles-1l, bottles-500ml
Default value: Polygon Mumbai Testnet
The ledger to be used, if not provided the default ledger of the project/client will be used.
Only registries defined for the project/client combination can be used.
Only "Polygon Mumbai Testnet" is initially supported
serviceEndpoints
object[]
A list of additional endpoints, which should be added to the Digital Twin. This operation is asynchronous and requires a ledger transaction. So the result will no be immediately available
the endpoint url providing additional services / information for the digital twin
Default value: LinkedDomain
categorization of the provided service url, if not maintained, LinkedDomain will be used.
Only chars a-z or A-Z are allowed
Responses
- 201
the created Digital Twin, be aware if services were added
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
Array [
]
the decentralized identifier of the physical object. see https://www.w3.org/TR/did-core/
the alias used for identifying the did. This could be a human readable identifier for did:web or the public address of a ledger based did
the protocol, method and optional the ledger identifier of the did.
Protocol is did
method for example ethr
and ledger identifier polygon:mumbai
the public ledger address of the controller / owner of a Digital Twin / DID
keys
object[]
required
A list of key materials used for verification, access and ownership.
identifier of the Key, acts like an alias for the key
the key management system of the key
Key algorithm
public part of the key as a string in hex format
the private part of the key, based on the security reasons will not be returned
meta
object
a lis tof supported key algorithm
services
object[]
required
A list of service endpoints, providing additional information to the digital twin
the identifier of the service. Required for deletion operation
Default value: LinkedDomain
categorization of the provided service url, if not maintained, LinkedDomain will be used.
Only chars a-z or A-Z are allowed
the endpoint url providing additional services / information for the digital twin
Endpoint is providing additional material information like Certificates and hazardous information
{
"did": "did:ethr:polygon:mumbai:0x023b1de7d53ebe9d97015514f44610702d889528fa0f00ffab8893c89426129462",
"alias": "0b6fe947a3add76d66ab697a46c1268e399366f98b44baf172cbb73762bbb01a",
"provider": "did:ethr:polygon:mumbai",
"controllerKeyId": "043b1de7d53ebe9d97015514f44610702d889528fa0f00ffab8893c89426129462a4266843f80b98fdc76077c066d89fae807a8d314e4c3947976fd64f726ee6da",
"keys": [
{
"type": "Secp256k1",
"kid": "043b1de7d53ebe9d97015514f44610702d889528fa0f00ffab8893c89426129462a4266843f80b98fdc76077c066d89fae807a8d314e4c3947976fd64f726ee6da",
"publicKeyHex": "043b1de7d53ebe9d97015514f44610702d889528fa0f00ffab8893c89426129462a4266843f80b98fdc76077c066d89fae807a8d314e4c3947976fd64f726ee6da",
"meta": {
"algorithms": [
"ES256K",
"ES256K-R",
"eth_signTransaction",
"eth_signTypedData",
"eth_signMessage",
"eth_rawSign"
]
},
"kms": "local"
}
],
"services": [
{
"id": "did:ethr:polygon:mumbai:0x03b383ce5ae3b7ec5d91f13cbe2088eb05890f217f4028505379a73404dc1ff2b5#service-1",
"type": "LinkedDomains",
"serviceEndpoint": "http://foo.bar"
}
]
}