curl -X POST https://verification.didit.me/v3/ip/risk/ \
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"ip_address": "8.8.8.8",
"claimed_country": "ESP",
"user_agent": "Mozilla/5.0",
"vendor_data": "lead-123"
}'from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.ip.assess_risk(
ip_address="8.8.8.8",
)
print(result)import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.ip.assessRisk({
ip_address: "8.8.8.8",
});
console.log(result);ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.IP.AssessRisk(ctx, didit.IPAssessRiskParams{
Body: didit.IPRiskRequest{
IPAddress: "8.8.8.8",
},
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)import me.didit.Didit;
import me.didit.types.IPRiskRequest;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.ip().assessRisk(IPRiskRequest.builder()
.ipAddress("8.8.8.8")
.build());
System.out.println(result);<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->ip->assessRisk([
'ip_address' => '8.8.8.8',
]);
print_r($result->toArray());require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.ip.assess_risk(ip_address: "8.8.8.8")
puts result.to_husing System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.Ip.AssessRiskAsync(new IPRiskRequest
{
IpAddress = "8.8.8.8",
});
Console.WriteLine(JsonSerializer.Serialize(result));{
"request_id": "9a96ed2a-721e-4b86-8cbf-d61eda529279",
"status": "Approved",
"ip": {
"status": "Approved",
"ip_address": "192.0.2.10",
"ip_country": "Spain",
"ip_country_code": "ES",
"ip_state": "Madrid",
"ip_city": "Madrid",
"latitude": 40.4168,
"longitude": -3.7038,
"isp": "Example Telecom",
"organization": "Example Telecom SA",
"is_vpn_or_tor": false,
"is_data_center": false,
"time_zone": "Europe/Madrid",
"time_zone_offset": "+0200",
"asn_number": 3352,
"asn_organization": "EXAMPLE-TELECOM",
"connection_type": "broadband",
"carrier": "Example Telecom",
"proxy_type": null,
"claimed_country": "ESP",
"country_mismatch": false,
"threat": {}
},
"vendor_data": "lead-123",
"metadata": null,
"created_at": "2026-09-01T10:30:00.123456+00:00"
}IP Risk API: Geo, VPN & Datacenter Signals
Risk-score an IP address with geolocation, ISP, VPN/Tor, datacenter, threat, and claimed-country mismatch signals.
curl -X POST https://verification.didit.me/v3/ip/risk/ \
-H 'x-api-key: YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"ip_address": "8.8.8.8",
"claimed_country": "ESP",
"user_agent": "Mozilla/5.0",
"vendor_data": "lead-123"
}'from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.ip.assess_risk(
ip_address="8.8.8.8",
)
print(result)import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.ip.assessRisk({
ip_address: "8.8.8.8",
});
console.log(result);ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.IP.AssessRisk(ctx, didit.IPAssessRiskParams{
Body: didit.IPRiskRequest{
IPAddress: "8.8.8.8",
},
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)import me.didit.Didit;
import me.didit.types.IPRiskRequest;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.ip().assessRisk(IPRiskRequest.builder()
.ipAddress("8.8.8.8")
.build());
System.out.println(result);<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->ip->assessRisk([
'ip_address' => '8.8.8.8',
]);
print_r($result->toArray());require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.ip.assess_risk(ip_address: "8.8.8.8")
puts result.to_husing System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.Ip.AssessRiskAsync(new IPRiskRequest
{
IpAddress = "8.8.8.8",
});
Console.WriteLine(JsonSerializer.Serialize(result));{
"request_id": "9a96ed2a-721e-4b86-8cbf-d61eda529279",
"status": "Approved",
"ip": {
"status": "Approved",
"ip_address": "192.0.2.10",
"ip_country": "Spain",
"ip_country_code": "ES",
"ip_state": "Madrid",
"ip_city": "Madrid",
"latitude": 40.4168,
"longitude": -3.7038,
"isp": "Example Telecom",
"organization": "Example Telecom SA",
"is_vpn_or_tor": false,
"is_data_center": false,
"time_zone": "Europe/Madrid",
"time_zone_offset": "+0200",
"asn_number": 3352,
"asn_organization": "EXAMPLE-TELECOM",
"connection_type": "broadband",
"carrier": "Example Telecom",
"proxy_type": null,
"claimed_country": "ESP",
"country_mismatch": false,
"threat": {}
},
"vendor_data": "lead-123",
"metadata": null,
"created_at": "2026-09-01T10:30:00.123456+00:00"
}POST /v3/ip/risk/ when your backend already has an IP address and needs a server-to-server risk decision.
The response includes geolocation, network ownership, VPN/Tor and data-center flags, threat data, and country_mismatch when you send a claimed country.
Interpret the response
statusisIn Reviewwhen the resolved country conflicts withclaimed_country, or when the address is associated with VPN, Tor, or data-center infrastructure. Otherwise it isApproved.ip.ip_country_codecontains the resolved country code. Compare countries throughip.country_mismatchinstead of comparing raw country strings yourself.ip.latitudeandip.longitudeare approximate network geolocation, not a precise device location.ip.is_vpn_or_tor,ip.is_data_center,ip.proxy_type, andip.threatcarry network-risk evidence.ip.asn_number,ip.asn_organization,ip.connection_type, andip.carrierdescribe the network the address belongs to.request_idis the API session id. Store it withvendor_dataif you need to correlate the result with later webhooks or console activity.
ip.ip_address: null, ip.country_mismatch: null, and an empty ip.threat object. Individual enrichment fields can also be null when unavailable.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, includingdevice_fingerprint, device and browser details, user_agent, raw device data, and cross-session matches.
Sandbox behavior
Sandbox keys validate the request and return deterministic approved data. They do not contact external intelligence services, consume credits, create a session, or contribute to Networks.Billing
IP Risk API calls cost $0.02 at list price. A live request is billable once the lookup starts.Authorizations
Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.
Headers
Optional retry-safety key you choose for one operation, up to 255 characters (a UUID works). A request repeated with the same key, endpoint, query and body is answered with the first response, same status and same body, and runs and bills nothing a second time. The same key with another endpoint, query or body returns 409 idempotency_key_reused, and while the first request is still running, 409 idempotency_key_in_progress with Retry-After. A failed request (any 4xx or 5xx) is not stored, so you can send it again with the same key. Keys belong to your application, whether you call with an API key or an access token. See Retries and idempotency.
1 - 255Body
Response
The risk evaluation completed. Inspect status for the decision; HTTP is always 200 for completed lookups.