DataHen Web scraping API pricing: POST / jobs/ {id}/ pages
Is DataHen yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
- $149 monthly, Professional PlanProfessional Plan$0.497 per 1,000
- $1,000 monthly, Enterprise PlanEnterprise Plan$0.50 per 1,000
POST / jobs/ {id}/ pages one of DataHen's 2 callsPOST /$149 monthly, Professional Plan$0.497 per 1,000jobs/ {id}/ pages GET /$149 monthly, Professional Planjobs/ {id}/ pages/ {gid}/ content
About this item
- Freshness. We don't know how fresh this plan's data is.
- 1 of the 7 fields on our checklist. Screenshot.
- A monthly subscription. You pay $149 a month for 300,000 requests.
- One call. You send
idandurltoPOST /. The call returns a job. You fetch the answer once the job is done.jobs/ {id}/ pages - Anyone can get it. Keep data: no API terms. Use data: no API terms.
DataHen: web scraping API alternatives
DataHen alternatives: other web scraping API providers by price
We list other providers' plans closest to this plan in price per 1,000 pages.
| This planDataHen, $149 monthly, Professional Plan, POST /jobs/{id}/pages | HasData, $1,190 yearly, Basic, POST /scrape/web, Web Scraping API, residential proxy | ScrapeUp, $149 monthly, Professional Advanced, POST /, Standard scrape | DataFluxor, $199 monthly, Scale, POST /api/v1/scrape/page | Crawlfox, $498 pack, 1,000,000 credits, POST /v1/batch | |
|---|---|---|---|---|---|
| $ per 1,000 pages | $0.497 | $0.496 | $0.497 | $0.497 | $0.498 |
| Completeness | 14% | 71% | 43% | 14% | 57% |
| Billing | monthly | yearly | monthly | monthly | pay first |
| Pay | $149 | $1,190 | $149 | $199 | $498 |
| Enough for | 300,000 calls a month | 200,000 calls a month | 300,000 calls a month | 400,000 calls a month | 1,000,000 results |
| Freshness | unknown | live | live | live | unknown |
| Who can get it | anyone | anyone | anyone with a confirmed email who accepts the Acceptable Use Policy | anyone | anyone |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-10.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Screenshot
- Markdown, not in the answer
- HTML, not in the answer
- Text, not in the answer
- Summary, not in the answer
- Links, not in the answer
- Images, not in the answer
| $ per 1,000 pages | $0.497 |
|---|---|
| Per | call |
| Billing | monthly |
| $ a month | $149 |
| Also pays for | 92 other DataHen calls · from the same budget: Add a Page in a Current Job · Refetch Pages in a Job · Refetch Pages in a Current Job |
|---|
| Their pitch | Scale your web scraping processes to millions of page requests with a few mouse clicks. |
|---|
| Keep data | no API terms |
|---|---|
| Use data | no API terms |
| Pay | $149 |
|---|---|
| You get | 300,000 requests a month |
| Enough for | 300,000 calls a month |
| Concurrent | 3 |
|---|---|
| Batch | 1 |
| Answer | by polling |
|---|
| You send | id, url. Optional: page_type, priority, fetch_type, method, headers, cookie, body, no_redirect, no_url_encode, http2, ua_type, freshness, reset, vars, driver |
|---|---|
| Method | POST |
| Path | /jobs/{id}/pages |
| Plan | Professional Plan |
|---|---|
| Who can get it | anyone |
The 53 fields the plan's answer can hold
page ID, job ID, job status, page status, page type, priority, fetch type, hostname, HTTP method, URL, effective URL, request headers, request cookie, request body, created at, no redirect, no URL encode, HTTP2, user agent type, freshness, fresh, fetching at, fetched at, to fetch at, total successes, total requests, total failures, response checksum, response status, HTTP status code, response headers, response cookie, response protocol, content type, content size, fetched from, reset, vars, driver, display, screenshot, driver log, force fetch, failed response checksum, failed response status, failed HTTP status code, failed response headers, failed response cookie, failed response protocol, failed content type, failed effective URL, failed at, failed content size