Skip to main content
Use POST /v3/ip/risk/ when your backend already has an IP address and needs a server-to-server risk decision. The response includes geolocation, ISP and organization, VPN/Tor and datacenter flags, provider threat data, and country_mismatch when you send a claimed country.

Request

Response

Device intelligence

The IP Risk API is a pure server-to-server endpoint. Device fingerprinting is not, because a backend cannot observe browser or device signals by itself. For hosted-flow and SDK sessions, Didit exposes the already collected device fields on the session response, including device_fingerprint, device_brand, device_model, browser and OS versions, user_agent, raw_device_data, and cross-session matches. A separate collector-plus-exchange device API would require a browser or native collector and is outside this endpoint.

Billing and providers

IP Risk API calls use ip_risk_api pricing. It reuses Didit’s existing IP enrichment path and cached network-address data where available. Sandbox mode returns deterministic mock risk data and never spends managed provider credentials.