Common Errors

The following issues are commonly encountered when working with the Extraction API.

Missing API Key

Requests must include the X-Api-Key header.

Incorrect

curl -X POST "https://scraper.geonode.io/v1/extract"

Correct

curl -X POST "https://scraper.geonode.io/v1/extract" \
  -H "X-Api-Key: YOUR_API_KEY"

Invalid URL

The url field must contain a valid URL.

Incorrect

{
  "url": "example"
}

Correct

{
  "url": "https://example.com"
}

Job Still Processing

When using asynchronous extraction, the result may not be available immediately.

Response

{
  "status": "processing",
  "data": null
}

Wait until the job status becomes:

completed

before attempting to use the extracted content.

Job Not Found

A job may not exist or may belong to a different account.

Request

GET /v1/extract/{job_id}

Verify that the job ID is correct and that it was created using the same API key.

Empty or Unexpected Results

Some websites require JavaScript rendering before content becomes available.

Try enabling:

{
  "render_js": true
}

This is common for:

• React applications
• Next.js websites
• Vue applications
• Single-page applications

Geo-Targeted Content Is Different Than Expected

Some websites return different content based on location.

Specify a country explicitly:

{
  "proxy": {
    "country": "US",
    "type": "residential"
  }
}

Custom Headers Not Applied

Headers must be passed inside the headers object.

Correct

{
  "headers": {
    "Accept-Language": "en-US,en;q=0.9"
  }
}

Do not place your Geonode API key inside the headers object.

Authentication must use:

X-Api-Key

Link Extraction Does Not Crawl Websites

extract_links only returns links found on the extracted page.

{
  "extract_links": true
}

It does not visit discovered links or recursively crawl a website.

For large-scale URL discovery, use the Map API.

Using JavaScript Rendering Unnecessarily

JavaScript rendering increases extraction time.

{
  "render_js": true
}

Enable it only when a website requires client-side rendering.

Need More Help?

If you continue to experience issues:

• Verify the request payload
• Verify the target URL
• Check job status for asynchronous requests
• Review response metadata
• Contact the Geonode support team

Success

You now understand the most common Extraction API issues and how to resolve them.

What's Next

You have completed the Extraction guides.

Continue to the next API section to learn about additional scraping and data collection capabilities.