Skip to main content

What you will build

Three synthetic sends per device per day, with growing waits. This is an illustrative application policy, not a default rule that ShieldLabs applies to every customer.

Run the starting application

You need Node.js 22 or later. The starter runs without ShieldLabs keys; the final version needs a registered HTTPS hostname and matching keys. Clone the public tutorial repository, then start this standalone application:
Open http://127.0.0.1:3000. The starter has no ShieldLabs dependency or identification check. Its own SQLite state is separate from every other tutorial.
The completed application uses browser SDK 1.1.0 and Node SDK 1.3.0. Its browser helper reads result.identificationId; requestId is the tutorial application’s own submitted field. Its server reads a domain-scoped identification card and requires available risk and signal states before applying the action policy. An unavailable state is not a clean score or a negative signal. See History for the response contract.

Add the integration

Stop the starter server. Follow these changes, then run the complete implementation from the final branch.
1

1. Prepare the keys and HTTPS hostname

The .env copied from starter contains no key entries yet. Add the three lines below with this domain’s real values:
Get the public domain UUID for this hostname using GET /api/v1/domains with the Private API Key, or OAuth MCP shieldlabs_list_domains. Copy its id into SHIELDLABS_DOMAIN_ID; do not substitute the hostname.Register the app’s hostname in Integration > Domains. Put its matching Public Key and Private API Key in the private sms-pumping/.env as SHIELDLABS_PUBLIC_KEY and SHIELDLABS_API_KEY. Resolve that hostname through GET /api/v1/domains with the Private API Key, or OAuth MCP shieldlabs_list_domains, and set its public UUID as SHIELDLABS_DOMAIN_ID. Serve this app through HTTPS on that registered hostname. The Private API Key stays on the server; a customer key does not automatically authorize localhost.
2

2. Identify the action in the browser

The protected page loads the locally served JS SDK. In public/index.js, each action takes a fresh Identification ID and sends it with the action. requestId is this application’s payload field; the browser helper reads result.identificationId from the SDK:
Only the Identification ID goes to the server; the browser does not supply the risk result.
3

3. Verify the identification on the server

server/shieldlabs.js uses @shieldlabs-ai/node and the Private API Key to find that exact Identification ID in History. The action route passes it to server/sms.js, where verifyIdentification(identificationId) rejects missing, stale, replayed, automated or unusable checks before this scenario’s rule is applied.
4

4. Apply the verification sends rule

This excerpt from server/sms.js shows the decision’s core:
server/sms.js verifies the check, refuses Tor, and limits sends by Device ID across phone numbers. The demo returns the generated six-digit code in its response instead of sending an SMS; the code expires after ten minutes.
5

5. Run the completed application

From the repository root, compare the two versions and start the final app:
A fresh clone has the remote origin/final ref even before its local final branch exists. Open the completed app through the registered HTTPS hostname. The Node server listens on 127.0.0.1:3000 behind your reverse proxy.

Follow the integration code

The completed source is in the sms-pumping application. Read these files in order:
  1. Browser helper: loads the installed SDK, serializes checks and returns an Identification ID.
  2. Server verification: reads real History, checks the matching ID, waits within a bounded budget for pending results and rejects unusable or replayed checks.
  3. Scenario decision: applies this app’s rule using the verified identification and stores its sample state.
The finished application keeps its browser, server and SQLite state inside this folder. The tests use synthetic History responses; the normal server does not manufacture a successful identification.

Try the completed application

  1. Request a sample code for a made-up number in the supported format. Read the demo code in the app and verify it.
  2. Request another code with a fresh identification. If the cooldown is active, the app tells you how long to wait.
  3. Changing the phone number does not reset the device counter. Use npm test for the 30/60-second waits and Tor branches without exhausting live checks.
Use Reset demo DB with DEMO_ALLOW_RESET=1 to repeat the exercise. These controls are for a disposable demonstration, not production authorization.

Check your result

In DevTools Network, inspect the /api/send-code request and copy its requestId. Compare Identification IDs for /api/send-code in History. The local sms_codes rows use the verified Device ID; no real SMS provider is contacted. Run npm run check and npm test from sms-pumping to exercise failure cases locally without making more identifications. For a real run, obtain fresh Identification IDs in the browser and confirm their Device IDs and signals in History. If identification returns HTTP 429, stop and respect the returned retry guidance; the status alone does not establish exhausted plan volume. A cookie change does not prove that the Device ID changed: compare the History rows.

Adapt it to your product

This example is a starting point, not a production-ready authorization system. Bind each action to an authenticated session where appropriate, authorize administration screens, persist state and atomically consume Identification IDs across all server instances. Review legitimate shared-device behavior before applying a device-based restriction. See Acting on results.