Domain WHOIS Lookup AI Agent / LLM

# Domain WHOIS Lookup API — Way2API®

- **Endpoint:** `POST https://app.way2api.com/api/v1/domain/whois`
- **Auth:** `Authorization: Bearer YOUR_API_KEY` (or `X-API-Key: YOUR_API_KEY`)
- **Content-Type:** `application/json`
- **Category:** Domain Intelligence and Analysis
- **Availability:** Available worldwide
- **Docs:** https://app.way2api.com/documentation/domain-whois-lookup-v2

## What it does

Domain WHOIS Lookup API — live registry WHOIS for any domain. Returns registration dates (created, updated, expires), the registrar with its IANA ID and abuse contact, the full registrant contact — organisation, name, email, phone and postal address — name servers, and the domain's EPP status codes. Registrant fields are returned exactly as the registry publishes them: privacy-protected or GDPR-redacted domains come back with the redacted fields empty rather than as an error, and unregistered names return is_registered = false with empty detail fields. Built for domain monitoring, expiry alerting, brand protection and due diligence. Raw WHOIS text is deliberately not returned — every field is parsed and normalised. It is a v2 API, an improvement on the v1 API.

## Request body (application/json)

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `domain_name` | string | yes | Domain name to query, e.g. example.com. A scheme, path or www. prefix is stripped automatically. Max 253 characters. |

## Example request

```bash
curl -X POST https://app.way2api.com/api/v1/domain/whois \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain_name":"way2api.com"}'
```

## Success response — 200

```json
{
    "status": "SUCCESS",
    "status_code": 200,
    "charged": true,
    "success": true,
    "message": "",
    "message_code": "OK",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "result": {
            "domain_name": "way2api.com",
            "is_registered": true,
            "created_on": "2024-03-03",
            "updated_on": "2026-02-21",
            "expires_on": "2031-03-03",
            "registrar": {
                "name": "GoDaddy.com, LLC",
                "iana_id": "146",
                "url": "http://www.godaddy.com",
                "abuse_email": "[email protected]",
                "abuse_phone": "+14806242505"
            },
            "registrant": {
                "registry_id": "way2apicom-reg",
                "name": "Registration Private",
                "organization": "Domains By Proxy, LLC",
                "email": "",
                "phone": "+14806242599",
                "street": "DomainsByProxy.com 100 S. Mill Ave, Suite 1600",
                "city": "Tempe",
                "state": "Arizona",
                "zip_code": "85281",
                "country": "United States",
                "country_code": "US"
            },
            "technical_contact": {
                "email": ""
            },
            "name_servers": [
                "magnolia.ns.cloudflare.com",
                "charles.ns.cloudflare.com"
            ],
            "domain_status": [
                "client_update_prohibited",
                "client_delete_prohibited",
                "client_renew_prohibited",
                "client_transfer_prohibited"
            ],
            "queried_at": "2026-08-06 05:53:51"
        }
    }
}
```

## Error response — 400

```json
{
    "status": "FAILED",
    "status_code": 400,
    "charged": false,
    "success": false,
    "message": "We are not providing the whois of this domain extension (local)",
    "message_code": "REQUEST_FAILED",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "error_code": "Not Supported Domain extension"
    }
}
```

## Integration rules

- Every response is JSON carrying `status`, `status_code`, `charged`, `success`, `message`, `message_code` and (once a call reaches the provider) `order_id`. The verification payload is under `data.result`.
- `charged` (boolean) is the authority on billing. Do NOT infer it from the HTTP status: `422` is returned both for input we rejected (not charged) and for a lookup the provider ran and billed us for that returned a negative result (charged).
- `message_code` is a fixed vocabulary — branch on it instead of parsing `message`. Values: `OK`, `ACCEPTED`, `PROVIDER_NO_RESPONSE`, `VERIFICATION_FAILED`, `NO_RECORD_FOUND`, `INVALID_INPUT`, `REQUEST_FAILED`, `MISSING_API_KEY`, `INVALID_API_KEY`, `INSUFFICIENT_BALANCE`, `NO_API_ACCESS`, `NOT_FOUND`, `RATE_LIMITED`, `INTERNAL_ERROR`, `PROVIDER_UNAVAILABLE`.
- `success` reports the verification outcome; `status` reports the ORDER lifecycle (`SUCCESS`/`PENDING`/`FAILED`). They differ on a charged negative result: the order completed and was billed while the verification did not pass.
- A failed verification is still a successful HTTP call — the outcome lives in the response body, so do not treat `200` as "verified".
- Status codes: `200` result returned, `202` pending or provider did not respond (both charged — quote the `order_id`), `401` missing/invalid key, `402` insufficient balance, `403` no access to this service, `422` see `charged`, `429` rate limited (honour the `Retry-After` header), `503` temporarily unavailable.
- Rate limits are per API key, per service, on a 1-minute sliding window.
- Load the API key from an environment variable or secret store. Never hard-code it, never commit it, and never ship it in client-side code — calls must be made from your backend.