praxyjobs
Browse documentation
On this page

API

Job schema

Every row has a stable identity, a direct path to the employer, and enough source metadata to verify where it came from.

Example job

json
{
  "job_key": "greenhouse:acme:45812",
  "title": "Senior Data Engineer",
  "organization": "Acme",
  "apply_url": "https://boards.greenhouse.io/acme/jobs/45812",
  "status": "open",
  "locations": [{ "city": "Berlin", "country": "DE" }],
  "employment_types": ["FULL_TIME"],
  "source": "greenhouse",
  "source_slug": "acme",
  "source_endpoint": "https://boards-api.greenhouse.io/v1/boards/acme/jobs",
  "first_seen_at": "2026-07-18T08:12:40Z"
}

Identity and source

job_key is the stable Praxy identifier. source, source_slug, source_endpoint, and directory_verified_at form the verification receipt. apply_url points to the employer's native application flow.

Location and workplace

Structured locations preserve published city, region, and country values. Work arrangement is normalized to remote, hybrid, on_site, or unknown and retains provenance where it is derived.

Null and missing fields

Fields the employer did not publish are omitted rather than invented. Structured location keys are the exception: their shape is stable and unknown values are explicitly null.

Was this page helpful?
YesNot yet