ParseAPI Deep
Simple by default.
Deep by choice.
A great answer gets you started.
The right detail takes you further.
Meet deep data. Richer profiles, useful context and verification,
one ?deep=true away.
ONE SMALL CHANGE
Go a little deeper.
Keep the call you know. Reveal what comes next.
THE SAME QUESTION. MORE CONTEXT.
Is this domain available?
Already registered.
See its registrar, registration dates and status. The context behind the answer, together in one response.
Registration detail is included on paid plans.
Domain reference/domain/gmail.com{"domain": "gmail.com","available": false}
DESIGNED FOR DEVELOPERS
Start with the answer.
A domain lookup tells you whether a name is available. Add Deep for its registrar and registration dates.
A useful answer from the first call. More detail when you need it. All through the interface you already know.
Useful defaults.
The result and the context your app needs to use it.
Detail on request.
Add ?deep=true for profiles, specifications or verification.
The same call.
Extra fields go under deep. The core fields keep their values.
ROOM TO GO FURTHER
A lighter start.
A richer answer.
Small responses are easier to read and carry less data. Deep adds the context when you need it.
in the Domain example
DETAIL THAT DOES SOMETHING
Context you can build with.
Registration dates. Vehicle specifications. Forecasts. Choose the detail your app needs.
WHAT IS INCLUDED
Depth is a choice.
Pricing stays clear.
One setting for more detail. What it costs depends on the work behind that answer.
Included on paid plans.
IP, Domain, Weather, VIN, geography and other maintained profiles. Part of your shared request allowance, with no separate deep surcharge.
See plansIncluded on every plan.
Calendar components, IBAN decomposition, phone numbering-plan context and other compact details. One pooled request, including deep.
See an exampleIncluded checks. Then usage.
Email and VAT verification use their own monthly included checks. Eligible on-demand usage follows your plan's rates and spending controls.
How checks workFor Carrier and HLR, add ?deep=true for more detail at the same price.
THAT SIMPLE
Add one thing.
Get the whole picture.
Use your API key, add ?deep=true, and read the extra fields under deep.
curl "https://api.parseapi.com/domain/gmail.com?deep=true" \
-H "X-API-Key: YOUR_API_KEY"Already have query parameters? Add &deep=true.
Using an SDK? Set its optional deep option.
For Email and VAT verification, use a secret key from your server.
no deep requestedThe response includes the core answer. The deep key is omitted.
deep: { ... }Available detail sits under deep. Read the fields your app needs.
deep: {}No detail was added: access may be restricted, unavailable or a no-op for that lookup.
A quota or verification failure may return an error. Check the result you need, such as deep.deliverable, rather than treating the presence of deep as success.
A few details about the details.
Does deep change the core answer?
Deep adds context to the same question. For the same input, options and underlying data, core fields keep their values and meaning. Your application can read the extra detail when it needs it.
Do I need a paid plan?
Richer maintained profiles are included on paid plans. Small optional details are available on every plan. Verification uses its own included checks, with limited checks available on Free too. Each API reference spells out its access and pricing.
Which details can I get?
Each API page shows its core and deep fields, with examples and coverage. Unknown values return null. A requested deep object is empty when no detail is added.
Is deep always a fresh, live check?
Profiles and reference data follow each API’s update schedule. Verification performs the checks described by that API and may reuse a recent result. See the API reference for freshness and reuse details.
ParseAPI Deep
There's more
to the answer.
Start simple. Go deep when it matters.