Skip to main content
Use by_direct_url when Context.dev should read one specific page, such as a campaign, preview environment, regional site, or deep product page.
This lookup reads only the URL you provide. It does not resolve the wider domain or combine cross-source data, so the returned profile can be much sparser than a domain lookup.

Send a URL

The PHP tab uses the SDK’s low-level request method because the 2.14.0 Brand helper requires conflicting lookup fields. See the PHP guide for details.
The endpoint costs 10 credits.

Supported controls

The direct URL variant accepts type, direct_url, timeoutMS, and tags. It rejects maxAgeMs, maxSpeed, and force_language. Those controls belong to resolver-backed lookup variants and do not apply to this one-page flow.

Handle sparse results

Only use fields that the page exposes. A successful response can omit the assets or company details that a wider domain lookup would find. If the page cannot be fetched, inspect the 400 response and its error_code before retrying.

Next steps

Retrieve brands by domain

Let the resolver identify the company and assemble a broader profile.

Scrape a webpage

Read the page’s content instead of its brand fields.

Troubleshooting

Review current failure categories before choosing a retry policy.

Brand API reference

Review the full request and response contract.