POST
Search LinkedIn job postings from a free-text query. The response is normalized, so it keeps the same shape whichever offer served it. The call is synchronous and comes back completed or failed. Body fields and error codes shared by every service are documented on Run a service.

Body

string[]
required
The search queries to run, as queries (array) or query (single string). Free text, exactly as you would type it on LinkedIn.
string
Single-input form of queries.
number
default:"100"
Maximum number of records to return. Integer, 1-250.
string
Pin one offer, as source/name. Serving this service: brightdata/linkedin. Omit it (the default) to let the router walk the failover chain.
object
Typed options for this service. Validation is strict, so an unknown key or an out-of-enum value returns a corrective 400 instead of being dropped.

Accepted queries

A job title or keyword, as you would type it in LinkedIn’s job search. Example: product manager. Quote a phrase (“product manager”) for an exact match. The location option is required: LinkedIn scopes a job search to a place.

Offers

One offer serves this endpoint today. When a second one implements it, failover turns on with no change on your side. Prices are live in the catalogue: GET /v1/services/linkedin/job.search. See Credits for how a call is billed.

Response

data[] holds the normalized records, served_by names the offer that answered, and credits_used carries the actual charge. The example response is a real run with values shortened for readability. A field is present when LinkedIn exposes it for that item, so the exact set varies record to record.