Overview of Hovi APIs
Hovi provides two wallet surfaces: the Organizational Wallet for issuers and verifiers (business use), and the Cloud Wallet API for end users (holders). The Organizational Wallet manages credential issuance, revocation, and cross-ecosystem verification, aligned with EU standards like eIDAS 2.0.
The Cloud Wallet API securely stores user wallets and enables on-demand credential proofs. Together, they offer end-to-end issuance, storage, and presentation of verifiable credentials, supporting multi-format credentials, privacy-first design, and seamless app integration.
Business Wallet API (Issuer / Verifier Side)
The Business Wallet API is the interface for organizations to issue, manage, and verify verifiable credentials at scale.
What it enables:
- Credential issuance: Create credential offers (for SD-JWT, JSON-LD, mDocs, etc.), send them to wallets or holders, and manage issuance policies.
- Verification & proof validation: Accept proof presentations from wallets, validate them, and return trusted results.
- Organization / ecosystem management: Manage credential and verification templates, webhooks, and tenant-level settings.
- Scalable operations: Optimized for volume, multi-tenant environments, and large issuance or verification workloads.
- Unified across ecosystems: Support for multiple identity ecosystems (OpenID, Cheqd, Indicio, Privado) under one API surface.
The Business Wallet API is your toolset for the issuer / verifier roles — entities that hold authority to issue and verify credentials.
Cloud Wallet API (Holder / Wallet Side)
The Cloud Wallet API provides a managed wallet layer to hold, present, and respond with credentials on behalf of users. It abstracts the wallet infrastructure so apps can integrate wallet features with minimal complexity.
What it enables:
- Wallet management: Create, retrieve, recover, and delete user wallets securely in the wallet.
- Credential operations: Preview credential offers, accept or decline credentials, list stored credentials, and delete credentials.
- Proof / presentation flows: Preview proof requests, submit presentations (proofs), decline proof requests, and query proof status.
- Connection management: Accept connection invitations and list or fetch connection details to enable secure communication channels.
- Webhook integration: Register webhook endpoints to receive events (e.g. credential accepted, proof processed, connection established).
- Cross-ecosystem compatibility & formats: Supports SD-JWT, mDocs, JSON-LD, OpenID-based flows, and multi-protocol interoperability e.g didcomm, openid.
- Fully managed infrastructure: Scales to thousands or millions of wallets without requiring you to run wallet servers or cryptographic key management.
The Cloud Wallet API is your toolset for the holder (wallet) role — enabling user-facing applications to manage credentials transparently without local wallet dependencies.
How They Work Together & When to Use Which
| Role | API to Use | Typical Workflow |
|---|---|---|
| Issuer / Credential Provider | Business Wallet API | You issue credential offers, define templates, and request proof validations. |
| Verifier / Relying Party | Business Wallet API | You request proofs, verify user presentations, and enforce policies. |
| Holder-facing Application | Cloud Wallet API | You provision user wallets, store credentials, present proofs, and manage connections. |
Sample end-to-end flow:
- Use Business Wallet API to issue a credential offer.
- The offer is passed to the Cloud Wallet (via your app) where Cloud Wallet API previews and accepts it.
- Later, a proof or presentation is requested — your app requests proof via Business Wallet API.
- The Cloud Wallet submits presentation via Cloud Wallet API.
- The Business Wallet API verifies the proof and returns a result.