Skip to main content
GET

Overview

The Expired Jobs endpoint allows you to retrieve jobs that have been removed or expired from company career pages after a specified date. This is useful for tracking job lifecycle, maintaining data freshness, and identifying positions that are no longer active.

Authentication

This endpoint requires an API key for all requests, including page 1. See Authentication to get one.
string
required
Your Hirebase API key

Query Parameters

string
required
Starting date to retrieve expired jobs from. Accepts ISO date format (YYYY-MM-DD) or other standard date strings (e.g., 2026-01-31)
integer
default:"1"
Page number for pagination (min: 1)
integer
default:"100"
Number of results per page (min: 1, max: 1000)

Response

array
List of expired job objects
integer
Total number of expired jobs matching the query across all pages
integer
Current page number in the response
integer
Number of results returned per page
integer
Total number of pages available for the query (ceil(total_count / limit))

Use Cases

Data Cleanup

Identify and remove stale job postings from your database

Job Lifecycle Tracking

Monitor how long positions remain active

Market Analysis

Analyze hiring velocity by tracking when jobs are filled or closed

Database Synchronization

Keep your local job database in sync with Hirebase

Pagination

Use the page and limit parameters to paginate through large result sets:
Calculate total pages: use the total_pages field in the response, or ceil(total_count / limit).

Important Notes

The since parameter is required and must be a valid date string
  • Jobs are considered expired when they are no longer available on the company’s career page
  • The date_expired field represents when Hirebase detected the job was no longer active (not necessarily when the company removed it)
  • Results are sorted by date_expired in descending order (most recent first)
  • Maximum limit per request is 1000 jobs
  • For optimal performance, query smaller date ranges (e.g., daily or weekly) rather than large historical periods

Error Responses

Unprocessable Entity
Missing required since query parameter:
Bad Request
since is present but cannot be parsed as a date (hand-rolled validation after FastAPI accepts the request).
Unauthorized
Invalid or missing API key
Not Found
Invalid endpoint path
Too Many Requests
Rate limit exceeded