Deep
Simple by default.
Detailed when needed.
Add ?deep=true for richer profiles, registration details
and verification results in the same response.
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.
Domain reference/domain/gmail.com{"domain": "gmail.com","available": false}
Why Deep?
Checking a domain's availability doesn't need its registrar and registration dates. Building a domain profile does.
Deep lets your app choose how much data to request. Keep routine lookups small, then include extra fields when a feature needs them. The endpoint and core fields stay the same.
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, Vehicle, 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 workTHAT 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"Using an SDK? Set its optional deep option.
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 extra fields were returned. Deep may be unavailable for this lookup, plan or API key.
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.
Deep
Details on demand.
Start simple. Add context when it matters.