SDKs

Stile's public integration surfaces split cleanly by where your code runs. A typical integration uses the hosted widget in the browser and direct HTTPS from your backend. This works with any server language and requires no Stile package installation.

Hosted widget

The public frontend half of an integration. Load <stile-frame> from the CDN with a single script tag. The widget handles the camera, document capture, and the entire verification UI — your page supplies a backend session-url and listens for provisional UI events while your server waits for the signed webhook.

<script src="https://js.stile.id/v1/stile.js"></script>

The repository's @stile/widget package also contains <stile-button>, verify(), and create(), but it is currently private and not published to public npm. See the Widget reference for the public contract and private-preview boundary.

Node.js SDK private preview

@stile/node is not published to public npm. It is a private-preview convenience wrapper whose methods map 1:1 to the HTTP API. Use direct HTTPS for public integrations. Only use the package when Stile has explicitly provided package access and version-specific setup instructions.

Which do I need?

• Gating a checkout or signup? Use the hosted widget on the frontend, direct HTTPS for session creation, and a signed webhook on the backend. Start with the Quickstart.
• Creating sessions from any backend? POST to the Verification Sessions API, then return the client_secret through your authenticated session-url endpoint.
• Invited to the Node.js private preview? Use the Node.js reference with the access instructions Stile provided.

Next steps