Check live service health and documented failure responses before you integrate.
Used by people at amazing companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Send your API key with the documented header and keep requests consistent across services.
Start from the curl and HTTP samples, then map the parameters into your application code.
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
Example Response
HTTP Status Codes
Endpoints
/v1/scrape
/v1/scrape/jobs
/v1/scrape/jobs/:job_id
/v1/scrape/jobs/:job_id/results
Choose the retrieval effort for each URL
Credits are based on the mode you request, not the HTTP status or content returned by the target website.
Standard
1 credit per URL
One standard retrieval attempt for straightforward pages.
Resilient
2 credits per URL
One standard attempt with one retry when the result meets the documented retry conditions.
Rendered
10 credits per URL
One browser-rendered attempt for pages that require JavaScript execution.
Rendered resilient
20 credits per URL
One browser-rendered attempt with one retry when the result meets the documented retry conditions.
Resilient modes cost the listed amount even when the first attempt succeeds. They include one eligible retry, not unlimited retries or a guarantee that the target website will return the content you expect.
Billing reflects the work requested
A successful API operation means DomScan performed the selected retrieval mode and returned the resulting target response.
The result may still be a redirect, an HTTP error, a blocked response, a challenge page, an empty page, or content that does not meet your needs. These target-site outcomes are chargeable and are not eligible for a credit refund.
A refund is available only when DomScan verifies that its own platform failed to perform the selected retrieval mode.
Browser rendering does not guarantee that a page will load successfully, and resilient modes do not guarantee that the retry will produce a different result.
Scrape-specific usage limits
These limits apply specifically to the Scrape API. Other account and platform safeguards may also apply.
| Capability | Free accounts | Paid accounts |
|---|---|---|
| Available modes | Standard only | All four modes |
| Request rate | 5 requests per minute | 60 requests per minute |
| Concurrent standard or resilient requests | 1 standard request | 5 requests |
| Concurrent rendered requests | Not available | 2 requests |
| Daily allowance | 100 requests | Based on available credits and rate limits |
| Monthly allowance | 500 requests | Based on available credits and rate limits |
| Maximum returned content | 256 KiB per request | 512 KiB per request |
| Async batches | Not available | Available |
When a response exceeds the applicable content limit, the API returns the permitted portion and marks the response as truncated.
Process up to 100 URLs asynchronously
Paid accounts can submit an async job containing up to 100 URLs.
Up to 5 new batch jobs per minute
Up to 3 active jobs per account
Up to 300 queued URL items per account
Up to 100 URLs in one job
Completed results available for 24 hours
Job metadata retained for 7 days
Each URL is billed independently using its selected mode.
Download or copy completed results within 24 hours. After that period, the response content is removed even though limited job metadata remains available for 7 days.
Clear scope, without hidden upgrade options
No CAPTCHA solving
Browser rendering can execute page JavaScript, but the Scrape API does not solve CAPTCHAs or bypass login requirements, paywalls, access controls, or other restrictions. A CAPTCHA or challenge page returned by the target is a target-site outcome and is not refundable.
No premium proxy selection
You choose the retrieval mode and effort level. There is no premium proxy, provider, pool, or country-selection parameter.
Acceptable use
Use the Scrape API only for content you are legally permitted to access and process. You are responsible for complying with applicable laws, target-site terms, privacy obligations, and required permissions.
Do not use the API to bypass authentication, paywalls, CAPTCHAs, or access controls, or for credential attacks, account abuse, harassment, unlawful surveillance, or unlawful collection of personal data. DomScan may reject requests or suspend access when use threatens people, services, or the platform.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Credits are based on the mode you request, not the HTTP status or content returned by the target website.
A successful API operation means DomScan performed the selected retrieval mode and returned the resulting target response.
Paid accounts can submit an async job containing up to 100 URLs.
These limits apply specifically to the Scrape API. Other account and platform safeguards may also apply.
Browser rendering can execute page JavaScript, but the Scrape API does not solve CAPTCHAs or bypass login requirements, paywalls, access controls, or other restrictions. A CAPTCHA or challenge page returned by the target is a target-site outcome and is not refundable.
Use the Scrape API only for content you are legally permitted to access and process. You are responsible for complying with applicable laws, target-site terms, privacy obligations, and required permissions.
Example Request
curl -X POST "https://domscan.net/v1/scrape" \
-H "X-API-Key: $DOMSCAN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com/","mode":"standard","output":"markdown"}'
curl -X POST "https://domscan.net/v1/scrape" \
-H "X-API-Key: $DOMSCAN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com/app","mode":"rendered","output":"html"}'
curl -X POST "https://domscan.net/v1/scrape/jobs" \
-H "X-API-Key: $DOMSCAN_API_KEY" \
-H "Idempotency-Key: docs-batch-1" \
-H "Content-Type: application/json" \
-d '{"mode":"standard","output":"text","urls":["https://example.com/page-1","https://example.com/page-2"]}'
Example Response
{
"data": {
"url": "https://example.com/",
"final_url": "https://example.com/",
"status": 200,
"outcome": "success",
"content_type": "text/html",
"content": "<!doctype html>...",
"bytes": 1256,
"truncated": false,
"redirect_count": 0,
"attempt_count": 1,
"duration_ms": 428,
"fetched_at": "2026-08-20T10:30:00.000Z",
"headers": { "cache-control": "max-age=604800" },
"rendered": false
},
"billing": {
"credits_charged": 1,
"credits_refunded": 0,
"policy": "effort_based"
}
}
Frequently Asked Questions
One URL costs 1, 2, 10, or 20 credits depending on the selected mode. Batch items use the same per-URL pricing.
Yes. Target responses such as redirects, HTTP errors, blocks, challenge pages, empty pages, or unexpected content are chargeable because DomScan still performed the requested retrieval work.
A refund is available only when DomScan verifies that its own platform failed to perform the selected retrieval mode. Target-site behavior is not a platform failure.
No. Resilient mode includes one retry when the first result meets the documented retry conditions.
No. It executes page JavaScript but does not solve CAPTCHAs or bypass access restrictions.
No. The API does not expose proxy tiers, providers, pools, or country targeting. You select only the retrieval mode.
No. Async batches are available only to paid accounts. Free accounts can use standard mode within the published free limits.
Completed response content is available for 24 hours. Limited job metadata remains available for 7 days.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
Request successful
Cache-only subdomain miss accepted for background refresh. No credits are charged; retry after the Retry-After delay.
Invalid parameters
Missing or invalid API key/session.
Not enough credits to run this request.
Authenticated but not allowed to use this operation or mode.
We document the HTTP status codes you should handle so you can distinguish successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
Rate limit exceeded
Upstream service unavailable or temporarily rate limited.
Get an API key