Web Scraping API

List async web jobs

List your asynchronous jobs, newest first, with keyset pagination. Free.

Read as Markdown Use with an AI agent

Endpoint

GET/v1/web/jobslive · provenfree

Try in Playground

Parameters

Query parameters

Name	Required	Description	Example
`limit`	no	Jobs per page (default 25, cap 100)	`25`
`cursor`	no	Opaque cursor from the previous page; omit for the first page
`status`	no	Filter by status: queued, running, completed, failed, cancelled (comma-separated for several)	`completed`
`dry_run`	no	Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution.	`1`

Examples

Make the request

curl

curl "https://www.monocrawl.com/v1/web/jobs" \
  -H "x-api-key: mn_your_key_here"

TypeScript

typescript

const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
  "https://www.monocrawl.com/v1/web/jobs",
  { headers: { "x-api-key": key } },
);
const body = await res.json();

if (!body.success) {
  // one error shape for every endpoint — see /docs/errors
  throw new Error(`${body.error.type}: ${body.error.message}`);
}

console.log(body.data, "credits left:", body.credits_remaining);

Python

python

import os
import requests

res = requests.get(
    "https://www.monocrawl.com/v1/web/jobs",
    headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
    timeout=60,
)
body = res.json()

if not body["success"]:
    # one error shape for every endpoint — see /docs/errors
    raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")

print(body["data"], "credits left:", body["credits_remaining"])

Response

Response fields and example

This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.

200 · application/json

{
  "success": true,
  "platform": "web",
  "endpoint": "/v1/web/jobs",
  "data": {
    "items": [],
    "count": 0,
    "cursor": null,
    "has_more": false
  },
  "credits_used": 0,
  "credits_remaining": 99,
  "request_id": "req_…",
  "cached": false
}

The example is illustrative and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.

Schema basis: reviewed response shaper. See schema coverage and validation limits.

Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.

Field inside data	Type	Meaning
`items`	`array \| null`	Nested response fields; optional unless explicitly documented.
`items[].id`	`string \| null`	id
`items[].kind`	`string \| null`	kind
`items[].status`	`string \| null`	status
`items[].error`	`string \| null`	error
`items[].refund_status`	`string \| null`	refund status
`items[].created_at`	`string \| null`	created at
`items[].started_at`	`string \| null`	started at
`items[].completed_at`	`string \| null`	completed at
`items[].credits_charged`	`number \| null`	credits charged
`items[].credits_refunded`	`number \| null`	credits refunded
`items[].attempts`	`number \| null`	attempts
`items[].params`	`object \| null`	Nested response fields; optional unless explicitly documented.
`items[].progress`	`object \| null`	Nested response fields; optional unless explicitly documented.
`items[].result`		Operation-specific JSON value; inspect the status and requested operation before reading it.
`count`	`number \| null`	Nested response fields; optional unless explicitly documented.
`cursor`	`string \| null`	Nested response fields; optional unless explicitly documented.
`has_more`	`boolean \| null`	Nested response fields; optional unless explicitly documented.

Core response fields reviewed from the public response shaper. Fields vary by requested options; additive fields remain allowed.

Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference

List async web jobs

Query parameters

Make the request

Response fields and example

More Web Scraping reference

First call in under a minute