Question 1

What is UnblockingAPI?

Accepted Answer

UnblockingAPI is a web unblocking API for developers who need reliable access to public web pages. You send a URL. We fetch it through real browsers, smart proxy routing and anti-detection logic, then return clean HTML, status codes, timing and metadata. No proxy dashboard. No browser farm. No credit calculator. Just the unblocking layer your scraper needs.

Question 2

Who is UnblockingAPI for?

Accepted Answer

UnblockingAPI is built for developers, data teams, founders, SEO teams, affiliate marketers, price monitoring tools, lead generation tools, AI/data pipelines and anyone who needs reliable public web data. Typical use cases include: E-commerce product pages Real estate listings Search results / SERPs Business directories Marketplaces Travel and hospitality pages Pricing and stock monitoring SEO and competitor research Public web data collection

Question 3

What problem does it solve?

Accepted Answer

Modern websites do not just serve HTML anymore. They inspect your request first — checking IP reputation, browser fingerprints, headers, TLS profiles, JavaScript environment, session behavior, rate limits, CAPTCHAs and headless browser signals. UnblockingAPI handles that messy layer so your scraper can focus on collecting data.

Question 4

How does it work?

Accepted Answer

You make a request to UnblockingAPI with the target URL: curl \ -H "X-Api-Key: YOUR_API_KEY" \ "https://api.unblockingapi.com/unblock?url=https://example.com&location=se" UnblockingAPI fetches the page using real browser infrastructure, proxy routing, retries and anti-detection logic. The response includes the rendered HTML, status code, timing, location and metadata.

Question 5

Do I need an API key?

Accepted Answer

For real API usage, yes. The public demo allows limited test requests without an API key, but production usage requires an account and API key. This helps prevent abuse and keeps the infrastructure reliable.

Question 6

Can I test a URL before signing up?

Accepted Answer

Yes. The live demo is designed for that. Paste a public URL, choose a country/location, optionally enable JavaScript rendering, and run a limited test request. The demo shows the response shape and product behavior before you create an account.

Question 7

What does the API return?

Accepted Answer

A typical response includes: { "status": "succeeded", "url": "https://example.com", "http_response_code": 200, "response_time_ms": 439, "location": "se", "render": true, "response_format": "html", "response": "<!doctype html>..." }

Question 8

Does UnblockingAPI support JavaScript-rendered pages?

Accepted Answer

Yes. JavaScript rendering is one of the core features. When rendering is enabled, the page runs in a real browser environment so JavaScript-heavy sites, SPAs and dynamic content can load before the HTML is returned. Use it for React/Vue/Next.js pages, SPAs, pages that hydrate after load, product pages with dynamic content, and pages where initial HTML is mostly empty.

Question 9

What is "Render JavaScript"?

Accepted Answer

It means UnblockingAPI opens the page in a real browser, waits for content to load, and returns the final rendered DOM instead of only the initial server response. Use it when the target page loads content dynamically.

Question 10

Do I need to manage proxies?

Accepted Answer

No. Proxy routing, sessions, country targeting and retries are handled behind the API. You do not need to buy proxy lists, rotate IPs manually or build your own proxy infrastructure. This is one of the main reasons to use UnblockingAPI instead of rolling your own scraper stack.

Question 11

Can I choose country or location?

Accepted Answer

The API works globally by default — you don't need to specify a location for most requests. When the target site shows different content by region, language, market or availability, add a country code:?url=https://example.com&location=se Routing is included in every plan with no extra cost or geo multipliers.

Question 12

Does it retry failed requests?

Accepted Answer

Yes. If a request fails due to temporary blocks, timeouts or flaky routing, UnblockingAPI retries with smarter routing and session behavior instead of forcing you to debug every failure manually. Retries are visible through metadata so developers can understand what happened.

Question 13

Does it avoid CAPTCHAs?

Accepted Answer

UnblockingAPI is designed to avoid many challenges before they appear by using better browser behavior, cleaner sessions, proxy routing and anti-detection techniques. No scraping service can honestly promise that CAPTCHAs will never happen. The goal is to reduce blocks and return a clean response whenever possible.

Question 14

Does it solve CAPTCHAs?

Accepted Answer

The preferred approach is CAPTCHA avoidance, not manual solving. The stack tries to behave naturally enough that many challenges do not appear in the first place.

Question 15

Does it support sticky sessions?

Accepted Answer

Session handling is part of the unblocking layer. For use cases where continuity matters, sticky sessions can help requests look more natural and preserve behavior across multiple requests.

Question 16

What is the main endpoint?

Accepted Answer

The primary endpoint is /unblock: curl \ -H "X-Api-Key: YOUR_API_KEY" \ "https://api.unblockingapi.com/unblock?url=https://example.com&location=se&render=true"

