Skip to main content
A Credential is a statement an issuer makes about a World ID holder. In IDKit, the credential you request determines what the user proves to your application.

What you can request with IDKit

You can also add a liveness check to any preset with require_user_presence.
If you have an existing legacy integration, see the World ID 4.0 migration guide.

SDK presets

This page focuses on preset helpers for common credential requests: proofOfHuman, passport, selfieCheckLegacy, identityCheck, and the legacy presets. The snippets below use rp_context as if it was already generated and signed by your backend. See Integrate IDKit for the full RP-signing flow.

Proof of Human

Use proofOfHuman for the current World ID 4.0 Proof of Human credential. The preset also includes legacy Orb fallback for users who do not yet have a World ID 4.0 proof available.

Passport

Use passport for the current World ID 4.0 Passport credential. The preset also includes legacy Document fallback for users who do not yet have a World ID 4.0 proof available.

Selfie Check

Selfie Check is available through the legacy preset today and returns a World ID 3.0 proof. World ID 4.0 support is rolling out soon. Learn more in Selfie Check.
Selfie Check is currently available to select partners. To discuss access or learn more, please contact us.

Identity Check (Preview)

Identity Check is currently in preview. If you’re interested in using or learning more about Identity Check, please contact us.
Identity Check lets your app ask the user to attest that document-backed attributes match your policy, without asking you to handle the underlying document data. Use it for eligibility checks such as minimum age, document type, issuing country, or nationality. You can request attributes such as:
Successful Identity Check responses include identity_attested so your backend can distinguish whether the requested attributes matched.

User presence and liveness

To check for user presence and liveness, add the require_user_presence flag to your request. This is a request-level flag, not a credential; it asks World ID for a fresh liveness check before returning the proof and fails with user_presence_failed if the check is not completed. Depending on the credential requested, World ID matches the user’s live selfie to the credential image, such as the passport photo or the image captured during Orb verification.

Other legacy presets

These presets only return World ID 3.0 proofs. Keep them for existing integrations or when you specifically need the older verification level.
PresetWhat it requests
orbLegacyOrb verification.
secureDocumentLegacyAt least a Secure Document verification. Returns the user’s highest legacy credential: Secure Document or Orb.
documentLegacyAt least a Document verification. Returns the user’s highest legacy credential: Document, Secure Document, or Orb.
deviceLegacyAt least a Device verification. Returns the user’s highest legacy credential: Device, Document, Secure Document, or Orb.

Common parameters

ParameterWhere it is usedDescription
signalPresetsBinds application context into the proof, such as a user ID or wallet address. Your backend should enforce the same value.
allow_legacy_proofsRequest config and widgetsRequired for request flows. Set to true while accepting World ID 3.0 fallback proofs; set to false for World ID 4.0-only requests.
require_user_presenceRequest config and widgetsOptional liveness step. Defaults to false.