Skip to main content
POST
Export Expired Jobs
Export the full expired-jobs feed since a given date as a downloadable JSONL file. This endpoint creates an async task and returns immediately; poll Get Task Status for the download URL.
This is the intended path for large historical pulls. The Expired Jobs feed is subject to deep-pagination limits (only roughly the most recent 350–450k records of a window are reachable page-by-page). The export walks the entire result set server-side with no page-depth limit — a one-week window of ~1M records exports completely.
This endpoint requires an API key for all requests. See Authentication.

Endpoint

Authentication

string
required
Your Hirebase API key

Request Body

string
required
Starting date/datetime to export expired jobs from. Accepts ISO 8601 date ("2026-08-15") or full datetime ("2026-08-15T14:00:00Z"). Naive datetimes are treated as UTC. Invalid values return 400 with a descriptive message; a missing since returns 422.
boolean
default:"false"
Set to true to receive an email at your account address when the export completes, containing the download link.
There is no format field — expired-jobs exports are always JSONL (one JSON object per line).

Metering

Expired-jobs exports are free: they cost 0 units of your Jobs API allowance (m_jobs_api_calls), regardless of how many records they export. Expired data is not billed; only live job data is.

Response

Returns a task object (type: "export_expired_jobs", initial state: "queued"). Poll GET /v2/tasks/{task_id}; when state is "finished", result contains:
object

Exported Record Fields

Each JSONL line contains exactly:
  • _id — unique job identifier; use it as job_id in GET /v2/jobs/{job_id}
  • company_slug
  • job_slug
  • date_expired (YYYY-MM-DD)

Example