Checks whether a held credential has been suspended or revoked.
For list-based revocation methods, the signed lists and any DID
documents containing public keys used to verify the lists are
cached. Use forceRefresh to force the system to retrieve these
from the external resource.
For modcs, use forceRefresh to force the system to request a
new MSO.
For wallet-initiated flows, continues the OpenID4VCI issuance process after completing authorization.
redirectUri and is used to continue the
Authorization Code Flow issuance process. For example:
myapp://example/credential-offer?code=xxx&clientId=myWallet&...Creates a backup of the current database and writes it to a file.
Creates a credential schema
Deprecated. Use the createIdentifier method.
For verifiers, creates a proof request and returns its ID. Choose what information to request via a proof schema, an identifier, and which protocol to use for making the request.
For online protocols, the request is created in CREATED state;
share it with the wallet using shareProof. For ISO_MDL, the
wallet starts the exchange: pass the device engagement data from the
wallet in isoMdlEngagement. The request is created directly in
PENDING state and needs no sharing.
Creates a proof schema, which defines the credentials and claims to request from a wallet. Proof schemas reference credential schemas already created in your own system; create or import those first before building a proof schema that includes their claims.
Permanently removes a credential schema.
Deletes an incomplete proof request. If the request is in REQUESTED
state the proof is retracted instead, retaining history of the interaction.
For ISO_MDL, this also closes the BLE session.
Deletes the claim data shared by the wallet holder for a proof
request, without waiting for the retention period set by the
expireDuration of the proof schema. The proof request itself is
kept, and claimsRemovedAt records when the claims were deleted.
Commits to the restored database, replacing the original. The old database is deleted.
Returns detailed information about a credential in the system.
Returns detailed information about a credential schema. A credential schema defines the structure and format of a credential, including the attributes that issuers make claims about. Schemas also specify how issued credentials should be presented in wallets, whether a revocation method is used to manage credential status, and issuer preferences for suitable key storage types for wallets to use.
Returns detailed trust information about a credential issuer.
Returns the full record for a single history event, including metadata if present.
Returns details of an existing organization, including the ecosystems offered to it.
For wallets, returns what a proof request asks for and which of the
wallet's credentials can satisfy it. Use the result to build the
submission for holderSubmitProofV2.
For ISO_MDL requests, every claim has required: false, since the
protocol cannot mark claims as mandatory. An incomplete submission
may be rejected if the verifier requires claims not submitted.
Returns detailed information about a proof request.
Poll this method to follow the state of the request.
Returns detailed trust information about the requesting entity for a proof request.
For a wallet, handles the interaction once the wallet connects to a share endpoint URL (for example, scans the QR code of an offered credential or request for proof).
Not for use with ISO_MDL proximity flows, where the wallet initiates the
flow using proposeProof instead.
Accepts an offered credential. The system will generate a new identifier that matches issuer's restrictions. Alternatively, you can specify an existing identifier.
Activates the instance with the provider after user authentication.
Returns instance registration details from the provider.
For wallets; returns the details of a single transaction data entry of a
proof request, including human-readable display data and the raw
transaction data received from the verifier. The transactionDataId is
obtained from getPresentationDefinitionV2. See
Transaction Authorization for Wallets
for more information.
Checks the status of an instance with the provider. Successful calls return 204.
To see the result, call holderGetInstance.
Request a new credential batch.
Registers the instance with a Wallet or Verifier Provider.
Rejects credentials or individual batch items. Selecting a batch parent rejects all its items.
Without credential_ids, all credentials of the interaction are rejected.
A batch format is notified as rejected and excluded from refreshes only when all its items are rejected.
For wallets, rejects a proof request. Pass the interactionId of
the request, not the proof ID.
For ISO_MDL, the wallet sends an empty response to the verifier and
closes the BLE session.
For wallets, submits a presentation using DCQL as a query language.
Use this after getPresentationDefinitionV2. Pass the
interactionId of the request, not the proof ID.
submission maps each credential query ID from the presentation
definition to the credentials chosen for it.
Imports a credential schema shared from another mobile verifier device using the one-core.
For wallets, starts the OpenID4VCI Authorization Code Flow.
Returns a filterable list of credentials in the system.
Returns a filterable list of credential schemas.
Returns a filterable list of history events.
Returns a filterable list of identifiers.
Returns a filterable list of proof requests.
Cancel previously started NFC scan via nfc_read_iso_mdl_engagement.
For wallets, initiates device engagement for offline flows. Reference
the verificationEngagement entry of your configuration for your
options for engagement.
For ISO_MDL, this creates a proof in PENDING state and starts BLE
according to the bleMode set in your configuration. Poll getProof
until the state is REQUESTED, then call
getPresentationDefinitionV2.
Initiates the QES signing flow for a document with a configured
QES provider. Returns an authorizationUrl for the user to
authenticate with the provider, and a codeVerifier to be passed
to the qesSign method on return.
Completes the QES signing flow. Exchanges the authorization
code received from the provider redirect and the codeVerifier
from qesAuthorize for a signed document.
Returns the JSON-LD context document for a given URI. This is a cached entity.
Discards the restored database and continues using the original.
Triggers a configured task by name. Pass the task name as defined in the
task configuration object, and optionally a JSON string of task-specific
parameters. Returns the result as a JSON string.
Produces a URL for sharing a credential schema with another mobile verifier device using the one-core.
Creates a share URL from a proof request. A wallet holder can use this
URL to access the request. Not used for the ISO_MDL proximity flow.
Deleting data while uninitializing the Core erases all wallet data permanently. If data is not deleted it is reused when Core is reinitialized.
Makes the restored database active for calls.
Follow by calling either finalizeImport or rollbackImport.
Updates or deactivates an organization
Returns information about items that will be excluded from the export.