# Indeed Salaries API (indeed.salaries)

- Canonical page: [https://everyinfra.com/en/indeed-api/salaries](https://everyinfra.com/en/indeed-api/salaries?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "indeed", "action": "salaries", "params": {...}}
- Price: $0.001389 per call ($1.39 per 1,000 requests); failed calls and empty results are not charged
- Returns: list, default 20, max 100 per call
- Mode: sync; add "mode": "async" for slow tasks

Indeed Salaries reads the salary page of one employer on Indeed and returns one row per job title: the reported pay in `salary`, the pay period in `salary_type`, and how many people reported it in `reported_count`. Name the employer with `company`, the same way it appears in the Indeed company URL, for example Google for indeed.com/cmp/Google.

Recruiters use it to check an offer against what employees report, and analysts use it to compare pay for the same role across employers or locations. Read `salary_type` before comparing rows, since hourly, monthly and yearly figures sit side by side, and weigh each figure by `reported_count`: one report is an anecdote, while dozens make a usable benchmark.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=indeed&action=salaries

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| company | not declared | yes | not declared | Accepts an Indeed company short name or full /cmp/<company>/ URL. For company_reviews, pass the /reviews page URL directly; for salaries and interviews, the system extracts the entity from the URL and routes to the correct section. Passing a plain company name converts spaces to hyphens rather than executing a fuzzy search. |
| limit | integer (1–100) | no | 20 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |

## Response fields (items in `results`)

| field | meaning |
|---|---|
| job_title | platform-native meaning |
| category | Category name in the platform's own taxonomy, not normalized across platforms. |
| salary | platform-native meaning |
| salary_type | platform-native meaning |
| reported_count | platform-native meaning |
| company_name | platform-native meaning |
| company_salary_count | platform-native meaning |
| updated_at | platform-native meaning |
| platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
| location | Location description passed through as is; the format varies by platform. |
| url | Link to the record on the platform. |

## Example

```bash
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "indeed",
  "action": "salaries",
  "params": {
    "company": "Microsoft"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "indeed",
        "action": "salaries",
        "params": {
            "company": "Microsoft",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-09-26T08:56:04Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2 of 17. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "id": "req_…",
  "platform": "indeed",
  "action": "salaries",
  "results": [
    {
      "job_title": "Software Engineer",
      "category": "Popular Roles",
      "salary": "$142,889",
      "salary_type": "YEARLY",
      "reported_count": 394,
      "company_name": "Microsoft",
      "company_salary_count": 19446,
      "updated_at": "2026-09-21T00:00:00+00:00",
      "platform": "indeed"
    },
    {
      "job_title": "Senior Software Engineer",
      "category": "Popular Roles",
      "salary": "$170,583",
      "salary_type": "YEARLY",
      "reported_count": 301,
      "company_name": "Microsoft",
      "company_salary_count": 19446,
      "updated_at": "2026-09-21T00:00:00+00:00",
      "platform": "indeed"
    }
  ],
  "count": 17,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

## FAQ

### What do I pass as `company`?

The employer name as it appears in its Indeed company URL, such as Google from indeed.com/cmp/Google. Check the spelling against that URL first: a call that returns no rows is not charged, but it also tells you nothing about the employer.

### Why do some salaries look ten times smaller than others?

Indeed lists hourly, monthly and yearly pay on the same page, and `salary_type` says which one each row is. Convert every row to one period before you average or rank them; comparing raw numbers across periods is off by an order of magnitude.

### How much should I trust a single figure?

Look at `reported_count` for the row and `company_salary_count` for the employer. A figure backed by one or two reports is an anecdote; prefer rows with more reports when you benchmark, and keep both counts in your stored copy so readers can judge for themselves.

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=indeed
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md
