Naver Comments API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Fetch the comments on a Naver Blog or Cafe post from its url, with each commenter's name, text, time and an is_reply flag for replies. Nothing is posted, and the full reply hierarchy is not guaranteed.
Send POST https://api.everyinfra.com/api/v1/social with platform set to naver and action set to comments. Price $20.79 per 1,000 requests ($0.02079 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
#Please help me write a data collection script with the EveryInfra Naver Comments endpoint (naver/comments).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to naver and action to comments, and put the parameters inside params.
- Required parameters:
- url: Specifies the target URL for Naver requests. The post and comments actions accept specific Blog or Cafe post URLs, whereas the reviews action requires Naver Place merchant links containing /restaurant/MERCHANT_ID or /pla…
- Optional parameters:
- limit: The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- Returns a list of records. Main fields of each record: author_name, text, posted_at, is_reply, post_url.
- Example request body:
{
"platform": "naver",
"action": "comments",
"params": {
"url": "https://blog.naver.com/hyemi35/224360992457"
}
}
- Price: $20.79 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | naver | Platform identifier, fixed value. |
action | body | string | Yes | comments | Capability identifier, fixed value. |
url | body.params | string | Yes | - | Specifies the target URL for Naver requests. The post and comments actions accept specific Blog or Cafe post URLs, whereas the reviews action requires Naver Place merchant links containing /restaurant/MERCHANT_ID or /place/MERCHANT_ID paths. |
limit | body.params | integer (1–) | No | - | The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "naver",
"action": "comments",
"params": {
"url": "https://blog.naver.com/hyemi35/224360992457"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "naver", "action": "comments", "results": [ { "author_name": …, "text": …, "posted_at": …, "is_reply": …, "platform": …, "post_url": … } ], "count": …, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
author_name | Author's display name. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
is_reply | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
post_url | Keeps the platform's own meaning |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.