Deploy digital wallet
POST/v2/config/digital-wallet/openid
Deploys the OID4VC digital wallet for the organisation. The service registers the organisation with the OpenID wallet backend and returns the endpoints of the new deployment. Call this operation once, before you create a global configuration, a credential definition or a presentation definition.
The organisation must have no deployment yet. If a deployment exists or a deployment request is open, the service answers with HTTP 400. There is no operation that removes a deployment, so you cannot deploy the wallet a second time.
Request
- application/json
Body
Optional seed for the key material of the wallet. Send an empty body to let the service make the deployment without a seed.
Seed that the service uses for the key material of the wallet. This field is optional. The service uses the value only when it holds one character or more, and it sends no seed when you give an empty value or leave the field out. Treat this value as a secret: keep it out of logs and out of version control.
Responses
- 200
- 400
- 401
- 500
The service deployed the OpenID digital wallet and returned the deployment details.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Base URL of the OID4VCI and OpenID4VP service of the organisation.
URL of the OID4VCI Credential Offer endpoint.
Software version of the deployed agent.
Possible values: [2]
Deployment status of the agent. A successful deploy always sets the status to Deployed, so this operation always gives 2.
Possible values: [Deployed]
Deployment status of the agent as text. This operation always gives Deployed.
Name of the distributed ledger that the agent uses for DID registration.
URL of the distributed ledger.
Identifier of the ledger network. The service does not set this field and always returns 0.
Infrastructure provider that hosts the agent.
Geographic region of the agent deployment.
When true, the organisation is a wallet provider and can issue Wallet Unit Attestations. A new deployment always returns false. Use the update operation on this path to enable the capability.
{
"agentServiceEndpoint": "https://api.igrant.io/v2/organisation/62d9e0b9e5b1a80001d0f8b1/service",
"credentialOfferEndpoint": "https://api.igrant.io/v2/organisation/62d9e0b9e5b1a80001d0f8b1/service/credential-offer",
"version": "1.0.0",
"status": 2,
"statusStr": "Deployed",
"ledgerName": "European Blockchain Services Infrastructure",
"ledgerURL": "https://hub.ebsi.eu/",
"ledgerID": 0,
"infrastructureProvider": "iGrant.io",
"deploymentRegion": "Europe: Frankfurt",
"isWalletProvider": false
}
The organisation is unknown, the organisation already has a deployment, a deployment request is already open, or the wallet backend refused the registration.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Unauthorized
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}
Internal server error
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"errorCode": 400,
"errorDescription": "Bad input parameter"
}