Start building

LinkedIn Jobs (index) API docs

Open Playground →

Start building

Send your first request

Platform API endpoint with unified authentication and usage tracking.

Production API
Platform API endpoint
https://api.sandbase.ai/v1/api/linkedin/jobs-thin
Authorization header
Authorization: Bearer $SANDBASE_API_KEY
# The quoted heredoc keeps Unicode and shell metacharacters unchanged.
result=$(curl --fail-with-body --silent \
  -X POST "https://api.sandbase.ai/v1/api/linkedin/jobs-thin" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary @- <<'SANDBASE_JSON'
{
  "limit": 3,
  "query": "software engineer",
  "location": "United States",
  "workplaceType": "remote"
}
SANDBASE_JSON
)
printf '%s\n' "$result"

2. Authentication

Set your SandBase API key in your server environment. Requests use Bearer authentication.

API key environment variable
export SANDBASE_API_KEY="YOUR_API_KEY"

Keep your key on the server. Do not expose it in browser code.

3. Parameters

querystringrequired

Job title or keywords to search.

geoIdstring

LinkedIn geo id to target a precise location (e.g. 103644278 for the United States); more exact than the free-text location.

limitinteger

Accepted for compatibility and ignored: each call returns one full source page (10 or 25 jobs depending on source); follow nextCursor for more.

cursorstring

Opaque pagination cursor from a previous response's nextCursor. Omit for the first page; pass it to fetch the next page of job listings.

locationstring

City, region, or country to search within.

companyIdstring

Filter to a specific company by its LinkedIn numeric company id.

postedLimitstring

Only jobs posted within this window (past 24 hours, week, or month).

Possible values: 24h, week, month

requireFieldsarray

Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `logoUrl`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a listing that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

workplaceTypestring

Filter by workplace type (remote, hybrid, or onsite).

Possible values: remote, hybrid, onsite

employmentTypestring

Filter by employment type.

Possible values: full-time, part-time, contract, internship, temporary

experienceLevelstring

Filter by required seniority/experience level.

Possible values: internship, entry, associate, mid-senior, director, executive

4. Response

Saved example response for this API; no live request is made when viewing it.

No saved response has been published. Run the API in Playground to inspect its response.