POST /api/habr/hubs/articles
Price: 5 credits
Get Habr Hub Articles
List articles or news inside a Habr hub. Order by date or rating over a period. Returns title, lead, tags, stats, author, and hubs.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)lang string — Content language (default: "ru"; one of: "ru", "en")hub string required — Hub alias or URL (examples: "python", "https://habr.com/ru/hubs/python/"; minLength: 1)news boolean — Return news posts instead of articles (default: false)sort string — Result ordering (default: "date"; one of: "date", "rating")period string — Time window when sort is rating (default: "daily"; one of: "daily", "weekly", "monthly", "yearly", "alltime")count integer required — Max result count (examples: 20; min: 1)@type string (default: "HabrArticleRef")id string requiredlead string nullableurl string nullableimage string nullablepost_type string nullablelang string nullablecomplexity string nullablereading_time integer nullableis_corporative boolean (default: false)tags array (default: [])published_at string nullableauthor object nullable@type string (default: "HabrAuthor")id string requiredalias string requiredfullname string nullablespeciality string nullableimage string nullablerating number nullablescore integer nullablestatistics object nullable@type string (default: "HabrArticleStatistics")comment_count integer nullablefavorite_count integer nullablereading_count integer nullablescore integer nullablevote_count integer nullablevote_count_plus integer nullablevote_count_minus integer nullablereach integer nullablereader_count integer nullablehubs array (default: [])@type string (default: "HabrHubRef")id string requiredalias string requiredflows array (default: [])@type string (default: "HabrFlowRef")id string requiredalias string required422 — 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 — Hub not found. Verify the alias. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.