LinkedIn job API

LinkedIn job data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

1 documented endpoints
GET /v1/linkedin/jobs/{id}

Contract summary (English): Get the LinkedIn job detail (capability linkedin.job)

Normalized response entity: linkedin/job
capability: linkedin.job

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

Feed content-analysis pipelines with structured {{platform}} posts: text, metrics, timestamps and media references.
Power moderation, research and monitoring workflows that need the original content plus engagement counts.
Archive {{platform}} content as stable, normalized JSON instead of brittle page scraping.

Response fields

LinkedIn job card (normalized non-entity payload)

Non-entity payload (type job) — the entity layer clean-skips it; served by the /v1/linkedin surface.

Field	Type	Required	Description
id	string \| null	Required	—
title	string \| null	Required	—
company	string \| null	Optional	—
location	string \| null	Optional	—
description	string \| null	Optional	—
employment_type	string \| null	Optional	—
posted_at	string \| null	Optional	—
platform	"linkedin"	Required	—
type	"job"	Required	—
fetched_at	string	Required	Normalization time (UTC).

Field notes are shown in the contract's original English.

Response meta

Field	Type	Required	Description
mode	cache \| default \| live	Required	Effective mode after merging param > max_age > source policy (D-004).
age_seconds	integer \| null	Optional	Age of served data; null when unknown.
source_layer	cache \| db \| upstream	Required	Which layer served the response (PRD §10).
stale	boolean	Optional	True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_credits	integer	Required	Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hit	boolean	Required	—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/linkedin/jobs/{id}

curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/linkedin/jobs/1842951234567890123"

{
  "data": {
    "id": "6257000000001001",
    "platform": "linkedin",
    "type": "job",
    "title": "数据平台工程师",
    "company": "MeshData",
    "location": "Remote",
    "description": "数据平台工程师职位。",
    "employment_type": "FULL_TIME",
    "posted_at": "2026-09-15T11:20:00Z",
    "fetched_at": "2026-09-21T09:00:00Z"
  },
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 100,
      "cache_hit": false
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

Which content fields are included?

The normalized content entity — text, author, timestamps, engagement metrics and media references — as documented in the field table below, plus freshness and billing metadata.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the job capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.

View pricing Browse all APIs