Developer cookbooks

14 recipes to integrate CodeB in an afternoon.

Task-oriented developer guides — every recipe is copy-paste-ready, tested against a real CodeB tenant, and honest about what ships today. Sign in with OIDC or the European Digital Identity Wallet, embed calling and chat, verify webhooks, stream events, forward audit trails to your SIEM. Pick the one you need.

Start with OIDC sign-in → Browse the API hub Get a tenant

Cookbooks shipped

50+

Snippets across languages

Data residency, self-hosted

Hyperscaler dependencies

01 / Identity & sign-in

Wire CodeB into your login story.

Add OIDC sign-in, validate the tokens yourself, federate to the IAM broker your enterprise already runs, or automate everything from a backend with M2M keys. All four flows are RFC-compliant and PKCE-first.

Sign in with OIDC

Authorization-code + PKCE (S256) against the CodeB discovery document. Ready-to-paste snippets for Vanilla JS, React, Angular, Vue 3, Node/Express, Python/Flask, PHP and ASP.NET Core.

8 frameworks Open cookbook →

Validate JWTs locally

Fetch the JWKS, verify RS256 signatures, check issuer / audience / expiry — without a callback to CodeB. Snippets for Node.js, Python, Go, Java, .NET, PHP and Ruby.

7 languages Open cookbook →

Federate IAM

Drop CodeB in as an upstream OpenID Connect Identity Provider for Keycloak, Auth0, Okta, Microsoft Entra ID or AWS Cognito — configuration only, no custom code.

5 brokers Open cookbook →

M2M API keys

Server-to-server automation with rotating API keys. HMAC-signed requests, tenant-scoped, revocable in one click. Includes rotation playbook and least-privilege scope guidance.

Backend automation Open cookbook →

02 / European Digital Identity Wallet

Accept EU Wallet sign-in in your app.

The CodeB verifier speaks OpenID4VP 1.0 and HAIP 1.0 today. Accept SD-JWT VC and mDoc presentations, ECDH-ES JWE-encrypted responses, DCQL queries, JAR request objects. The two guides below cover the copy-paste path plus the full ecosystem — verifier, issuer, wallet, trust anchor.

Accept EU Wallet sign-in

OpenID4VP verifier integration for Vanilla JS, React, Angular, Vue, Node/Express and Python/Flask. Renders the QR, polls for the wallet response, exchanges for a tenant session token.

6 frameworks · OID4VP Open cookbook →

EU Wallet ecosystem

The bigger picture: how CodeB fits alongside the reference EU Wallet, HAIP verifier certification, EU LOTL trust-anchor cache and the OpenID4VCI credential issuer. Cross-links every wallet page in one map.

Verifier · issuer · wallet · trust anchor Open cookbook →

03 / Embed comms

Put calling, chat and meetings on any page.

Three lightweight embeds. The softphone is a full SIP-over-WebSocket iframe. The chat widget is a floating “Chat with us” button that opens a tenant-hosted room. The meet embed is a click-to-conference launcher. All three are drop-in, no NPM required.

Embed softphone

Iframe the CodeB SoftPhone into any tenant page or third-party site. Sandboxed, tenant-scoped, SIP-over-WebSocket. Includes CSP hardening and per-user OIDC gating recipes.

SIP-over-WebSocket iframe Open cookbook →

Embed chat widget

Chat-with-us button that opens a per-visitor tenant chat room. Per-domain allow-list. Guest sessions issued via HMAC invitation. Anonymous visitors are OIDC-invited only.

Chat-with-us on any site Open cookbook →

Embed meet room

Click-to-conference button that spins up a signed room and drops the visitor into a browser meeting. QR + shareable URL. Personal-name pre-fill honoured only for explicit personal links.

Click-to-conference button Open cookbook →

Sign a PDF (PAdES-B-T)

Browser-side PAdES-B-T assembly against a Cloud Signature Consortium (CSC) v2 endpoint — incremental save preserves prior signatures, an RFC 3161 timestamp is embedded into every signature, encrypted PDFs (RC4-128 & AES-128) are supported, and each user gets an EC P-256 signing certificate enriched from their OIDC profile (CN / given / family / e-mail with SAN). Advanced Electronic Signature only (self-signed trust chain) — not QES. Ready for European Digital Identity Wallet integrations.

CSC v2 · PAdES-B-T · RFC 3161 Open the signer →

Server-side signDoc (CSC v2)

Prefer server-side PAdES assembly? The CSC v2 signatures/signDoc endpoint (§11.10) accepts a document upload, produces the CMS signature and returns the signed PDF — useful for batch jobs, notifications and PMS integrations. Same per-user certificate and RFC 3161 timestamp as the browser flow.

CSC v2 §11.10 · server-side See the endpoint →

Digital signatures cookbook

End-to-end integration guide covering all four PAdES conformance levels — B-B, B-T (RFC 3161 timestamp), B-LT (embed OCSP + cert chain for long-term validation) and B-LTA (append /DocTimeStamp for archival). Step-by-step with fall-back semantics, browser + server paths, standards citations, and troubleshooting.

PAdES-B-B / B-T / B-LT / B-LTA Open cookbook →

OCSP responder (RFC 6960)

Public docs for the in-tenant RFC 6960 OCSP responder at /csc/v2/ocsp. Answers CertID queries for the per-user signing certs, the TSA responder cert and the OIDC / VCI issuer certs. Powers id-aa-ets-revocationValues inside every PAdES-B-LT / B-LTA envelope.

RFC 6960 · long-term validation Open reference →

SCA (ETSI TS 119 432) + ARF §5.7.5

How the CodeB Remote Signature Service maps onto the ETSI Signature Creation Application role — protocol operations, DTBS composition, SCAL1/SCAL2 activation, and the EU Wallet acting as SAP authoriser via OpenID4VP transaction_data.

ETSI TS 119 432 · EN 419 241-1 · ARF 3.0 Open mapping →

04 / Data & operations

Stream events, archive artefacts, forward audit trails.

Once CodeB is live you will want to react to it. Verify webhook signatures, subscribe to the real-time signalling WebSocket, snapshot recordings and transcripts into your own storage, and forward the audit trail into Splunk, Elastic, Datadog, Loki or Microsoft Sentinel.

Receive webhooks

HMAC-SHA256 signature verification, replay-window enforcement, idempotency-key handling. Snippets for Node/Express, Python/Flask, Go, PHP and ASP.NET Core.

HMAC-verify in 5 stacks Open cookbook →

Real-time WS events

Signal WebSocket consumer patterns — auto-reconnect, backoff, message filtering, per-tenant scope. Track calls, chat messages, presence and admin events without polling REST.

Signal WebSocket consumers Open cookbook →

Compliance archive

Copy signed recordings, transcripts and call-detail records into your own retention store. Recipes for S3-compatible buckets, on-prem SMB and Azure Blob. Integrity re-verification.

Recordings · transcripts · CDR Open cookbook →

SIEM integration

Forward the CodeB audit log into Splunk, Elastic, Datadog, Grafana Loki or Microsoft Sentinel. HEC + Elastic bulk + Datadog logs + Loki push + Sentinel Data Collection Rules.

5 SIEM destinations Open cookbook →

Need something we do not cover yet? The REST API reference and the OIDC endpoint catalogue are the authoritative surfaces — every recipe on this page is a translation of those documents into a shape a developer can paste into an editor.