# IPGeolocation.io — LLM Reference (Full) > This file is a consolidated, AI-oriented reference for IPGeolocation.io products, API endpoints, databases, SDKs, and support/policy pages. Last updated: 2026-01-19 Primary domains: - ipgeolocation.io (marketing + documentation) - api.ipgeolocation.io (API base hostname) - app.ipgeolocation.io (account dashboard) ====================================================================== 1) QUICK PRODUCT MAP ====================================================================== APIs (v2): - IP Geolocation API (geo + optional enrichments) - IP Security API (VPN/proxy/Tor + threat intelligence) - ASN API (ASN details: routes/peers/upstreams/downstreams/raw whois response) - IP Abuse Contact API (abuse contact details) - Timezone API (timezone lookup + time conversion) - Astronomy API (sun/moon & twilight timings) - User Agent API (UA parsing) Databases (download): - IP Geolocation DB - IP Security DB - IP Company DB - IP to ASN DB - IP Abuse Contact DB - IP Whois DB - ASN Whois DB - IP Hosting DB - Residential Proxy DB SDKs: - Language SDKs are published under the IPGeolocation GitHub organization and linked from the documentation hub. ====================================================================== 2) AUTHENTICATION, TRANSPORT, AND RESPONSE SHAPING ====================================================================== Authentication: - Use an API key (apiKey=...) for API calls. - Some use cases can also be authorized by request origin (CORS/origin-based authorization), depending on plan/setup. Transport: - HTTPS endpoints on api.ipgeolocation.io. Common output: - JSON is the default. Some endpoints or features may support additional formats (see product docs). Common response shaping patterns (varies by API): - fields=... (select specific fields/paths; reduces payload) - include=... (include optional objects such as network, location, time_zone, abuse, user_agent) - excludes=... (exclude specific fields/paths) ====================================================================== 3) API: IP GEOLOCATION API (v2) ====================================================================== Docs: - https://ipgeolocation.io/ip-location-api.html - https://ipgeolocation.io/documentation.html Endpoints: - GET https://api.ipgeolocation.io/v2/ipgeo?apiKey=API_KEY&ip=IP_OR_DOMAIN - GET https://api.ipgeolocation.io/v2/ipgeo?apiKey=API_KEY (without ip: returns caller/client info) - POST https://api.ipgeolocation.io/v2/ipgeo-bulk?apiKey=API_KEY (bulk lookup) Key behaviors: - ip can be IPv4/IPv6. Some examples also show passing a domain name. - bulk endpoint accepts a JSON body like: {"ips":["1.1.1.1","1.2.3.4", ...]} - fields can select nested paths such as: - fields=location - fields=location.country_name,network.asn.organization - includes/excludes can be used to enrich or trim response payload. - lang can localize response (plan-dependent; see docs). Typical response shape (high level): - ip - location (country/state/city, lat/long, etc.) - network (asn and/or company details depending on plan and includes) - optional objects based on include/fields ====================================================================== 4) API: IP SECURITY API (v2) ====================================================================== Docs: - https://ipgeolocation.io/ip-security-api.html Endpoint: - GET https://api.ipgeolocation.io/v2/security?apiKey=API_KEY&ip=IP Common enrichments: - include=network (add ASN/company context) - include=location (add geo fields) - include=time_zone (add timezone object) - include=country_metadata (add country metadata as documented) - include=location,network (multiple) Typical response shape (high level): - ip - security (VPN/proxy/Tor/threat-related signals) - optional: location, network, time_zone, country_metadata ====================================================================== 5) API: ASN API (v2) ====================================================================== Docs: - https://ipgeolocation.io/asn-api.html Endpoint: - GET https://api.ipgeolocation.io/v2/asn?apiKey=API_KEY&asn=AS_NUMBER Common enrichments via include=... (as documented): - include=downstreams - include=upstreams - include=routes - include=peers - include=whois_response Typical response shape (high level): - asn object (organization, country, and optional arrays/fields from include=...) Note: - ASN details can also appear inside the IP Geolocation API responses under a network/asn object, depending on plan and fields/include usage. ====================================================================== 6) API: IP ABUSE CONTACT API (v2) ====================================================================== Docs: - https://ipgeolocation.io/ip-abuse-contact-api.html Endpoint: - GET https://api.ipgeolocation.io/v2/abuse?apiKey=API_KEY&ip=IP Response shaping: - excludes can remove specific abuse fields/paths (example docs show excluding abuse.handle, abuse.emails). Also supported via IP Geolocation API enrichment: - GET https://api.ipgeolocation.io/v2/ipgeo?apiKey=API_KEY&ip=IP&include=abuse Typical response shape (high level): - ip - abuse contact details (structure depends on fields/excludes) ====================================================================== 7) API: TIMEZONE API (v2) ====================================================================== Docs: - https://ipgeolocation.io/timezone-api.html Timezone lookup: - GET https://api.ipgeolocation.io/v2/timezone?apiKey=API_KEY&ip=IP - GET https://api.ipgeolocation.io/v2/timezone?apiKey=API_KEY&lat=...&long=... - GET https://api.ipgeolocation.io/v2/timezone?apiKey=API_KEY&location=... - GET https://api.ipgeolocation.io/v2/timezone?apiKey=API_KEY&tz=... - GET https://api.ipgeolocation.io/v2/timezone?apiKey=API_KEY&lo_code=UNLOCODE Time conversion: - GET https://api.ipgeolocation.io/v2/timezone/convert?apiKey=API_KEY&location_from=...&location_to=...&time=... - GET https://api.ipgeolocation.io/v2/timezone/convert?apiKey=API_KEY&iata_from=...&iata_to=... Typical response shape (high level): - timezone identifiers/names - local date/time fields - DST fields where applicable - conversion output for convert endpoint ====================================================================== 8) API: ASTRONOMY API (v2) ====================================================================== Docs: - https://ipgeolocation.io/astronomy-api.html Endpoint: - GET https://api.ipgeolocation.io/v2/astronomy?apiKey=API_KEY&lat=...&long=...&date=YYYY-MM-DD - GET https://api.ipgeolocation.io/v2/astronomy?apiKey=API_KEY&ip=...&date=YYYY-MM-DD Notes: - date must be YYYY-MM-DD; if omitted, current date is used (per docs examples). Typical response shape (high level): - sun timings (sunrise/sunset, twilight begin/end) - moon timings (moonrise/moonset, phase) - additional numeric fields (altitude/azimuth/distance, etc.) as documented ====================================================================== 9) API: USER AGENT API (v2) ====================================================================== Docs: - https://ipgeolocation.io/user-agent-api.html Endpoint: - GET https://api.ipgeolocation.io/v2/user-agent?apiKey=API_KEY Provide the User-Agent string in the HTTP "User-Agent" header. Also supported via IP Geolocation API enrichment: - GET https://api.ipgeolocation.io/v2/ipgeo?apiKey=API_KEY&fields=location&include=user_agent Provide the User-Agent string in the HTTP "User-Agent" header. Typical response shape (high level): - device/OS/browser/engine classification fields - robot/hacker/anonymized indicators where applicable (as documented) ====================================================================== 10) DATABASES (DOWNLOAD) ====================================================================== Docs hub: - https://ipgeolocation.io/documentation/databases.html Database pages: - IP Geolocation Database: https://ipgeolocation.io/ip-geolocation-database.html - IP Security Database: https://ipgeolocation.io/ip-security-database.html - IP Company Database: https://ipgeolocation.io/ip-company-database.html - IP to ASN Database: https://ipgeolocation.io/ip-asn-database.html - IP Abuse Contact Database: https://ipgeolocation.io/ip-abuse-contact-database.html - IP Whois Database: https://ipgeolocation.io/ip-whois-database.html - ASN Whois Database: https://ipgeolocation.io/asn-whois-database.html - IP Hosting Database: https://ipgeolocation.io/ip-hosting-database.html - Residential Proxy Database: https://ipgeolocation.io/residential-proxy-database.html Pricing: - https://ipgeolocation.io/db-pricing.html Formats: - Database offerings commonly include CSV and MMDB options (see each database page for exact formats and field sets). ====================================================================== 11) SDKS AND INTEGRATIONS ====================================================================== Documentation hub: - https://ipgeolocation.io/documentation.html Integrations: - https://ipgeolocation.io/integrations.html GitHub (SDK sources): - https://github.com/IPGeolocation ====================================================================== 12) SUPPORT, STATUS, AND POLICIES ====================================================================== Support: - FAQs: https://ipgeolocation.io/faq.html - Contact: https://ipgeolocation.io/contact.html - Data corrections: https://ipgeolocation.io/corrections.html - Status: https://status.ipgeolocation.io/ - Subprocessors: https://ipgeolocation.io/subprocessors.html Policies: - Privacy: https://ipgeolocation.io/privacy.html - GDPR: https://ipgeolocation.io/gdpr.html - Terms: https://ipgeolocation.io/tos.html Site map: - https://ipgeolocation.io/site-navigation.html