Batch

Listing Batch Jobs

Listing batch jobs allows you to retrieve previously created batch requests. This is useful when you want to review completed jobs, monitor running batches, or locate a job ID for checking its status.

Batch Jobs Endpoint

Use the following endpoint to retrieve previously created batch jobs.

GET /v1/batch/jobs

The response returns a paginated list of batch jobs.

List Batch Jobs

Use the following request to retrieve your recent batch jobs.

Request

request.sh
curl -X GET "https://scraper.geonode.io/v1/batch/jobs" \
  -H "X-Api-Key: YOUR_API_KEY"

Response

response.json
{
  "jobs": [
    {
      "job_id": "9e60e068-b6ac-408d-aa6e-f120f41faf0d",
      "status": "completed",
      "accepted_urls": 3,
      "completed_urls": 3,
      "failed_urls": 0,
      "config": {
        "render_js": false,
        "formats": [
          "markdown"
        ],
        "proxy": {
          "country": null,
          "type": "residential"
        },
        "headers": null,
        "wait_config": null
      },
      "created_at": "2026-07-05T16:29:56.344150Z",
      "completed_at": "2026-07-05T16:30:13.963398Z"
    }
  ],
  "page": 1,
  "page_size": 10,
  "page_count": 1
}

Understanding the Response

Each batch job contains summary information about the processing request.

FieldDescription
job_idUnique identifier for the batch job.
statusCurrent status of the batch job.
accepted_urlsNumber of valid URLs accepted when the batch was created.
completed_urlsNumber of URLs processed successfully.
failed_urlsNumber of URLs that failed during processing.
configConfiguration used when the batch job was submitted.
created_atTime the batch job was created.
completed_atTime the batch job finished processing.

The response also includes pagination information.

FieldDescription
pageCurrent page number.
page_sizeNumber of jobs returned per page.
page_countTotal number of available pages.

Filtering Batch Jobs

You can filter the returned jobs using query parameters.

Query ParameterDescription
statusReturn only jobs with a specific status.
start_dateReturn jobs created on or after the specified date.
end_dateReturn jobs created on or before the specified date.
pagePage number to retrieve.
page_sizeNumber of jobs to return per page.

Filter by Status

Retrieve only completed batch jobs.

request.sh
curl -X GET "https://scraper.geonode.io/v1/batch/jobs?status=completed" \
  -H "X-Api-Key: YOUR_API_KEY"

Supported values:

queued
processing
completed
failed
cancelled

Filter by Date Range

Retrieve jobs created within a specific time period.

request.sh
curl -X GET "https://scraper.geonode.io/v1/batch/jobs?start_date=2026-07-01&end_date=2026-07-31" \
  -H "X-Api-Key: YOUR_API_KEY"

Pagination

Retrieve a specific page of results.

request.sh
curl -X GET "https://scraper.geonode.io/v1/batch/jobs?page=2&page_size=10" \
  -H "X-Api-Key: YOUR_API_KEY"

Understanding Job Progress

The job summary makes it easy to see how a batch performed without retrieving the full job details.

ScenarioAccepted URLsCompleted URLsFailed URLs
All URLs processed successfully330
One URL failed321
Two URLs failed532

When to Use This Endpoint

Use this endpoint to:

  • View recent batch activity.
  • Find a previous batch job.
  • Monitor completed or failed batches.
  • Search jobs created within a specific date range.
  • Retrieve a job ID before checking detailed status.
  • Build dashboards or reporting tools.

Next Steps

Now that you know how to retrieve and filter batch jobs, continue to Cancelling Batch Jobs to learn how to stop a running batch job.

On this page