Public Schema Contracts · OpenAPI 3.1 + JSON Schema 2020-12
Job listing JSON Schemas and OpenAPI contracts
These are the machine-readable contracts behind the canonical /v1 API and the versioned datasets. Per JPE-RFC-0001, they are the source of truth — SDKs, tests, validators, and AI agents should generate against them, not against scraped page copy.
Job listing schema
Defines a single job listing as it appears in /v1/jobs responses and public CSV snapshots (e.g. listings-june-2026.csv). Fields preserve provenance signals (url, apply_link) and ingest lifecycle (ingestion_date, ingest_utc_date, ingest_utc_hour, validated_on, listing_closed) so downstream consumers can reason about origin and freshness without re-deriving them.
Launch metrics schema
Aggregate request and unique-IP rollups across the public usage dashboards. Surfaces only coarse counters (totals, daily averages, hourly buckets) — never raw IPs or user identifiers. Backs the public "Who uses JobDataPool" panel.
Source catalog & health
/v1/sources returns the canonical source catalog — repository, DVC pointer, R2 CSV URL, schema reference, and downstream endpoint relationships for every pooled source. /v1/health returns ecosystem heartbeat and version metadata.
Error schema
All non-2xx API responses follow the same ErrorResponse envelope so downstream tooling can parse failures uniformly. See the errors and rate limiting section for HTTP status semantics.
Standards posture
- JSON Schema 2020-12 — the modern, stable draft used across all schemas in this folder.
- OpenAPI 3.1 — aligned with JSON Schema 2020-12; the single source of truth for the
/v1API. - Stable URLs — schema paths are versioned by name; breaking changes ship at new paths, not in place.
- Free, public, no-auth — intentionally easy to consume from CI, SDK generators, and AI agents.