Question 17

Can I use POST instead of GET?

Accepted Answer

Yes. For simple tests, GET is convenient. For production usage, POST is often better because it handles longer URLs and structured options more cleanly: curl -X POST "https://api.unblockingapi.com/unblock" \ -H "X-Api-Key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"url": "https://example.com", "location": "se", "render": true}'

Question 18

Does it work with Node.js?

Accepted Answer

Yes. Any HTTP client works: const res = await fetch("https://api.unblockingapi.com/unblock", { method: "POST", headers: { "X-Api-Key": process.env.UNBLOCKING_API_KEY, "Content-Type": "application/json" }, body: JSON.stringify({ url: "https://example.com", location: "se", render: true }) }); const data = await res.json(); console.log(data.response);

Question 19

Does it work with Python?

Accepted Answer

Yes: import requests res = requests.post( "https://api.unblockingapi.com/unblock", headers={ "X-Api-Key": "YOUR_API_KEY", "Content-Type": "application/json" }, json={ "url": "https://example.com", "location": "se", "render": True } ) data = res.json() print(data["response"])

Question 20

Does it work with Ruby?

Accepted Answer

Yes: require "net/http" require "json" require "uri" uri = URI("https://api.unblockingapi.com/unblock") req = Net::HTTP::Post.new(uri) req["X-Api-Key"] = "YOUR_API_KEY" req["Content-Type"] = "application/json" req.body = { url: "https://example.com", location: "se", render: true }.to_json res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(req) } data = JSON.parse(res.body) puts data["response"]

Question 21

Does it work with PHP?

Accepted Answer

Yes: $ch = curl_init("https://api.unblockingapi.com/unblock"); curl_setopt_array($ch, [ CURLOPT_RETURNTRANSFER => true, CURLOPT_POST => true, CURLOPT_HTTPHEADER => [ "X-Api-Key: YOUR_API_KEY", "Content-Type: application/json" ], CURLOPT_POSTFIELDS => json_encode([ "url" => "https://example.com", "location" => "se", "render" => true ]) ]); $response = curl_exec($ch); curl_close($ch); $data = json_decode($response, true); echo $data["response"];

Question 22

Do I need an SDK?

Accepted Answer

No. UnblockingAPI is a plain HTTP API. Use curl, Node.js, Python, Ruby, PHP or whatever your stack already runs. No special libraries needed.

Question 23

What data can I retrieve?

Accepted Answer

UnblockingAPI is built for public web data. Typical examples: Product pages and pricing Search result pages Real estate listings Business directories Marketplace listings Travel and hotel pages SEO result pages Public articles

Question 24

Can I access private data or pages behind login?

Accepted Answer

No. UnblockingAPI is designed for public web data. Do not use it for private data, personal data, content behind logins or anything you are not allowed to access.

Question 25

Can I retrieve data from Google?

Accepted Answer

UnblockingAPI can support search-result style pages and localized result fetching. A dedicated Google Search template endpoint is available at /api/google-search — see the API docs for details.

Question 26

Can I retrieve data from Amazon, eBay, Zillow or Idealista?

Accepted Answer

UnblockingAPI is a general web unblocking API, not a set of dedicated site-specific extractors. It can be used to fetch public pages from e-commerce, marketplace and real estate websites. Site-specific success depends on the target, traffic pattern, region, rendering mode and anti-bot behavior. A dedicated template endpoint is available for idealista property listings.

Question 27

Does UnblockingAPI extract structured product data automatically?

Accepted Answer

The core API returns rendered HTML, status codes and metadata. Structured extraction is available through template endpoints (like /api/idealista-property and /api/google-search), with more on the roadmap.

Question 28

What happens if a request gets blocked?

Accepted Answer

UnblockingAPI retries with smarter routing, browser sessions and anti-detection logic. If the request still fails, the API returns a clear error response with metadata: { "status": "failed", "http_response_code": 403, "error": "blocked", "response_time_ms": 2100 }

Question 29

What happens if the target times out?

Accepted Answer

The API returns a 504 timeout error with metadata so you know what happened: { "status": "failed", "error": "timeout", "response_time_ms": 30000 }

Question 30

Is there a free trial?

Accepted Answer

Try limited demo requests without an API key. Create an account when you're ready to run real requests.

Question 31

Why not offer unlimited free access?

Accepted Answer

Browser rendering, proxy routing and anti-detection infrastructure are expensive. Unlimited free access would attract fake accounts, abuse and high-cost traffic. Limits keep the product stable for real users.

Question 32

How is pricing calculated?

Accepted Answer

UnblockingAPI is designed around simple usage and concurrency — not confusing credit math. Pay for scraping power, not surprise credits. More concurrency means more pages processed in parallel.

