LinkedIn API Capability

Get Company Life Page

Fetches a company's public employer-brand Life page with its descriptive content and imagery.

Capability ID linkedin.company.life.get

Cost 1 credit per request

Maximum runtime 60 seconds

# Get Company Life Page

Fetches a company's public employer-brand Life page with its descriptive content and imagery.

- Platform: [LinkedIn](https://docs.upscrape.com/docs/platforms/linkedin)
- Capability ID: `linkedin.company.life.get`
- Cost: 1 credit per request
- Maximum runtime: 60 seconds
- Execute endpoint: `POST https://data.upscrape.com/execute`

## Request

Use the exact public capability ID in the shared execute envelope.

```bash
curl --request POST \
  --url https://data.upscrape.com/execute \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Prefer: wait=30" \
  --data '{
  "input": {
    "url": "https://www.linkedin.com/company/microsoft/life"
  },
  "capability": "linkedin.company.life.get"
}'
```

## Input

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | `string` | Yes | LinkedIn company slug or HTTPS /company/{slug}/life URL. |

### Example input

```json
{
  "url": "https://www.linkedin.com/company/microsoft/life"
}
```

## Response

Successful output is returned in `results[0].data`. Raw platform output is intentionally open-ended and may evolve with the upstream source.

### Illustrative sample output

This redacted fixture is an example, not a fixed response schema.

```json
{
  "company_slug": "microsoft",
  "content_length": 0,
  "cover_image": "https://media.licdn.com/dms/image/v2/D560BAQH32RJQCl3dDQ/company-logo_200_200/B56ZYQ0mrGGoAM-/0/1744038948046/microsoft_logo?e=2147483647&v=beta&t=[redacted:token]",
  "description": "Microsoft | 28,915,963 followers on LinkedIn. Every company has a mission. What's ours? To empower every person and every organization to achieve more.",
  "title": "Microsoft: Life",
  "url": "https://www.linkedin.com/company/microsoft/life"
}
```
### Illustrative output fields

Derived from the sample above for orientation only. These fields are not a fixed response schema.

| Path | Observed type | Example |
| --- | --- | --- |
| `company_slug` | `string` | microsoft |
| `content_length` | `integer` | 0 |
| `cover_image` | `string` | https://media.licdn.com/dms/image/v2/D560BAQH32RJQCl3dDQ/company-logo_2… |
| `description` | `string` | Microsoft \| 28,915,963 followers on LinkedIn. Every company has a missi… |
| `title` | `string` | Microsoft: Life |
| `url` | `string` | https://www.linkedin.com/company/microsoft/life |

## Execution behavior

A `200` response completed inline. A `202` response was queued; poll `GET /jobs/{id}` until the job reaches `completed` or `failed`. Use an `Idempotency-Key` when retrying must not create a duplicate logical job.

## Related documentation

- [Authentication](https://docs.upscrape.com/docs/api/authentication)
- [Jobs and results](https://docs.upscrape.com/docs/api/jobs)
- [Errors and retries](https://docs.upscrape.com/docs/api/errors)
- [Idempotency](https://docs.upscrape.com/docs/api/idempotency)

POST /execute Shared execution endpoint

Input parameters

url string required

LinkedIn company slug or HTTPS /company/{slug}/life URL.

Example https://www.linkedin.com/company/microsoft/life

Response

Successful output is returned in results[0].data. Raw platform output is intentionally open-ended and may evolve with the upstream source.

Illustrative sample The full redacted fixture is shown in the response panel.

Illustrative output fields

Derived from the sample above for orientation only. These observed fields are not a fixed response schema.

Path	Observed type	Example
`company_slug`	`string`	microsoft
`content_length`	`integer`	0
`cover_image`	`string`	https://media.licdn.com/dms/image/v2/D560BAQH32RJQCl3dDQ/company-logo_2…
`description`	`string`	Microsoft \| 28,915,963 followers on LinkedIn. Every company has a missi…
`title`	`string`	Microsoft: Life
`url`	`string`	https://www.linkedin.com/company/microsoft/life

Execution behavior

A 200 response completed inline. A 202 response was queued; poll GET /jobs/:id until the job reaches completed or failed.

curl --request POST \ --url https://data.upscrape.com/execute \ --header "Authorization: Bearer YOUR_API_KEY" \ --header "Content-Type: application/json" \ --header "Prefer: wait=30" \ --data '{ "input": { "url": "https://www.linkedin.com/company/microsoft/life" }, "capability": "linkedin.company.life.get" }'

import json import requests payload = json.loads(r'''{ "input": { "url": "https://www.linkedin.com/company/microsoft/life" }, "capability": "linkedin.company.life.get" }''') response = requests.post( "https://data.upscrape.com/execute", headers={ "Authorization": "Bearer YOUR_API_KEY", "Content-Type": "application/json", "Prefer": "wait=30", }, json=payload, ) response.raise_for_status() print(json.dumps(response.json(), indent=2))

{ "company_slug": "microsoft", "content_length": 0, "cover_image": "https://media.licdn.com/dms/image/v2/D560BAQH32RJQCl3dDQ/company-logo_200_200/B56ZYQ0mrGGoAM-/0/1744038948046/microsoft_logo?e=2147483647&v=beta&t=[redacted:token]", "description": "Microsoft | 28,915,963 followers on LinkedIn. Every company has a mission. What's ours? To empower every person and every organization to achieve more.", "title": "Microsoft: Life", "url": "https://www.linkedin.com/company/microsoft/life" }