# Website WebUnlocker (POST)

## Overview

| Property | Value |
|----------|-------|
| **Status** | active |
| **Method** | `POST` |
| **Endpoint** | `/v1/website/webunlocker` |
| **Base URL** | `https://api.browsersolver.com` |
| **Credit Cost** | 3 credits per call |
| **Documentation** | https://www.browsersolver.com/library/website-webunlocker-website-webunlocker-post |

## Description

Call approved JSON APIs with POST through BrowserSolver unlock sessions when a normal Crawler POST is rejected by bot management.

## Authentication

- **Key Name:** `x-api-key`
- **Location:** HTTP Header
- **Get an API key:** https://app.browsersolver.com/register

## Example Request

```bash
curl --location --request POST 'https://api.browsersolver.com/v1/website/webunlocker' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: YOUR_API_KEY'
```

## Example Response

### POST inventory API after unlock

```json
{
  "data": [
    {
      "ref": "INV-44019",
      "link": "https://catalog.example.org/items/INV-44019",
      "label": "Office desk oak",
      "stock": 12,
      "warehouse": "LYS-02",
      "list_price": 459
    }
  ],
  "cursor": {
    "next": "eyJwYWdlIjoyfQ==",
    "count": 86
  }
}
```

## Documentation

## Purpose

[Website WebUnlocker (POST)](/v1/website/webunlocker) sends a **POST** through BrowserSolver's premium unlock stack to a whitelisted page or JSON API, then returns the upstream response (HTML or JSON).

Reach for this card when:
- The target expects a JSON POST body, and
- [Website Crawler (POST)](/v1/website/crawler) cannot pass enterprise bot checks on an approved hostname.

For GET page fetches on whitelisted domains, use [Website WebUnlocker](/v1/website/webunlocker).

**Whitelist:** the hostname must be approved on your BrowserSolver account before production traffic.

**Pricing:** 3 credits per successful response.

## Quickstart

```
POST https://api.browsersolver.com/v1/website/webunlocker?query=https://www.kleinanzeigen.de/s-api/search
Content-Type: application/json

{"page":1,"size":25,"codeTypeBiens":[600,700]}
```

Pass the target URL in `query` (query string or JSON wrapper). The POST body is forwarded upstream after the unlock flow.

## Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Target URL with protocol; domain must be whitelisted |

**POST only** on this card. Simple GET HTML retrieval uses [Website WebUnlocker](/v1/website/webunlocker).

## Response
Upstream payload after bot bypass (JSON or HTML).

## Companion endpoints
| Situation | Endpoint |
|---|---|
| Open POST API, no bot wall | [Website Crawler (POST)](/v1/website/crawler) |
| GET HTML on whitelisted domain | [Website WebUnlocker](/v1/website/webunlocker) |
| Check vendor before picking tier | [Website Antibot](/v1/website/antibot) |

## Tips
- Validate [Website Crawler (POST)](/v1/website/crawler) first when no unlock is needed (saves credits).
- Same `query` + JSON body pattern as the Crawler POST card.
- Contact BrowserSolver support to whitelist additional hostnames.

## Common workflows
- Protected search or listing APIs that require JSON POST bodies
- DataDome, Cloudflare, or Akamai on whitelisted commercial endpoints
- Enrichment pipelines against approved marketplace backends
- Prototype XHR calls without operating your own unlock infrastructure