Incremental ingestion
Fetch only changes within a time window or after your saved cursor.
JOB FEED API
A job feed API that tells you what changed.
Static job dumps become stale immediately. Praxy Jobs exposes separate lifecycle feeds so downstream products can ingest new openings, update changed fields, and remove closed roles without repeatedly downloading the entire corpus.
What your product gets
Explicit expirations
Receive stable identifiers and closure context for jobs that are no longer open.
Recoverable sync
Cursor-based pagination makes scheduled imports easier to resume and observe.
From first request to production sync
01
Backfill
Select the initial slice of jobs your product needs through search or active feeds.
GET /v1/feed/active02
Checkpoint
Persist the response cursor after each successfully processed page.
next_cursor03
Reconcile
Apply modified records and retire identifiers emitted by the expired feed.
GET /v1/feed/expiredBuilt for real product workflows
- ✓Search-index synchronization
- ✓Warehouse ingestion
- ✓Job-board freshness
- ✓Hiring-signal pipelines
Frequently asked questions
What is the difference between job search and a job feed?
Search retrieves records matching filters. Feeds are designed for recurring synchronization and expose jobs by lifecycle event or time window.
How are expired jobs represented?
The expired feed returns stable job identifiers with closure timestamps and close reasons where available.
Can a failed import resume?
Yes. Consumers can persist cursors and continue after the last successfully processed page.
Are feeds included in every paid plan?
The complete production API is included; plans differ by the monthly number of jobs returned.
Build on source-verified job data.
Start at 100,000 jobs returned per month. Upgrade when your product grows.