IPstack icon

IPstack

Get IP geolocation data using IPstack API
Join our community

Actions3

Overview

This node integrates with the IPstack API to provide geolocation data for IP addresses. It is useful for scenarios where you need to enrich data with location information based on IPs, such as fraud detection, content localization, or network diagnostics.

The Standard Lookup operation allows you to query detailed geolocation information for a single IPv4 or IPv6 address. You can customize the response by specifying additional fields, language preferences, and enabling hostname or security threat lookups.

Practical examples:

  • Enriching user sign-up data with their geographic location.
  • Verifying the origin of suspicious login attempts.
  • Displaying localized content based on visitor IP.

Properties

Name Meaning
IP Address The single IP address (IPv4 or IPv6) to look up.
Additional Fields A collection of optional parameters to customize the lookup:
- Fields Comma-separated list of specific fields to return from the API response.
- Language Language code for the API response. Options: Chinese, English, French, German, Japanese, Portuguese (Brazil), Russian, Spanish. Default is English.
- Enable Hostname Lookup Boolean flag to include hostname information in the response.
- Enable Security Module Boolean flag to include security threat information related to the IP address.

Output

The node outputs JSON data containing the geolocation details returned by the IPstack API for the queried IP address. This includes standard IP location fields such as country, region, city, latitude, longitude, and optionally hostname and security threat info if enabled.

If an error occurs during the API request, the output JSON will contain an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires an API key credential for the IPstack service.
  • The node makes HTTP GET requests to the IPstack API endpoint (http://api.ipstack.com or https://api.ipstack.com depending on configuration).
  • The API key must have appropriate permissions to access the requested data.
  • Network connectivity to the IPstack API is required.

Troubleshooting

  • Maximum IPs exceeded: When using bulk operations (not applicable here but relevant generally), the node throws an error if more than 50 IPs are provided.
  • API errors: If the IPstack API returns an error (e.g., invalid IP, quota exceeded, or authentication failure), the node throws an error with details from the API response.
  • Invalid IP format: Providing an improperly formatted IP address may cause the API to return an error.
  • Network issues: Connectivity problems to the IPstack API endpoint will result in request failures.
  • To handle errors gracefully, enable "Continue On Fail" in the node settings to receive error details per item instead of stopping execution.

Links and References

Discussion