1. Create a ShieldLabs account and get your API key
- Start Free to create your account, or sign in.
- Open Integration > Domains and add your website’s hostname, such as
example.com. - Select the domain and open Integration > API keys.
- Copy its Public Key. You will use it as
PUBLIC_API_KEYin the browser examples below.
2. Add ShieldLabs to your website
Choose a guide for your frontend. Each guide covers installation, configuration and a first check.JavaScript
Step-by-step browser setup
React
Provider and identification hook
Next.js
Client components and server integration
Vue
Plugin and identification composable
Angular
Provider and identification helper
Svelte
Context and SvelteKit integration
PUBLIC_API_KEY with the Public Key you copied in step 1. For a website without a build step, follow Install the snippet.
3. Identify your first visitor
Callidentify() when a visitor takes the action you want to protect, such as signing up, logging in or checking out:
identificationId identifies this check. The JavaScript guide shows a complete working page with a button, error handling and the result displayed on screen.
For a signed-in user, pass the stable pseudonymous account ID supplied by your backend:
4. View the result in the analytics dashboard
- Open your website on the registered domain and run the check.
- Open Analytics > Identifications in the analytics dashboard.
- Find the check by its Identification ID and open the identification card.
- Review the Risk Score, risk signals, identifiers and device and network details.
5. Connect the result to your backend
Send theidentificationId with the action your application handles. Your server retrieves the identification using the domain’s Private API Key, available under Integration > API keys.
Choose your backend guide:
Node.js
History reads and webhook verification
Python
Sync and async clients
Go
Context-aware reads and webhooks
PHP
Composer and server handlers
Java
Maven or Gradle and typed results
.NET
NuGet and ASP.NET Core
SHIELDLABS_API_KEY in your server environment, then read the result:
Keep the Private API Key on your server. For push delivery, configure signed webhooks. The data model reference explains the fields available through each delivery method.
Next steps
Protect your first action
Use verified risk results at signup, login or checkout.
Use case tutorials
Build a complete example for your use case.
Content Security Policy
Allow the connections needed by the browser SDK.
Playground
Explore identification and risk results.