Skip to main content
History stores every API call your account makes (scrape, extract, search, monitor ticks, crawl jobs, schema generations) and lets you fetch them back later by ID. For crawl page content, use GET /api/crawl/:id/pages first; it returns paginated crawl pages with the underlying scrape result resolved into each page. Use History when you need to inspect an individual underlying request by its scrapeRefId.

List history

Returns a paginated list of recent entries, newest first.

Query parameters

integer
default:"1"
Page number to fetch (1-indexed).
integer
default:"20"
Entries per page.
string
Filter by service. One of "scrape", "extract", "search", "monitor", "crawl", "schema".

Example request

Example response

Get one entry

Returns the full record for a single request — including the full result payload (markdown, HTML, JSON extraction, screenshots, etc.).

Path parameters

string
required
The UUID of a request. This is the same UUID returned by the originating endpoint:
  • From POST /api/scrape → top-level id
  • From POST /api/extract → top-level id
  • From POST /api/search → top-level id
  • From GET /api/crawl/:id → each pages[].scrapeRefId
  • From GET /api/monitor/:cronId/activity → each ticks[].id

Example request

Example response

Entry shape

Every entry — both in GET /history and GET /history/:id — has the same shape:

Fetching crawled page content

The canonical pattern: start a crawl, poll until completed, then for each page fetch its scrape result.
The requestParentId on each child scrape entry equals the parent crawl’s id, so you can also list every page produced by a single crawl with:

Errors

See Error handling for the full envelope.