Skip to main content
POST
The POST /request endpoint sends HTTP or browser-rendered requests through Unblocker. You specify the target method and url (and optional headers, body, geo, or browser mode); the service applies anti-bot handling, optional egress proxy selection, and returns a JSON envelope with the target response. LLM prompts (ChatGPT, Gemini, Google AI Overview) use a separate endpoint: POST /llm. That call takes source and prompt, not url. Access token: You must bring your own Bearer token (JWT) for every call and for Try it. If you do not have a token yet, see Token acquisition.

Overview

Unblocker POST /request supports:
  • HTTP methods: GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS
  • Optional country codes to prefer a matching egress proxy
  • Optional browser: true for JavaScript-rendered HTML
  • Bearer JWT authentication (gateway maps the token to your tenant)
  • Monthly request quotas on self-serve plans (HTTP 429 when exceeded)

Endpoint

URL: POST /request
Base URL: https://unblocker.bringits.com
Full URL: https://unblocker.bringits.com/request

Headers

In Try it, enter your JWT only in Authorize (token field). Do not paste the full Authorization header or duplicate the token in a Headers box.

Response headers

Request body parameters

How the request is handled

  1. Quota — Monthly usage is checked before proxy selection. Over limit → 429 (no proxy slot used). Usage is incremented only after the target response is successfully read (not on transport or proxy-selection failures).
  2. Proxy — Unblocker selects a proxy for the URL domain and optional countries. If your pool has no proxy for those countries, the request proceeds with direct egress; fingerprint emulation still applies on the HTTP path. Any other proxy-pool problem (for example a pool that is still being created) does not fall back to direct egress: you get 503 SERVICE_UNAVAILABLE with Retry-After.
  3. Delivery — browser: false uses an HTTP client with browser-like TLS/fingerprinting through the proxy (or direct). browser: true calls the browser rendering service and returns page HTML.

Response format

Classic scrapes use Content-Type: application/json and this envelope:
When the unblocker successfully delivers a classic scrape, the outer HTTP status is 200, even if the target returned 404 or 500. Read the target status from status in the JSON body.

Errors

Errors use the scrape envelope with error set and status / body null. The body carries only the code, no message. error is always one of these nine codes: Example (HTTP 502, with Retry-After: 60):
A missing or gone page is the target’s answer, not an error: a target 404 or 410 is delivered as outer 200 with status set to the target’s status.

HTTP 429 — quota exceeded

Check X-RateLimit-* and Retry-After headers. Enterprise tenants are not subject to monthly request quotas.

Usage examples

cURL: GET (minimal)

Replace <YOUR_ACCESS_TOKEN> with a valid tenant JWT.

GET with custom headers

POST with body

Geo proxy preference

Browser-rendered HTML (with geo)

Use browser: true for JavaScript-rendered pages. Optional countries selects egress (here, Brazil):
Replace <YOUR_ACCESS_TOKEN> with your tenant JWT and set url to the page you want rendered. On success, body contains the rendered HTML string; headers is often {}.

Best practices

  • Store the token in a secret (e.g. %{LINK_UNBLOCKER_TOKEN}) instead of hardcoding.
  • Use HTTPS for target url values when possible.
  • Classic scrapes: check both layers — outer HTTP status (200 vs 4xx/5xx from unblocker) and envelope status (target outcome).
  • Handle 429: respect Retry-After and surface used / limit / reset_at to users.
  • Retry by code: wait for Retry-After on 429, 502, and 503; retry 504 with backoff and 500 once. Do not retry 400, 401, or 403 with the same request.
  • Log x-request-id when opening support tickets.

Try it

Use the interactive Try it panel below to send a real request.

Before you start

  1. Get a token – See Token acquisition.
  2. Authenticate – Enter the token in Authorize (Bearer is applied automatically).
  3. Edit the body – Default: {"method":"GET","url":"https://tlsinfo.me/json"}. Try countries or browser as needed.
  4. Send – Inspect the JSON envelope; on success, error is null and target data is under status, headers, and body.
Security: Do not share your token or commit it to code. Use the Authorize dialog only in your browser; the token is not stored in the documentation.

Base URL

Requests use https://unblocker.bringits.com (shown in the Try it panel as the server URL).

Authorizations

Authorization
string
header
required

Use Authorize and enter your tenant JWT in the token field only. The gateway validates the token and injects x-tenant-id from the tenantId claim; do not set x-tenant-id manually in production.

Body

application/json
method
enum<string>
default:GET
required

HTTP method the unblocker uses when calling the target url (ignored when browser is true).

Available options:
GET,
POST,
PUT,
DELETE,
PATCH,
HEAD,
OPTIONS
Example:

"GET"

url
string<uri>
required

Target URL to request.

Example:

"https://tlsinfo.me/json"

headers
object

Optional headers sent to the target URL (HTTP path only).

body
string | null

Optional raw request body for the target (HTTP path only). For JSON payloads, stringify the JSON.

countries
string[]

Optional ISO country codes used to select a proxy. If your proxy pool has no proxy for these countries, the request still proceeds using direct egress. Other proxy-pool problems (for example a pool that is still being created) return 503 SERVICE_UNAVAILABLE instead.

browser
boolean
default:false

When true, fetches the page through the headless browser service and returns rendered HTML in body.

Response

Request delivered; target response is in the JSON envelope (error is null). Outer HTTP status is 200 even when the target returned 4xx/5xx — check status in the body.

status
integer | null
required

HTTP status code from the target URL (or 200 for browser HTML success).

Example:

200

headers
object
required

Response headers from the target (may be empty for browser mode).

body
string | null
required

Response body from the target (HTML string when browser is true).

error
string | null
required

Null on success.

Example:

null