Skip to main content
POST
Ask for a domain to be prepared for Extract

Authorizations

apikey
string
query
required

Fetch, Extract, Crawl and the account endpoint accept the key as the apikey query parameter. Keys are per account and self-serve: create one in the Zenrows dashboard (app.zenrows.com), or, for an agent with no human present, POST https://app.zenrows.com/api/agent/signup.

Headers

Idempotency-Key
string

The same key returns the original submission instead of spending a second allowance slot.

Body

application/json
domain
string
required

The domain to prepare, without scheme.

Example:

"scrapingcourse.com"

example_urls
string<uri>[]

1 to 5 URLs on that domain. One works; we recommend 3 or more of the same page type (e.g. 3 product pages), because Extract compares pages of one type to check the fields it found and fill in fields one page is missing. Several page types can share the 5 (e.g. 3 product pages + 2 search-result pages). When present, they replace discovery.

Example:

Response

Accepted. The body is the submission in the same shape getExtractDomainStatus returns.

A domain's preparation for Extract.

domain
string
status
enum<string>

Whether the domain can be used yet. Branch on this.

Available options:
preparing,
ready,
failed
state
string

The current step. Gains steps over time.

Examples:

"received"

"discovering"

"preparing"

"verifying"

"ready"

"failed"

roles
object[]

Progress per page, with its page type in role. Only present for the account that submitted the domain.

failure
object

Present when status is failed.

submitted_at
string<date-time>
updated_at
string<date-time>