/sravni/reviews/search

POST /api/sravni/reviews/search

Price: 1 credit

Search customer reviews of Russian banks, insurance companies and microfinance companies on Sravni.ru

How to use it

Search customer reviews on Sravni.ru across banks, insurance companies, and microfinance companies. Filter by organization type, product-category tag, rating sentiment, and location; order by date or popularity. Returns each review's title, text, star rating, moderation status, date, product category, author name, reviewed organization id, helpful vote counts, comment count, and reviewer location.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• review_object_type string — Type of organization reviews are about (default: "banks"; one of: "banks", "insuranceCompany", "mfo")
• tag string nullable — Filter by product category tag (examples: "debitCards", "mortgage", "creditCards", "credits", "casco", "osago")
• order_by string — Result ordering (default: "byDate"; one of: "byPopularity", "byDate")
• filter_by string — Review subset (default: "all"; one of: "all", "withRates")
• rated string — Filter by rating sentiment (default: "any"; one of: "any", "good", "bad")
• location_gar_id string nullable — Filter by GAR location id
• count integer required — Number of reviews to return (min: 1)

Response

• @type string (default: "SravniReview")
• id integer required
• text string nullable
• rating integer nullable
• rating_status string nullable
• created_at string nullable
• review_object_id string nullable
• review_object_type string nullable
• tag string nullable
• specific_product_name string nullable
• author_name string nullable
• author_last_name string nullable
• is_legal boolean nullable
• is_sravni_client boolean (default: false)
• is_recommended boolean nullable
• problem_solved boolean (default: false)
• has_company_response boolean (default: false)
• comment_count integer nullable
• positive_vote_count integer nullable
• negative_vote_count integer nullable
• location object nullable
  • @type string (default: "SravniReviewLocation")
  • id integer nullable
  • alias string nullable
  • name string nullable
  • full_name string nullable

Errors

• 422 — The request body did not validate 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.