Zhihu Salt search API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Search Zhihu Salt (paid) content by keyword, 20 per page, with title, free opening, column, cover, date and upvotes; the paid body is not included.

Price $0.81 per 1,000 requests ($0.000806 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

Please help me write a data collection script with the EveryInfra Zhihu Salt search endpoint (zhihu/salt_search).

How the endpoint works:
- 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 zhihu and action to salt_search, and put the parameters inside params.
- Required parameters:
- keyword: A keyword to search Zhihu Salt (paid) content, such as a genre like mystery or a theme like the workplace; Chinese-language terms match best.
- Optional parameters:
- page_token: Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received. 20 results per page; each page is one call.
- Returns a list of records. Main fields of each record: id, type, url, title, text, column_title (Name of the paid column or story collec…), cover_image_url (Cover image URL), posted_at, like_count, comment_count.
- Example request body:
{
"platform": "zhihu",
"action": "salt_search",
"params": {
"keyword": "python"
}
}
- Price: $0.81 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	`zhihu`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`salt_search`	Capability identifier, fixed value.
`keyword`	body.params	`string`	Yes	-	A keyword to search Zhihu Salt (paid) content, such as a genre like mystery or a theme like the workplace; Chinese-language terms match best.
`page_token`	body.params	`string`	No	-	Page token. Leave it out for the first page, then pass back the previous response's `next_page_token` exactly as received. 20 results per page; each page is one call.

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": "zhihu",
  "action": "salt_search",
  "params": {
    "keyword": "python"
  }
}'

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

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "zhihu",
  "action": "salt_search",
  "results": [
    {
      "id": …,
      "type": …,
      "url": …,
      "title": …,
      "text": …,
      "column_title": …,
      "cover_image_url": …,
      "posted_at": …,
      "like_count": …,
      "comment_count": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": …,
  "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.
`type`	Record type; values depend on the capability (for example video / image / text).
`url`	Link to the record on the platform.
`title`	Title. null when the platform has no titles (for example text-only posts).
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`column_title`	Name of the paid column or story collection the Salt item belongs to (salt_search).
`cover_image_url`	Cover image URL.
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`comment_count`	Comments. null means not disclosed, not 0.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors