Social platforms

List the hiring team of a LinkedIn job · LinkedIn API

GET/linkedin/jobs/{id}/hiring-team
$min $0.009

Returns the people LinkedIn lists as the hiring team for a job posting.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/linkedin/jobs/{id}/hiring-team \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

idpathrequired
LinkedIn job id, as in linkedin.com/jobs/view/{id}.
The parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the LinkedIn API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs LinkedIn public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Enrich public company and job data from LinkedIn for prospecting or market-research agents.
  • Keep company-specific lookups in the same billing and observability surface as social and web data.
  • Give an AI agent a stable LinkedIn data source without building a per-platform integration.
  • Normalize LinkedIn responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 9 credits ($0.009) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 9 credits ($0.009) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields on each record in data

A successful List the hiring team of a LinkedIn job call returns data as an array; each record carries these fields.

entity_idstring | null
Person entity ID.
usernamestring | null
Person handle.
namestring | null
Person name.
headlinestring | null
Person headline.
rolestring | null
Hiring role.
profile_picture_urlstring | null
Profile image URL.
urlstring | null
Profile URL.