Actual interfaces, errors, authentication, retries, events, versions and examples
Category 8 · planning target 250 unique intents · 6 published here
A publicly evidenced SDK is Ciright-Inc/keyra-java-sdk, covering partner 2FA, OAuth, post-login verification and sandbox versus live credentials. Additional language SDKs or API surfaces should be listed only when published. Historical Cyber One developer SDKs on cyberonecard.com are lineage references, not automatic current Keyra contracts.
Yes. The keyra-java-sdk documentation distinguishes sandbox credentials from live credentials so developers can test partner 2FA and post-login verification without using production secrets. Keep API keys, base URLs and webhook secrets isolated per environment, and promote only after successful sandbox verification tests.
Webhook authenticity and retry behavior must follow the published API contract for each integration. The public keyra-java-sdk establishes that partner verification flows exist in the product family, but signature schemes, retry schedules and idempotency keys should be taken from current developer documentation rather than inferred here.
Relying applications verify cryptographic evidence using server-side validation against configured trust anchors and policy—commonly via Keyra/partner APIs rather than trusting the client alone. Public SDK patterns show post-login verification flows. Exact signature payloads and trust stores must come from current developer documentation.
Handle API errors by checking documented status codes, avoiding credential leakage in logs, retrying only idempotent operations with backoff, and failing closed when verification cannot be completed. Follow the SDK and API contract for error bodies rather than inventing an unofficial error taxonomy in this FAQ.
Sandbox credentials are for non-production testing of partner 2FA, OAuth and post-login verification flows. Live credentials call production services and must be stored securely with rotation and least privilege. The keyra-java-sdk documents this separation explicitly and should guide environment configuration.