Question 33

Why concurrency-based pricing?

Accepted Answer

Concurrency-based pricing is easier for developers to understand. Instead of calculating credits, JavaScript multipliers, geo multipliers and proxy add-ons, you choose how much scraping power you need.

Question 34

Can I get custom limits or enterprise setup?

Accepted Answer

Yes. For larger workloads we offer custom throughput, dedicated routing, SLAs, invoicing and priority support. Need custom throughput, SLA or dedicated routing? Talk to us.

Question 35

How fast is it?

Accepted Answer

Speed depends on the target website, rendering mode, location, page size, JavaScript complexity and anti-bot behavior. A simple non-rendered request is fast. A full browser-rendered page with JavaScript takes longer. Use rendering only when the target needs it.

Question 36

Why is JavaScript rendering slower?

Accepted Answer

Because the page runs in a real browser — loading scripts, waiting for network requests, rendering the DOM and handling page behavior before returning the result.

Question 37

Does UnblockingAPI return HTML or JSON?

Accepted Answer

The API response wrapper is JSON. The page content inside the response is HTML: { "status": "succeeded", "response_format": "html", "response": "<!doctype html>..." } Template endpoints return structured JSON in the response field instead.

Question 38

Does it return structured JSON?

Accepted Answer

The core /unblock endpoint returns rendered HTML and metadata. Structured JSON extraction is available through template endpoints like /api/idealista-property and /api/google-search, with more planned.

Question 39

Is this legal?

Accepted Answer

Web scraping rules vary depending on jurisdiction, target website, data type and usage. UnblockingAPI is built for public web data. Users are responsible for following applicable laws, website terms and privacy rules.

Question 40

What data should I avoid scraping?

Accepted Answer

Avoid: Personal data without a lawful basis Private content or content behind logins Payment or medical data Anything you are not allowed to access

Question 41

What can I use UnblockingAPI for?

Accepted Answer

Anything that involves legitimate access to public web data — price monitoring, lead generation, SEO research, real estate listings, market intelligence, academic research, and more. See our Acceptable Use Policy for details.

Question 42

Do you bypass security systems?

Accepted Answer

UnblockingAPI is designed to improve reliable access to public web pages by handling browser rendering, routing, retries and anti-detection. It is not a tool for unauthorized access, account abuse, private data extraction or breaking into systems.

Question 43

Do you offer support?

Accepted Answer

Yes. When you reach out, you're talking directly to the dev team building the engine — not a ticket queue. We can help debug tricky targets, tune request strategies and get you unblocked fast.

Question 44

Can I talk to someone before buying?

Accepted Answer

Yes. No sales call required — unless you want one. You'll chat directly with the team building the product. For larger workloads, we're happy to discuss custom throughput, SLAs and dedicated routing.

Question 45

What endpoints are live today?

Accepted Answer

Live today: /unblock — Web unblocking API (HTML + metadata) /api/google-search — Structured Google Search results /api/idealista-property — Structured property data

Question 46

What is on the roadmap?

Accepted Answer

Potential roadmap items include SERP API expansion, SEO metrics, e-commerce price/review extraction, screenshots, structured extraction for more sites, webhooks and bulk crawling. The core product stays clear: UnblockingAPI is the unblocking layer first. Dedicated structured endpoints come later.

Question 47

I get a 403. What should I try?

Accepted Answer

Try these steps: Enable JavaScript rendering ( render=true) Use another location Increase timeout Retry the request Check whether the page requires login Check whether the URL is publicly accessible If it still fails, talk to us with the request ID — you'll reach the dev team directly, and we can help tune the setup for your target.

Question 48

I get empty HTML. Why?

Accepted Answer

Common reasons: The page requires JavaScript rendering The content loads after initial page load The target blocks the request The page uses lazy loading The timeout is too short Try enabling rendering and using the wait parameter.

Question 49

The page works in my browser but not through the API. Why?

Accepted Answer

Your browser has your real session, cookies, behavior, IP history and local environment. A fresh API request is different. Some websites react differently to new sessions, different countries, datacenter IPs, browser environments or missing interaction history.

Question 50

Why does the same URL sometimes behave differently?

Accepted Answer

Modern websites change responses based on location, IP reputation, session history, cookies, A/B tests, rate limits, anti-bot systems, time of day and device/browser profile. UnblockingAPI reduces this pain, but some variability is normal in public web data collection.

Built for developers

Simple plans. Predictable capacity.

Popular use cases

Frequently asked questions

Overview

Getting started

Features

API usage

Scraping behavior

Plans & billing

Performance

Response format

Security & compliance

Support

Roadmap

Troubleshooting

Still have questions?