> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Does country_code US restrict comments to US users?

> country_code: US in youtube.web_v2.get_video_comments sets the collection context and defaults to US, but does not filter comments to US residents.

No. `country_code: US` is a collection setting on `youtube.web_v2.get_video_comments` and does not restrict returned comments to commenters located in the US. To identify feedback relevant to the US market, look for comments that explicitly describe local use, purchases, or shipping, and label those statements as self-reported.

## Example: a product team wants US-market complaints

A product team asking for US-market complaints can mean two distinct deliverables:

* **Comments collected under a US request setting:** Record `country_code=US`, the selected videos, the sort order, the language setting, the collection time, and the observed coverage. That record provides a reproducible collection specification.
* **Complaints from commenters who explicitly describe US use:** Retain the exact supporting quote and mark the quote as self-reported context rather than verified residence or nationality. A dollar price, English text, a profile name, or a flag emoji alone is not proof of location.

If a comment states no location, record "not stated." A comment such as "shipping to the US took two weeks" supports a claim about that specific shipment, not a permanent home address or verified buyer status. Keep the boundary between request parameters and commenter evidence explicit in the final conclusion.

## Keep the collection settings explicit

```json
{"action":"youtube.web_v2.get_video_comments","params":{"video_id":"<eleven_character_video_id>","country_code":"US","language_code":"en-US","sort_by":"newest","need_format":true}}
```

Replace `<eleven_character_video_id>` with the real eleven-character video ID. The JSON above illustrates Social Data request parameters rather than a comment-response schema. `country_code` currently defaults to `US` and `language_code` defaults to `zh-CN`, so record both values explicitly to avoid assuming every default is English. `en-US` neither translates comments nor guarantees English-only text. When changing `country_code` or `language_code`, record the new query context and never reuse a `continuation_token` from a previous context.

## What should the report contain?

Include these columns in the deliverable: source video, collection settings and time, exact complaint text, the supporting quote for any market claim, and evidence status (`self-reported` / `not stated`). Populate comment identifiers only when a verified response mapping includes comment IDs, and never add IP address or geolocation columns.

Example conclusion: "These are complaints observed in the selected videos under the recorded US request setting. Market-specific statements are labeled separately; no verified US-buyer count was established." The wording above is a reporting template rather than a record of a collected sample. The share of English comments is not the share of US viewers, and neither `top` nor `newest` returns a random sample of all commenters.

Every comment page requested is billed separately. See the [BeatAPI pricing page](https://beatapi.io/pricing).

[Language setting](/faq/youtube-language) · [Sorting](/faq/youtube-comment-sort) · [YouTube research](/guides/youtube-review-questions)

Free reference: `data:youtube.web_v2.get_video_comments`.