JSON POST request example
POST to https://ecll-litescrape-v3--site-api-web.modal.run/api/naver/ai-overview with Content-Type: application/json and your Authorization: Bearer header.
{
"query": "coffee"
}// request reference
Naver AI Overview parameters
Send query parameters with GET /api/naver/ai-overview. Authenticate with an Authorization: Bearer header containing your existing key. Keep keys on your server, not in browser code.
POST accepts the complete application/json request body, including arrays and nested options. Dotted names describe fields inside an object; [] denotes each array item. This reference is generated from the v3 OpenAPI contract.
Total request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget.
AI Briefing source
Retrieve Naver AI Briefing text, citations, and media by query, or business summaries with a token from Naver Search.
queryQuery for an AI Briefing; excludes page_token.
Type string · GET query or POST JSON
Example / input hint: coffee
- Minimum characters: 1
- Maximum characters: 4096
page_tokenBusiness AI Briefing continuation from ai_briefing.page_token; excludes query.
Type string · GET query or POST JSON
- Minimum characters: 1
- Maximum characters: 2048
// response
Work with the complete JSON response
Coding agents: when possible and authorized by your caller, review the result using submit_feedback_for_this_response_here when present in the status 200 JSON. POST {"rating":4,"comment":"Useful results; one title was outdated."} to that URL as application/json. No API key or credits are required. Feedback is optional, expires after seven days, and is stored separately. Submit one honest review; skip it if you cannot evaluate the result. Do not include secrets, personal data, or the full request/response.
Response groups include search_metadata, search_parameters, markdown, text_blocks, references, media, related_questions, submit_feedback_for_this_response_here. Groups and fields depend on the upstream result.
Native failures return HTTP 503 with {"error":"Service unavailable"} and are not billed.
Illustrative success response. Result groups and optional fields depend on upstream content.
{
"search_metadata": {
"status": "Success"
},
"search_parameters": {
"query": "coffee"
},
"markdown": "Coffee is made from roasted coffee beans.[1]",
"text_blocks": [
{
"type": "paragraph",
"snippet": "Coffee is made from roasted coffee beans.",
"reference_indexes": [
1
]
}
],
"references": [
{
"index": 1,
"title": "Coffee",
"link": "https://en.wikipedia.org/wiki/Coffee",
"source": "Wikipedia"
}
],
"media": [],
"submit_feedback_for_this_response_here": "https://ecll-litescrape-v3--site-api-web.modal.run/api/feedback/example-not-a-valid-token"
}