The 4.0 migration guide (world-id/4-0-migration.mdx, lines 248-299) presents IDKit.createSession(...) / IDKit.proveSession(sessionId, ...) as the way to adopt World ID 4.0 Session Proofs, and tells apps with a 'Recurring Verifications' pattern to migrate onto this API — but there is no dedicated reference page anywhere in the docs for the Session Proofs JS builder API or an equivalent React hook/widget. A developer following the migration guide has nowhere to go for the actual API surface (params, return shape, error cases, session lifetime/expiry semantics).
Needs: a new reference page under world-id/idkit/ covering the Session Proofs API end-to-end (mirroring the depth of world-id/idkit/verification-flows.mdx), cross-linked from integrate.mdx, credentials.mdx, and 4-0-migration.mdx. This needs input from whoever owns the Session Proofs feature to confirm the full API surface, error modes, and session-expiry behavior — flagged as a docs audit finding rather than opened as a PR because it requires new subject-matter content, not a mechanical text fix.
The 4.0 migration guide (
world-id/4-0-migration.mdx, lines 248-299) presentsIDKit.createSession(...)/IDKit.proveSession(sessionId, ...)as the way to adopt World ID 4.0 Session Proofs, and tells apps with a 'Recurring Verifications' pattern to migrate onto this API — but there is no dedicated reference page anywhere in the docs for the Session Proofs JS builder API or an equivalent React hook/widget. A developer following the migration guide has nowhere to go for the actual API surface (params, return shape, error cases, session lifetime/expiry semantics).Needs: a new reference page under
world-id/idkit/covering the Session Proofs API end-to-end (mirroring the depth ofworld-id/idkit/verification-flows.mdx), cross-linked fromintegrate.mdx,credentials.mdx, and4-0-migration.mdx. This needs input from whoever owns the Session Proofs feature to confirm the full API surface, error modes, and session-expiry behavior — flagged as a docs audit finding rather than opened as a PR because it requires new subject-matter content, not a mechanical text fix.