Web Scraping Data Export API - Grepsr Reports, Runs and Files

Export what your own Grepsr web scraping projects have already collected: every scraped record of a report's latest run or of any past history, the run history with item counts, output file links, run parameters and schedules, as clean rows ready for a warehouse, a spreadsheet or the next step of a pipeline.

What it collects

• Scraped records: the newest finished history of a report, or any history by id, one row per scraped record with every field under data, keyed by the report's own column names. The actor reads the history's JSON output file, or its CSV file when there is no JSON one.
• Run history: the histories of a report with status, item count, request count, upload and download bandwidth, start and end time and the CSV link; or its runs with run parameters and every output file link.
• Run search: the runs of a report whose run parameters match the values you give, such as one file name.
• Output files: the XLSX, XML, CSV and JSON download links of a history, with their expiry time.
• Run status: the status of the run behind a history.
• Parameters and schedules: the run parameters a report takes, its schedules with start, end and next update times, and the parameters set on a schedule.
• Projects: every project in the account, with status, type and schedule type.
• Read only, pay per result, bring your own key.

Input

Field	What it does
What to read	Projects (default, needs nothing else), latest scraped records of a report, scraped records of a history, histories, runs, search runs, files of a history, status of a history, parameters of a report, schedules, or parameters of a schedule.
Ids	One number per line: report ids, history ids or schedule ids, depending on the service.
Histories or runs per report	Histories and runs: how many to return per report.
Search parameters	Search runs: a JSON object of run parameter name to value.
Report id for schedule parameters	Parameters of a schedule: the report the schedules belong to.
Project type	Projects: WEBAPP (default) or any.
Maximum results	Row cap for the run.
Requests per minute	Pacing for calls to the provider, which allows 100 per minute.
API key	Your own API key, as a secret input.

Example output

{
  "service": "latestRecords",
  "serviceLabel": "Latest scraped records of a report",
  "requested": "104522",
  "found": true,
  "reportId": "104522",
  "historyId": "8841207",
  "status": "SUCCESS",
  "startedAt": "2026-09-28T06:00:12",
  "endedAt": "2026-09-28T06:41:55",
  "fileFormat": "JSON",
  "rowIndex": 0,
  "data": {
    "Product Name": "Trail Running Shoe 1042",
    "Price": "89.99",
    "Currency": "EUR",
    "Availability": "In stock",
    "Product URL": "https://shop.example.com/products/trail-running-shoe-1042"
  },
  "retrievedAt": "2026-09-29T09:14:52.118Z",
  "note": null
}

Values are illustrative; the columns under data are whatever your report extracts. A history row looks like this:

{
  "service": "histories",
  "requested": "104522",
  "found": true,
  "reportId": "104522",
  "historyId": "8841207",
  "status": "SUCCESS",
  "itemCount": 2488,
  "startedAt": "2026-09-28T06:00:12",
  "endedAt": "2026-09-28T06:41:55",
  "fileFormat": "CSV",
  "fileUrl": "https://files.example.com/oJElX0e",
  "details": { "requestCount": 126, "bandwidthUploadBytes": 25022, "bandwidthDownloadBytes": 1984907 }
}

FAQ

What is this web scraping data export API used for?

Getting data out of managed scraping projects that already run on a schedule and into the systems that use it. A pricing team pulls the latest competitor price and product scrape every morning into BigQuery, Snowflake or Google Sheets. An analyst lists last month's histories of a report to see item counts and which runs failed. An operations team checks request counts and bandwidth per run. An integration finds the run for one file name with a parameter search.

Which data source does this actor read?

The Grepsr API at api.grepsr.com, through the read routes of its public documentation at api-docs.grepsr.com: POST /v1/project/list, POST /v1/report/history/list, POST /v1/report/run/list, POST /v1/report/run/search, POST /v1/history/files, POST /v1/history/run/status, GET /v1/report/parameters/list, POST /v1/report/schedule/list and GET /v1/report/schedule/parameters. The provider documents most reads as POST requests with a JSON body; none of them writes anything. Scraped records come from the JSON or CSV output file a history links to.

Is this a scraping API that takes a URL?

No. The provider's documented API does not take a URL and return a page. It exports the output of the crawlers (reports) set up in your own account, which is what this actor reads.

Do I need an API key?

Yes. This actor is bring-your-own-key and never ships one. The key is shown under Personal Details on the Profile page of your Grepsr account. Paste it into the input, or set it once as the DATA_API_KEY environment secret. It is sent in the X-Api-Key header to the API host only, and never to the file download links. A missing or refused key ends the run cleanly with a message saying which it was.

How do I find report ids and history ids?

The provider has no route that lists the reports of a project, so a report id is the number in the report's address in the web app. With a report id, the histories or runs service lists the history ids. The latest scraped records service needs only the report id, which is usually all you need.

Can this actor run a report or change anything?

No. It never runs or stops a report, never stops a schedule and never calls the instant crawler. It reads what your reports have already collected.

What happens when there is nothing for an id?

It becomes its own row with found: false and a note: a report with no finished history yet, a history id the account cannot see, an expired file link, or a history delivered only as XLSX or XML. Those rows are never charged.

How is it priced?

Pay per result: one flat price per record returned, whether a scraped record, a project, a history, a run, a file link, a status, a parameter set or a schedule. Rows for ids that produced nothing are free. Your Grepsr subscription applies separately.

Pricing

Event	Price
Web scraping data record returned	$0.005 per record

Keyword map

web scraping data export, web scraping API, scraped data API, managed web scraping export, crawler output to database, scheduled scraping export, ecommerce product data export, competitor pricing data feed, scraping run history, Grepsr API, Grepsr reports, Grepsr histories, web data extraction export.