How it works

One request in. A clean response out.

Send a public URL with optional controls for rendering, location and session behavior. UnblockingAPI handles browser execution, routing, retries and response delivery behind one predictable endpoint.

Try it freeView API docs
1Request
GET /unblock·https://example.com·location=se·render=true
2UnblockingAPI
Browser
·
Routing
·
Retries
Target page·Public web page
4Response
200 OK· 439 ms
{ "status": "succeeded", "location": "se", "render": true, ... }

Request lifecycle

What happens after you send a URL

1

Request received

We validate the URL and request options.

2

Browser and route selected

The engine chooses an appropriate browser session, location and network route.

3

Page rendered

JavaScript executes, dynamic content loads and managed retries run when needed.

4

Response returned

You receive HTML, status codes, timing, location and metadata in one predictable response.

One endpoint. Predictable responses.

Use any HTTP client. Add rendering, location or session options only when your workflow needs them.

request.sh
curl \
  -H "X-Api-Key: YOUR_API_KEY" \
  "https://api.unblockingapi.com/unblock\
?url=https://example.com\
&location=se&render=true"
response.json
{
  "status": "succeeded",
  "http_response_code": 200,
  "response_time_ms": 439,
  "render": true,
  "location": "se",
  "response_format": "html",
  "response": "<!doctype html>..."
}

What the engine handles

So you don't have to.

JavaScript rendering

Pages run in real browsers so dynamic content loads before the DOM is captured and returned as HTML.

Global routing

Works worldwide by default. Add a country code when you need region-specific content.

Managed browser sessions

Cookies, fingerprints and TLS profiles handled automatically.

Automatic retries

Failed requests retry with smarter routing and session behavior.

Response normalization

HTML, status codes, timing and metadata in one consistent shape.

Infrastructure monitoring

Route health, success rates and latency tracked continuously.

No multiplier math.

Browser rendering, routing and retries do not multiply your usage. Plans are based on concurrency and requests per hour — not credit calculations.

Typical credit API

1 request
× rendering
× proxy
× retry
= 5 – 25 credits

UnblockingAPI

1 successful request
= 1 successful request

One successful request is one request.

What counts as successful

You pay for completed target responses.

A successful request is a completed target response. Target 2xx responses and target 404 responses count because the target page was fetched successfully. UnblockingAPI infrastructure errors, rendering backend failures and service errors do not count.

Counts

  • Target responds with 2xx
  • Target responds with 404
  • Target page fetched successfully

Does not count

  • Infrastructure errors
  • Rendering backend failures
  • Service errors

Honest target behavior

Built for real-world public web pages.

Site-specific success depends on the target page, region, rendering mode and anti-bot behavior. The engine automatically manages routing, sessions and retries to improve consistency across different targets.

Send your first public URL.

Up to 2,000 free requests. No credit card required.

Start freeRead the docs