# Job schema (/docs/schema/job)



{/*
  AUTO-GENERATED. Do not hand-edit.
  Source: packages/social-api/src/docs/generate-schema-pages.ts
  Regenerate with: pnpm -F @repo/social-api generate:docs
  Field tables derive from the canonical Zod schemas (packages/social-api/src/schemas/canonical.ts);
  availability + equivalence derive from the registry fieldMaps.
  */}

Job schema [#job-schema]

Every SocialCrawl endpoint that returns a job posting gives you this exact shape, whatever the source platform. Write your parser once and the same code reads job data from every platform below. That is the unified schema: one contract instead of a dozen raw upstream formats.

Field reference [#field-reference]

| Field              | Type                | Nullable | Description                      |
| ------------------ | ------------------- | -------- | -------------------------------- |
| `id`               | `string`            | No       |                                  |
| `title`            | `string`            | Yes      |                                  |
| `url`              | `string`            | Yes      |                                  |
| `company.id`       | `string`            | Yes      |                                  |
| `company.name`     | `string`            | Yes      |                                  |
| `company.url`      | `string`            | Yes      |                                  |
| `company.verified` | `boolean`           | Yes      |                                  |
| `location`         | `string`            | Yes      |                                  |
| `listed_at`        | `string or integer` | Yes      | Union: string \| integer \| null |
| `easy_apply`       | `boolean`           | Yes      |                                  |
| `remote`           | `string`            | Yes      |                                  |
| `employment_type`  | `string`            | Yes      |                                  |
| `experience_level` | `string`            | Yes      |                                  |
| `description`      | `string`            | Yes      |                                  |
| `apply_url`        | `string`            | Yes      |                                  |

Extension fields (`ext`) [#extension-fields-ext]

Platform-specific passthrough. Each field is present only on the platforms that expose it and is absent everywhere else, so treat every `ext.*` field as optional. These carry the richer, per-platform signals the unified leaves cannot hold, and the join keys that chain endpoints together.

| Field                 | Type       | Nullable | Description |
| --------------------- | ---------- | -------- | ----------- |
| `ext.is_promote`      | `boolean`  | Yes      |             |
| `ext.applicant_count` | `integer`  | Yes      |             |
| `ext.skills`          | `string[]` | Yes      |             |

Platform availability [#platform-availability]

1 platform returns the `Job` shape. `id` are never null on any platform. The fields below vary: **yes** means the platform populates it (the value may still be null); a blank means the platform never provides it, so it is always null.

<div className="overflow-x-auto">
  | Platform | `title` | `url` | `company.id` | `company.name` | `company.url` | `company.verified` | `location` | `listed_at` | `easy_apply` | `remote` | `employment_type` | `experience_level` |
  | -------- | ------- | ----- | ------------ | -------------- | ------------- | ------------------ | ---------- | ----------- | ------------ | -------- | ----------------- | ------------------ |
  | LinkedIn | yes     | yes   | yes          | yes            | yes           | yes                | yes        | yes         | yes          |          |                   |                    |
</div>

Machine-readable schema [#machine-readable-schema]

Validate responses programmatically against the JSON Schema (2020-12):

[`/schemas/job.json`](/schemas/job.json)

Point a validator (Ajv, `jsonschema`, or your framework's) at that URL, or hand it to an agent so it can check the shape without a live call.

Returned by [#returned-by]

Endpoints with the `Job` / `JobList` archetype return this shape:

[LinkedIn](/platforms/linkedin)

See how the same fields map to each platform's raw upstream names in the [cross-platform field equivalence table](/docs/schema/field-equivalence).