/vk/posts/comments

POST /api/vk/posts/comments

Price: 5 credits

Get comments on a VK wall post by {owner_id}_{post_id} or post URL: each comment with author, text, date, likes, reply count, attachments and nested reply thread.

How to use it

Fetch comments on a VK wall post identified by {owner_id}_{post_id} (e.g. -22822305_1703293) or a wall post URL. Each comment has author, text, created_at, like_count, reply_count, images, attachments and thread (nested replies).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — VK wall post in {owner_id}_{post_id} form or a wall post URL (examples: "-22822305_1703293", "1_2442097", "https://vk.com/wall-22822305_1703293"; minLength: 1)
• count integer required — Max number of comments to return (examples: 20; min: 1)
• offset integer — Number of comments to skip (default: 0; min: 0)
• sort string — Comment ordering by date (default: "asc"; one of: "asc", "desc")

Response

• @type string (default: "VkComment")
• id integer required
• from_id integer nullable
• author object nullable
  • @type string (default: "VkAuthor")
  • id integer required
  • name string nullable
  • alias string nullable
  • image string nullable
  • is_group boolean (default: false)
  • is_verified boolean (default: false)
• created_at integer nullable
• text string nullable
• like_count integer nullable
• reply_count integer nullable
• reply_to_user_id integer nullable
• reply_to_comment_id integer nullable
• images array (default: [])
• attachments array (default: [])
  • @type string (default: "VkAttachment")
  • attachment_type string nullable
  • image string nullable
  • link_url string nullable
  • attachment_title string nullable
  • description string nullable
  • duration integer nullable
  • view_count integer nullable
  • platform string nullable
• thread array (default: [])

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 — Post not found or comments disabled. 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.