DOCS
Deep ID SDK vs API: how to choose
Use the SDK when you need device identity and mobile integrity signals. Use the API when you need server-side enrichment, scoring, and policy enforcement.
Recommended architecture
Generate the device ID on the client, then send it to your server. Use the API to fetch signals and score risk, then apply policies in your backend.
Related resources
When to use the SDK
You need device identity, mobile integrity signals, and client-side context.
You want to detect tampering, emulators, and mobile-first fraud tooling.
You need SIM binding and SIM anomaly intelligence in OTP flows.
When to use the API
You want server-side enrichment and risk scoring across events.
You need a single place to apply policies for signup, login, checkout, and promotions.
You want to store decisions and outcomes for monitoring and analytics.