Data API

Structured JSON from 35+ sites over one HTTP call. Ask for a product, a search page, a profile, or a thread and get back clean, source-shaped data. Run it on demand, or put it on a schedule.

Every extractor lives at a predictable path: /v1/{platform}/{action}, served from https://api.capzy.ai. You send the parameters for that endpoint, we handle the proxying, anti-bot clearance, and parsing, and you get JSON that mirrors the source. Pricing is a flat number of credits per run, no matter how many rows come back.

35+ sites, 350+ endpoints

Search engines, marketplaces, social, travel, and real estate. Browse the full, always-current list in the dashboard playground.

On demand or scheduled

Call it synchronously and read the result inline, or queue items and fire them on an interval or cron.

Flat credits per run

One run is one price. Result count never changes what you pay, and failed runs are free.

A first call

The example below runs an Amazon search. Authenticate with your dedicated Data API key, name the endpoint in the URL, and pass its parameters in params.

first-call.sh

curl -s https://api.capzy.ai/v1/amazon/search \
  -H 'X-API-Key: capzy_data_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{ "params": { "query": "usb c cable", "domain": "com" } }'
# -> { "errorId": 0, "status": "ready", "data": { ... }, "itemCount": 48, "credits": 1 }

A separate key from the Solver API

The Data API uses its own dedicated key, distinct from the Solver clientKey. It draws from the same account balance. See Authentication.

Where to go next

Authentication get and rotate your dedicated key, and the three ways to pass it.
Making a request the request body, the response shape, headers, and batch calls.
Jobs & polling the async lifecycle, polling, and pagination.
Queues & schedules run many items on a timer.
Endpoint catalog the platforms grouped by category.
Pricing credits, PAYG, and subscription tiers.

Authentication