Skip to main content
Combine automation detection with per-account and per-device send limits.

​
Where to integrate

Identify before your backend calls the messaging provider. Start with the SDK for your stack and retrieve the result on your backend.

​
What to read

Read the verified device and score, then check recent send attempts and completion rates in your own records. Use the current Risk Score and flags, plus High-Risk Events where relevant. Treat a missing or incomplete result as an explicit unverified state.

​
How to act

Reserve a permitted send atomically, or require another verification step. Apply destination and provider spending controls as well. A browser check supplies device evidence, while your send ledger tracks messaging cost.

​
Build the example

The runnable tutorial includes the starting app, the completed integration, and steps to test its behavior. Its application policy is stated separately from ShieldLabs detection. For implementation details, see Acting on results and Identification flow. Verify the expected domain, result age and account association, and consume protected actions atomically.