GetClickInfo

Docs

Quickstart

A clear path from example to integration. Keep credentials on your server, handle missing fields, and test failure cases before going live.

  1. Get API access — create a Free account and copy the key (shown once).
  2. Run a documented request — POST /api/v1/lookup with X-API-Key.
  3. Add your application rules — treat signals as context, not automatic blocks.

Integration brief

Endpoint: POST {ORIGIN}/api/v1/lookup
Auth: header X-API-Key: $SIGNALLAYER_API_KEY
Body JSON:
  ip | q          required string (IPv4/IPv6)
  user_agent      optional string (end-user UA)
Response:         ipapi.is-shaped JSON (nested asn, location, company, …)
Errors:
  401 invalid/missing key
  429 daily or burst limit
Missing fields:
  absent or null means unavailable — do not treat as false/clean
Never ship the API key in browser bundles.

cURL

curl -sS -X POST "https://YOUR_HOST/api/v1/lookup" \
  -H "X-API-Key: $SIGNALLAYER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"ip":"8.8.8.8","user_agent":"Mozilla/5.0"}'

Supported fields (verified)

Location

location.country, location.country_code, location.state, location.city, location.latitude, location.longitude, location.timezone, location.zip — IP-derived estimates when coverage exists.

Network

asn (nested), company, datacenter, hostname, connection_type, is_vpn, is_proxy, is_datacenter, is_tor, is_bogon, is_mobile.

User-agent / automation

is_crawler, crawler_name, is_bot, bot_status — from IP ranges and/or supplied User-Agent when sent. Describes the client string, not a unique device.

Risk

risk_signals.combined_bucket (LOW/MEDIUM/HIGH), plus nested UA/ASN/context scores when enrichment runs. Also is_abuser, abuse_age.

Coverage and limitations

What this API does not claim

An IP does not identify a person. Geolocation is not GPS. VPN/proxy/datacenter flags do not prove fraud. A missing field is unavailable — never silently treat it as a reassuring false.

Localization

Suggest a region from country_code when present, and always let the user change it.

Signup review

Combine is_vpn/is_proxy/is_datacenter/is_bot/risk_signals with your own app events. Prefer review queues over automatic hard blocks as a default.

User-agent parsing

Send the end-user User-Agent on lookups to improve crawler/bot classification. Keep raw UAs out of marketing analytics.

Data handling

Demo vs production

The public playground uses /api/v1/demo/lookup (rate-limited, no customer key). Production traffic must use /api/v1/lookup with X-API-Key. Do not send lookup payloads to third-party LLM services merely to generate explanations.

Get API access Open playground