Indeed Interviews API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Check what candidates report about interviewing at a company on Indeed: questions asked, process stories and time from application to start. These are past accounts and do not predict the current hiring process.

Indeed Interviews reads the interview section of one employer's Indeed page and returns a single record: the interview questions candidates report, their own accounts of how the process went, and how long it took from application to starting the job. Career coaching services and job platforms use it to prepare candidates for a specific employer, and recruiters and employer branding teams use it to see how a hiring process looks from the outside and how its length compares with other employers.

Name the employer in company with its Indeed short name, such as Microsoft, or any link to its /cmp/<company>/ page. questions and process_stories are text written by candidates, so weigh a theme by how many candidates mention it rather than by one vivid account, and read hiring_durations as a distribution rather than one figure.

Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Indeed Interviews endpoint (indeed/interviews).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to indeed and action to interviews, and put the parameters inside params.
- Required parameters:
  - company: Accepts an Indeed company short name or full /cmp/<company>/ URL. For company_reviews, pass the /reviews page URL directly.
- Returns one object. Main fields: id, url, company_name, hiring_durations, questions, process_stories.
- Example request body:
{
  "platform": "indeed",
  "action": "interviews",
  "params": {
    "company": "Microsoft"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`indeed`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`interviews`	Capability identifier, fixed value.
`company`	body.params	Not declared	Yes	-	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.

Code samples

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": "interviews",
  "params": {
    "company": "Microsoft"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "indeed",
  "action": "interviews",
  "results": {
    "id": …,
    "url": …,
    "company_name": …,
    "hiring_durations": …,
    "questions": …,
    "process_stories": …,
    "platform": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`url`	Link to the record on the platform.
`company_name`	Keeps the platform's own meaning
`hiring_durations`	Keeps the platform's own meaning
`questions`	Keeps the platform's own meaning
`process_stories`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

Why do I get one record instead of a list?

This capability summarizes the employer's interview section as a whole: one record holds the reported questions, the candidate accounts in process_stories and the timing in hiring_durations. Expand those lists yourself if you want one row per question or per story.

How should I read `hiring_durations`?

It describes how long hiring took, from application to starting the job, as a distribution rather than a single number. Look at where most of it falls instead of the fastest or slowest case, and compare employers only when you read their distributions the same way.

Can I pass a link to another section of the company page?

Yes. Any /cmp/<company>/ link works, whether it points at the reviews, salaries or jobs part of the page: the call takes the employer from the link and reads its interviews section. A link also spares you from guessing how a name with spaces is written in Indeed's URL.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

Indeed: Candidate-Shared Interview Experiences ↗
Indeed notes that interview details originate from other job candidates to help users understand past experiences, questions, and common workflows. This information does not constitute an official employer question bank, nor does it mean this endpoint provides mock interview services.
Checked 2026-09-04