Yahoo! JAPAN search results, as a visitor in Japan sees them
Yahoo! JAPAN (search.yahoo.co.jp) is the search engine most people in Japan use besides Google, and its results page is its own: Google's web index rendered by Yahoo, with Yahoo's ads, news, Q&A, realtime posts and knowledge panels mixed in.
This page covers what the Yahoo! JAPAN Search API returns, who uses it, a real response and pricing. Every parameter and response field is in Yahoo! JAPAN Search API parameters and responses →
- endpoints
- 7
- credits per call
- 1–2
2 credits per call≈ $2/1,000 calls1,000 free credits, no card
- has_next
- true
- last_page_reached
- false
7 active endpoints, on 1 and 2 credit tiers.
- POST/yahoo-japan-search/v1/search2 credits
- POST/yahoo-japan-search/v1/images1 credit
- POST/yahoo-japan-search/v1/videos1 credit
- POST/yahoo-japan-search/v1/news1 credit
- POST/yahoo-japan-search/v1/realtime1 credit
- POST/yahoo-japan-search/v1/chiebukuro1 credit
- POST/yahoo-japan-search/v1/suggest1 credit
Run the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
Yahoo! JAPAN Search API
3 of 7 endpoints, ready to run
The web results page with ads, related questions and inline blocks
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What Yahoo! JAPAN Search endpoints does ReefAPI ship?
7 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Every parameter, every allowed value →
Missing a Yahoo! JAPAN Search endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the Yahoo! JAPAN Search API works
Yahoo! JAPAN Search is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 632 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a keyword to its Japanese SERP, its news and what people post about it
One keyword, three calls, all in Japan time.
エージェント
Organic results with sitelinks and dates, up to 8 paid ads with advertiser and sitelinks, related searches, related questions with Yahoo's AI answers and sources.
エージェント
Yahoo! News articles with publisher, categories and publish time, 50 a page.
エージェント
Up to 40 recent posts on X with counts and media; pass next_cursor back for older posts.
A dated picture of a keyword in Japan: who ranks, who advertises, what the news says and what people post.
curl -X POST https://api.reefapi.com/yahoo-japan-search/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"富士山"}'{
"ok": true,
"data": { … },
"meta": {
"api": "yahoo-japan-search",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a Yahoo! JAPAN Search field actually contains
Fields that read differently from how they look. Every row was measured against live Yahoo! JAPAN answers on 2026-11-06.
| Field | What it holds |
|---|---|
| ads (search) | The paid ads Yahoo! JAPAN shows a visitor in Japan, each with block (top, middle or bottom), title, snippet, displayed URL, domain, advertiser, the click link and sitelinks. link and the sitelink links are Yahoo's ad click links (rd.listing.yahoo.co.jp): opening one counts as a paid click for the advertiser, so use displayed_url or domain for the advertiser's site. Yahoo serves ads only to Japanese visitors: the same queries read from the United States returned no ads at all. 9 of the 44 queries checked carried ads, up to 8 per page (ホテル 予約, 転職 エージェント, 英会話 オンライン). |
| search_information (search) | exit_country is the country the page was read from (JP normally) and ads_included says whether ads could be present. If every Japanese exit fails, the page is read from the United States: organic results are complete, ads is empty, and a warning says so. local_area names the area Yahoo placed the visitor in when the page shows a local block (area, latitude, longitude), otherwise null. |
| Localised results (search) | Yahoo! JAPAN localises results to the city it places the visitor in, which follows the Japanese network exit of the call; there is no location parameter. Local queries change most: ホテル 予約 read three times in a row on 2026-11-06 was placed in 東京都荒川区, 東京都板橋区 and 名古屋市千種区. Every search answer carries a warning saying so, and local_area names the area when the page shows it. |
| total_results (search) | The 約…件 hit count exactly as the page prints it. It is not stable: the same page printed 1,270,000, 1,230,000 and 102 on three reads. Do not use it to size a crawl; page until pagination.has_next is false. |
| pagination (search) | Yahoo! JAPAN goes about 20 to 40 pages deep, not as far as total_results suggests. last_page_reached is true on the site's own last page; a page past it returns no results with stop_reason past_last_page. |
| related_questions (search) | Questions Yahoo shows beside the results. When Yahoo has written an AI answer for one, answer holds it and sources lists the pages it cites, each once. |
| published_at (news) | Japan time. Yahoo! News prints month, day and time without a year (11/6(金) 20:01, kept in published_text); the year is the current one in Japan, or the previous one for a date that would otherwise be in the future. |
| next_cursor (realtime) | Pass it back unchanged for the next 10 older posts. It carries Yahoo's own rewritten query and the oldest post id, so every page continues where the last one stopped: 10 follow-up pages checked, 100 of 100 posts older than the first page and none repeated. Popular order is a single page of up to 40 posts. |
| status (chiebukuro) | open (回答受付中), resolved (解決済み) or empty for questions in voting. status=open returned only open questions on every page checked. |
| spelling (images, videos) | Set when Yahoo searched for a corrected query instead of yours (did you mean); results are for searched_query. |
Snippets, titles and post text come back as plain text: Yahoo's highlight tags and markers are removed (0 left in 362 live answers). Every organic URL returned was also a link on the page Yahoo served (506 of 506).
Yahoo! JAPAN coverage, measured
Every number below was read from live Yahoo! JAPAN answers on 2026-11-06: 362 calls over 44 queries (30 Japanese, 14 English) and all seven actions.
362 of 362 calls answered: search 60, images 48, videos 49, news 48, realtime 65, chiebukuro 48, suggest 44.
506 organic results on 60 pages, every URL also a link on the page Yahoo served. Ads on 9 of 44 queries, up to 8 per page; 26 pages with a knowledge panel, 21 with related questions, 17 with 知恵袋 answers, 14 with news.
images size=icon: 20 of 20 images 256 px wide, size=large: none under 800 px; videos duration=short 36 to 206 s, long 1,218 to 12,284 s, site=niconico all nicovideo.jp; realtime media=image 40 of 40 posts with media; chiebukuro status=open only open questions; news category=sports only sports categories.
realtime next_cursor: 10 of 10 follow-up pages older than the first page, no post repeated. Search page 5 answered on every query checked.
Median per call: suggest 1.1 s, news 1.3 s, videos 1.5 s, images 1.7 s, chiebukuro 1.7 s, realtime 1.8 s, search 2.5 s.
Web results are localised to the Japanese city Yahoo places the visitor in, which follows the exit of the call and can change between calls (search_information.local_area names it when the page shows a local block); web results go about 20 to 40 pages deep and the hit count is not stable between reads; realtime popular order is a single page; Yahoo! News dates are printed without a year (inferred in Japan time); map, shopping and auction search are not covered here (see Yahoo! Shopping Japan and Yahoo! Auctions).
What people build with Yahoo! JAPAN Search
The jobs this data is most often used for.
endpoints
credits per call
Track rankings on Yahoo! JAPAN for Japanese and English keywords, page by page, with the ads competing for the same query.
Monitor which advertisers buy a keyword in Japan and what their ad copy and sitelinks say.
Follow a brand or topic on Yahoo! News and on X through Yahoo realtime search, with publish times in Japan time.
Collect real questions people ask on 知恵袋 about a product or topic, with answer and view counts.
What Yahoo! JAPAN Search data costs
The cheapest call here is 1 credit, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 632 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/yahoo-japan-search/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"富士山"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/yahoo-japan-search/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "富士山"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Yahoo! JAPAN Search.
Do I need a Yahoo! JAPAN ID, an appid or a Japanese IP?▾
No. Everything is read logged out from the public site, and you call reefapi.com from anywhere. The web results page is read through Japan so that you get the page, and the ads, a visitor in Japan gets.
Is this the same as Google Japan?▾
The organic results come from Google's index, but the page is Yahoo's own: Yahoo's ads, Yahoo! News, 知恵袋, realtime posts on X, Yahoo knowledge panels and stock and currency boxes. Of the 60 result pages read on 2026-11-06, 26 carried a knowledge panel, 21 related questions, 17 a 知恵袋 block and 14 a news block.
Can I search in English?▾
Yes. English and Japanese both work, and language=en keeps only English pages: sushi returned kura sushi and other Japanese chains in Japanese and Wikipedia, Tripadvisor and Yelp in English. News, realtime and 知恵袋 are Japanese services, so English-only queries can return few or no results there (yen exchange rate had no Yahoo! News match; yen alone had 186).
Which filters are there?▾
search: period (past hour to past year) and language. images: size, colour, type, period. videos: duration, period, site (YouTube, Dailymotion, niconico) and HD. news: category. realtime: newest or popular, image or video posts only. chiebukuro: open or resolved, and the site's eleven sort orders. Each was checked live: images size=icon returned 20 of 20 images 256 px wide and size=large none under 800 px; videos duration=short returned 36 to 206 seconds and duration=long 1,218 to 12,284 seconds; realtime media=image returned 40 of 40 posts with media.
How do I get more realtime posts?▾
The first call returns up to 40 posts. Pass next_cursor back for the next 10 older posts, as many times as you like. Popular order (sort=popular) is one page.
What happens when there is no result?▾
You get ok with an empty list and stop_reason no_match, after the empty answer was confirmed from a second exit. Yahoo sometimes serves a complete results page with no results by mistake; that is retried from other exits and never reported as no match.
How fast is it?▾
Median 1.1 to 2.5 seconds per call depending on the action, measured over 362 live calls: suggest 1.1 s, news 1.3 s, videos 1.5 s, images 1.7 s, chiebukuro 1.7 s, realtime 1.8 s, search 2.5 s.
What is the Yahoo! JAPAN Search API?▾
Yahoo! JAPAN Search API is a ReefAPI endpoint group for yahoo! japan search results as json: web results with the ads people in japan see, images, videos, yahoo! news, posts on x from realtime search, 知恵袋 q&a and search suggestions. It returns live JSON through POST requests under /yahoo-japan-search/v1.
Is the Yahoo! JAPAN Search API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Yahoo! JAPAN Search calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Yahoo! JAPAN Search login or account?▾
No login to Yahoo! JAPAN Search is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Yahoo! JAPAN Search data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Yahoo! JAPAN Search API use?▾
Yahoo! JAPAN Search actions currently cost 1-2 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Yahoo! JAPAN Search from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call yahoo-japan-search actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Yahoo! JAPAN Search API a Yahoo! JAPAN Search scraper?▾
It is the managed alternative to a DIY Yahoo! JAPAN Search scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same yahoo! japan search results as json: web results with the ads people in japan see, images, videos, yahoo! news, posts on x from realtime search, 知恵袋 q&a and search suggestions back as clean JSON.
11 Search & SEO APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Yahoo! JAPAN Search, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 631 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-06.