BlogAPI designUpdated

One route. Two depths.

API 2.1 returns the profile data your plan includes at its natural field paths, with a complete everyday answer on Free.

An integration shouldn't need a rewrite when you decide you want more detail. If your app already reads the country and ASN from an IP lookup, those fields should stay where they are.

In API 2.1.0, a lookup returns the profile data your plan includes. Free returns the complete everyday answer. Paid plans include their additional profile fields automatically, through the same route:

GET /ip/8.8.8.8
X-API-Version: 2.1.0

On an eligible paid plan, the response includes fields such as datacenter, relay and tor at the root of the IP record. There is no response deep object. Code that reads country keeps working, and new code can read datacenter directly. Existing explicit deep requests and earlier API versions retain their behavior. No depth option is needed for the API 2.1 paid default.

Missing and unknown are different

Profile fields can be absent when they were not selected or are unavailable to the plan or key. An included field can be null when its value is unknown. Known false and zero values keep their own meanings.

The same rule applies within a distinct resource. Additional Weather observations join current, and Domain registration details live in registration. Each result in a list carries its own additional fields. The plan's profile determines the included detail without creating another layer in the JSON.

Profile detail is included on paid plans within the ordinary pooled request allowance. Existing accounts keep their current profile access. Complete small answers such as Language and Currency do not need a depth option. Check the endpoint reference for the useful details available to the operation you use.

Verification is a separate operation

Mailbox verification uses GET /email/verify with an email in the JSON body and the Email verification allowance. The result also contains the basic validation fields, so you do not need to call both Email operations.

Carrier and HLR return the complete selected metered answer without a depth option or a second check charge. Phone formatting does not silently buy either check. Choose the operation whose answer changes what your application needs to do.

Profile data follows the plan. Separate checks remain deliberate operations, and their fields stay at their natural homes.