IP2WHOIS
IP2WHOIS is a domain WHOIS lookup API from IP2Location that returns registrant, registrar, and registration details for any domain name. It resolves a domain into structured WHOIS data, including creation, update, and expiration dates, domain age, nameservers, and contact records for the registrant, administrative, technical, and billing roles.

Power end-to-end data operations for your IP2WHOIS API with Nexla. Our bi-directional IP2WHOIS connector is purpose-built for IP2WHOIS, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to IP2WHOIS or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your IP2WHOIS workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating an IP2WHOIS credential, you need an IP2WHOIS API key. IP2WHOIS is provided by IP2Location and offers a free tier that does not require a credit card. The API key authenticates every request to the WHOIS lookup endpoint.
To obtain your IP2WHOIS API key, follow these steps:
-
Navigate to the IP2WHOIS registration page and sign up for a free account, or sign in if you already have one.
-
After signing in, open your account dashboard to locate your API key. The free plan includes a monthly quota of WHOIS lookups, with higher volumes available on paid plans.
-
Copy the API key and store it securely, as you will need it to configure your Nexla credential.
Nexla sends the API key to IP2WHOIS as a bearer token in the Authorization request header. For complete details about the API, response fields, and supported top-level domains, see the IP2WHOIS API documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key | Yes | Yes | API key used to authenticate requests to the IP2Whois API. |
Create a credential in Nexla
-
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your IP2WHOIS API key in the API Key field. This key authenticates Nexla with IP2WHOIS and is sent as a bearer token in the
Authorizationheader for all API requests. Keep this value confidential.If your API key is compromised, regenerate it from your IP2WHOIS account dashboard and update the credential in Nexla. For more information about the API and your usage quota, see the IP2WHOIS API documentation.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the IP2WHOIS connector tile, then select the credential that will be used to connect to IP2WHOIS, and click Next; or, create a new IP2WHOIS credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common IP2WHOIS endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
IP2WHOIS data sources can also be manually configured to ingest data from any valid IP2WHOIS API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new IP2WHOIS data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.