Custom Connector
IP-API Location Intelligence Connector
Global
The IP-API Location Intelligence Connector provides a RESTful interface to retrieve detailed location-based data for a given IP address. Powered by the IP-API service, it delivers geolocation (latitude/longitude), ISP, timezone, region, and city — ideal for geofencing, analytics, content localization, security applications, or traffic auditing.
Overview
Integration Overview
The IP-API Location Intelligence Connector offers the following integration points:
- queryIP. Fetch geolocation data for a specific IP.
- queryBulkIPs. Bulk IP geolocation for multiple addresses.
- getStatus. Monitor the service health and quota.
Documentation
Detailed Integration Documentation
Query IP Address
| Action | queryIP |
|---|---|
| Purpose | Retrieves detailed geolocation data for a single IP address. |
| Parameters | Required: ip – IPv4 or IPv6 address (path parameter). |
| Configuration | Configure the connector with the correct base URL. |
| Output | Successful: JSON object with fields such as country, city, latitude, longitude, ISP, timezone. |
| Workflow example | Use this to localize the user experience, verify IP origin, or plot user distribution on maps. |
Query Multiple IPs
| Action | queryBulkIPs |
|---|---|
| Purpose | Retrieve geolocation data for multiple IP addresses in one request. |
| Parameters | Required: Request body (JSON array): each item must contain a query field with the IP address to locate. |
| Configuration | Configure the connector with the correct base URL. |
| Output | Successful: JSON array of geolocation results. |
| Workflow example | Use during traffic analysis where many IPs need location resolution, or for historical log audits. |
Check System Status
| Action | getStatus |
|---|---|
| Purpose | Checks the current system quota and validates whether the API service is operational. |
| Parameters | Required: None. |
| Configuration | Configure the connector with the correct base URL. |
| Output | Successful: JSON with API status, query IP, and remaining request quota. |
| Workflow example | Use to avoid exceeding daily limits and trigger alerts when nearing usage caps. |
Example Workflow: Visitor Location Analytics Platform
| Capture IP | Capture the client IP address during a session or request. |
|---|---|
| Fetch geolocation | Use queryIP (/json/{ip}) to fetch geolocation info. |
| Respect limits | Use getStatus (/check) periodically to ensure request limits are respected. |
| Bulk logs | For analytics on bulk logs, use queryBulkIPs (/batch) to geolocate IPs efficiently. |
| Visualize | Display aggregated geolocation data on maps or charts. |
Support
For technical support, contact custom-connectors-support@isolutions.sa.