Managed Web Access API

Web Unlocker

Send a target URL and receive the rendered response while DINPROXY handles routing, JavaScript, retries, anti-bot challenges, and CAPTCHAs.

Success rate99.5%

Anti-bot checks handled

Cloudflare, DataDome, PerimeterX, Imperva and CAPTCHAs are dealt with inside the request.

One price per result

JavaScript rendering and screenshots cost nothing extra: each success counts once.

Failed requests$0
Concurrency100

Fits the tools you use

Call the API, set it as your scraper’s proxy, or add it to an AI assistant over MCP.

Countries195+

No proxies or browsers to run

Anti-bot coverage

Every CAPTCHA. Every bot wall.

Solved automatically, in seconds. Failed requests are free.

SolutionsSpeed
reCAPTCHA v2under 5 seconds
reCAPTCHA v3under 3 seconds
reCAPTCHA v2 Enterpriseunder 3 seconds
reCAPTCHA v3 Enterpriseunder 3 seconds
AWS WAFunder 3 seconds
GeeTest v3 / v4under 5 seconds
ImageToTextunder 1 seconds
Cloudflare Turnstileunder 3 seconds
Cloudflare Challengeunder 10 seconds
DataDomeSupported
PerimeterXSupported
ImpervaSupported
Not on the list? We build a custom unlock for your site.Talk to us

Pricing

Web Unlocker pricing

Choose how many results you need, in steps of 1k, and estimate the cost of successful results.

Results20 × 1k results
Need more than 2 million results?

Contact our team for a larger result volume and custom commercial plan.

Contact sales

Why teams choose it

Turn difficult pages into usable responses

Start with the page you need

Send a target URL and ask for the location, rendering, and response state your collector needs.

Skip the browser plumbing

Keep routing, rendering, retries, and challenge-related handling out of the collector itself.

Move from page to pipeline

Receive rendered HTML (or a PNG screenshot) that can flow into parsing, monitoring, and downstream systems.

Integration

Production-ready responses

Use a standard authenticated request pattern and choose only the target, geography, rendering, and response options your workflow needs.

Target URL and location optionsJavaScript rendering (on by default)HTML or PNG screenshot response
Web Unlocker request pattern
const response = await fetch("https://app.dinproxy.com/api/unblocker/request", {  method: "POST",  headers: {    Authorization: "Basic " + Buffer.from("USERNAME:PASSWORD").toString("base64"),    "Content-Type": "application/json",  },  body: JSON.stringify({    target_url: "https://www.google.com",    response_format: "html",    js_render: true,  }),});
const result = await response.json();console.log(response.status);console.log(result.data.html);
Replace USERNAME and PASSWORD with a proxy user from your dashboard (Users): the full name, such as 1024~myuser. Send the target URL and options as JSON; the response contains the rendered HTML.

Use cases

Complex web access

Select an access or delivery pattern that aligns with the identity, page state, and output requirements of the intended workflow.

Rendered collection

Retrieve pages whose useful content appears only after JavaScript execution.

Ad verification

Inspect localized placements, creatives, and landing page states.

Recurring monitoring

Reduce the routing and retry maintenance behind repeated page checks.

Public page research

Collect usable rendered HTML from supported public targets.

Product requirements

Web Unlocker requirements

Review the operating model, control scope, and delivery attributes that define Web Unlocker before implementation.

Input
Target URL plus rendering and location options
Managed steps
Proxy routing, JavaScript, retries, CAPTCHAs, and anti-bot challenges
Output
Rendered HTML, PNG screenshot, or both
Location
Country-level routing across supported regions

Frequently asked questions

Key implementation questions

Use it when the target needs managed retries, browser rendering, or challenge handling rather than direct proxy connectivity alone.

Commercial consultation

Managed access workflow

Tell us the targets, rendering needs, locations, output format, and expected request volume.