ZipRecruiter Data API: Extract Structured JSON in 2026

This guide covers extracting publicly accessible data. Always review a site's robots.txt and Terms of Service before scraping.

TL;DR

Use AlterLab's Extract API to turn any ZipRecruiter job page into typed JSON. Define a schema for the fields you need, POST the URL and schema, and receive validated data without writing parsers. The service handles anti‑bot measures, proxies, and automatic retries.

Why use ZipRecruiter data?

Job listings are a rich source for market analysis, salary benchmarking, and training AI models. Teams extract this data to:

• Build datasets for large language model fine‑tuning on employment trends.
• Monitor competitor hiring patterns and emerging skill demands.
• Power internal tools that match candidate profiles with open roles in real time.

What data can you extract?

From a typical ZipRecruiter job page you can pull the following publicly visible fields:

• job_title – the role title as displayed.
• company – the hiring organization name.
• location – city, state, or remote designation.
• salary – listed compensation range or exact figure.
• posted_date – when the listing went live.
• employment_type – full‑time, part‑time, contract, or internship.

All fields are returned as strings unless you specify otherwise in the schema.

The extraction approach

Raw HTTP requests followed by HTML parsing break frequently because ZipRecruiter updates its markup, serves dynamic content via JavaScript, and employs anti‑bot techniques. Maintaining selectors, handling pagination, and solving CAPTCHAs consumes engineering effort that does not add value to your core product.

A data API abstracts those concerns. You provide a URL and a JSON schema; the platform returns typed JSON. This shifts the work from fragile scraping to reliable data delivery.

Quick start with AlterLab Extract API

See the Getting started guide for installation steps. Below are ready‑to‑run examples.

Python example

import alterlab

client = alterlab.Client("YOUR_API_KEY")

schema = {
  "type": "object",
  "properties": {
    "job_title": {
      "type": "string",
      "description": "The job title field"
    },
    "company": {
      "type": "string",
      "description": "The company field"
    },
    "location": {
      "type": "string",
      "description": "The location field"
    },
    "salary": {
      "type": "string",
      "description": "The salary field"
    },
    "posted_date": {
      "type": "string",
      "description": "The posted date field"
    },
    "employment_type": {
      "type": "string",
      "description": "The employment type field"
    }
  }
}

result = client.extract(
    url="https://ziprecruiter.com/example-page",
    schema=schema,
)
print(result.data)

cURL example

curl -X POST https://api.alterlab.io/v1/extract \
  -H "X-API-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://ziprecruiter.com/example-page",
    "schema": {"properties": {"job_title": {"type": "string"}, "company": {"type": "string"}, "location": {"type": "string"}}}
  }'

The response is a JSON object whose keys match the schema you supplied. No further parsing is required.

Define your schema

The Extract API uses JSON Schema to validate and shape the output. By declaring the expected types, you guarantee that downstream consumers receive predictable data. For example, if you need the salary as a number you can add a transformation step later, but the raw extraction returns the string as shown on the page.

AlterLab validates the extracted content against your schema before returning it. If a field cannot be found, the API returns null for that property, keeping the structure intact.

Handle pagination and scale

ZipRecruiter lists many jobs per search result page. To collect large datasets you need to iterate through pages. The platform supports async job submission and webhook delivery so you can process thousands of URLs without blocking.

Batch/async example

import alterlab
import asyncio

client = alterlab.Client("YOUR_API_KEY")
schema = {
  "type": "object",
  "properties": {
    "job_title": {"type": "string"},
    "company": {"type": "string"},
    "location": {"type": "string"}
  }
}

async def extract_one(url):
    return await client.extract_async(url=url, schema=schema)

urls = [
    f"https://ziprecruiter.com/jobs-search?page={i}" for i in range(1, 101)
]

# Fire all requests concurrently
results = await asyncio.gather(*[extract_one(u) for u in urls])
for r in results:
    print(r.data)

When you scale, review the AlterLab pricing page to estimate costs. The service charges per extraction, with a minimum of $0.001 and a maximum of $0.50 per call. There are no monthly minimums, and you only pay for what you use.

Key takeaways

• Use a data API to avoid fragile HTML parsers and anti‑bot maintenance.
• Define a JSON schema to receive typed, validated output.
• Paginate through search results with async calls for high‑volume pipelines.
• Cost is usage‑based with no minimums; see pricing for details.
• Always verify that your extraction complies with ZipRecruiter's robots.txt and Terms of Service.