/cninfo/interactions/search

POST /api/cninfo/interactions/search

Price: 5 credits

Search investors' questions to Shenzhen-listed companies and the companies' answers on the CNINFO investor interaction platform (互动易), by keyword and answer status, each with the question, answer, company and times

How to use it

Covers roughly the last three months of questions, most recently updated first; `updated_from` and `updated_to` bound the day of a question's last update, not the day it was asked. Several keywords separated by a space narrow the match. For one company's questions use cninfo/companies/interactions.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of questions to return (min: 1; max: 10000)
• keyword string nullable — Words to find in questions and answers (examples: "电池", "电池 储能"; minLength: 1)
• status string nullable — Keep only answered or only unanswered questions (one of: "answered", "unanswered")
• updated_from integer nullable — Earliest day of the question's last update, as unix seconds; day-granular (examples: 1788220800)
• updated_to integer nullable — Latest day of the question's last update, as unix seconds; day-granular (examples: 1790812800)

Response

• @type string (default: "CninfoInteraction")
• id string required
• is_answered boolean nullable
• question string nullable
• answer string nullable
• company_code string nullable
• company_name string nullable
• org_id string nullable
• industries array (default: [])
• board_type_codes array (default: [])
• asked_at integer nullable
• updated_at integer nullable
• answered_at integer nullable
• answered_by string nullable
• author_id string nullable
• author_name string nullable
• client_code string nullable
• like_count integer nullable
• favorite_count integer nullable
• forward_count integer nullable

Errors

• 422 — count is out of range or keyword is empty Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.