# Coincover Developer Docs ## Docs - [Partner - Store secure encrypted data](https://developer.coincover.com/api-reference/backups/partner--store-secure-encrypted-data.md): Stores base64-encoded encrypted data with checksum validation and padding type specification. The data is verified using the enclave before storage. Partner-only endpoint. The checksum is required and must be the SHA-256 of the plaintext. - [Partner - Store secure encrypted files](https://developer.coincover.com/api-reference/backups/partner--store-secure-encrypted-files.md): Stores encrypted files securely. The key environment is determined from the provided key. The file must already be encrypted on the partner side; CoinCover applies no additional server-side encryption. Maximum payload 10MB. Partner-only endpoint. - [Recover encrypted backup data](https://developer.coincover.com/api-reference/backups/recover-encrypted-backup-data.md): Recovers previously stored backup data. Requires successful identity verification (verification_id must be approved/successful). Requires a GPG public key for encrypting the recovered data. Returns an array of backup recovery results, each containing recovery information or error details. This endpo… - [Store encrypted backup data](https://developer.coincover.com/api-reference/backups/store-encrypted-backup-data.md): Stores encrypted backup data securely. Accepts multiple backup items in a single request via the backup array (limited to a maximum of 3 items). Requires a verification_id that exists in the identity_verifications table and belongs to the user associated with the organisation. Each backup item's ite… - [Store secure encrypted data](https://developer.coincover.com/api-reference/backups/store-secure-encrypted-data.md): Stores base64-encoded encrypted data with optional checksum validation and padding type specification. The data is verified using the enclave before storage. Supplying the SHA-256 of the plaintext as the checksum is recommended. - [Store secure encrypted files](https://developer.coincover.com/api-reference/backups/store-secure-encrypted-files.md): Stores an already-encrypted file. CoinCover applies no additional server-side encryption. - [Verify a backup's integrity](https://developer.coincover.com/api-reference/backups/verify-a-backups-integrity.md): Verifies that a backup is valid by checking the encrypted data. - [Assign a new key](https://developer.coincover.com/api-reference/keys/assign-a-new-key.md): Creates a new key pair with the enclave, shards the private key, and securely stores the encrypted key shards. organisation and package are optional; key_environment defaults to HOT if omitted. - [Generate a cryptographic key](https://developer.coincover.com/api-reference/keys/generate-a-cryptographic-key.md): Generates a new cryptographic key for a user. Requires a user identifier and a verification_id that exists in the identity_verifications table and belongs to the user associated with the organisation. This endpoint calls the hot-keys orchestrator partner-assign-key endpoint. - [Partner - Assign a new key with environment specification](https://developer.coincover.com/api-reference/keys/partner--assign-a-new-key-with-environment-specification.md): Creates a new key pair with the enclave, shards the private key, and securely stores the encrypted key shards. Includes key environment specification: HOT (online generation/storage) or COLD (offline generation/storage). Partner-only endpoint. - [Verify a key's integrity](https://developer.coincover.com/api-reference/keys/verify-a-keys-integrity.md): Verifies that a key's shards can be reconstructed and that the key pair is valid. - [Get verification status](https://developer.coincover.com/api-reference/verification/get-verification-status.md): Retrieves the current status of a biometric verification. The status can be in multiple states: 'pending' (initial state), 'approved' (all verifications passed), 'declined' (verifications failed), or 'review' (marked for manual review). - [Simulate biometric verification events](https://developer.coincover.com/api-reference/verification/simulate-biometric-verification-events.md): Simulates biometric verification events for testing in non-production environments. - [Start identity verification](https://developer.coincover.com/api-reference/verification/start-identity-verification.md): Initiates a new identity verification workflow and returns a Verification ID. The user will use this verification_id to spin up a front-end SDK that will guide the user through the identity verification workflow. - [Changelog](https://developer.coincover.com/changelog/changelog.md): New features, fixes, and improvements to CoinCover. - [Welcome to CoinCover](https://developer.coincover.com/index.md): Pick the product you're integrating with and follow its guide. - [Add a backup key](https://developer.coincover.com/institutional-recovery/add-a-backup-key.md) - [Back up key material](https://developer.coincover.com/institutional-recovery/back-up-key-material.md): Encrypt your own recovery material client-side and store it with CoinCover, using an RSA key. - [CLI integration guide](https://developer.coincover.com/institutional-recovery/cli-integration-guide.md) - [CLI reference](https://developer.coincover.com/institutional-recovery/cli-reference.md) - [Overview](https://developer.coincover.com/institutional-recovery/overview.md): How to integrate CoinCover recovery for your institution — through a supported wallet platform, our API, or the CLI. - [Testing](https://developer.coincover.com/institutional-recovery/testing.md) - [Integration guide](https://developer.coincover.com/retail-recovery/integration-guide.md): End-to-end integration of Recover for Retail. - [Overview](https://developer.coincover.com/retail-recovery/overview.md): Identity-verified backup and recovery for end users of consumer wallets. - [Testing & sandbox](https://developer.coincover.com/retail-recovery/testing.md): Simulating verification outcomes without real customers. - [UI components](https://developer.coincover.com/retail-recovery/ui-components.md): Embedding the Identity SDK in your wallet app for retail recovery. - [API integration guide](https://developer.coincover.com/wallet-provider-recovery/api-integration-guide.md): End-to-end integration of the Partner Key Service for wallet providers. - [Overview](https://developer.coincover.com/wallet-provider-recovery/overview.md): Backup and recovery for institutional digital asset wallets, integrated with your wallet platform — for providers backing up their customers' wallets. - [Testing & sandbox](https://developer.coincover.com/wallet-provider-recovery/testing.md): Walking through every recovery scenario before you ship — for wallet providers on the Partner Key Service. ## OpenAPI Specs - [retail.openapi](https://developer.coincover.com/specs/retail.openapi.json) - [wallet-provider.openapi](https://developer.coincover.com/specs/wallet-provider.openapi.json) - [institutional.openapi](https://developer.coincover.com/specs/institutional.openapi.json) - [openapi](https://developer.coincover.com/api-reference/openapi.json)