# Yahoo Flea Market Japan Prices (Yahoo!フリマ) (`jpopendata/japan-flea-market-paypay`) Actor

Marketplace listings from Yahoo!フリマ (PayPay Flea Market) search: title, asking price JPY, condition, category, brand, like count, listing status — English schema for price research on Japan's #2 flea market. Item facts only, no seller data. Unofficial; not affiliated with LY Corporation.

- **URL**: https://apify.com/jpopendata/japan-flea-market-paypay.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 record scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Yahoo Flea Market Japan Prices (Yahoo!フリマ / PayPayフリマ)

**Live marketplace listings from Yahoo!フリマ (formerly PayPayフリマ), Japan's second-largest flea market app — item title, asking price in JPY, condition, category, brand, like count and listing status, in a clean English schema.**

This Actor searches the public listings on paypayfleamarket.yahoo.co.jp by keyword and returns each listing as English-schema JSON: item title, asking price (JPY), condition (new/used plus the site's condition grade code), sold status, category path and id, brand name and id, "like" count (demand signal), listing timestamp (ISO 8601), thumbnail image URL, image count, price-drop flag, and item URL. Optional price-range, condition, category and sold-status filters and price/recency sorting are applied client-side.

Yahoo!フリマ is the fixed-price flea market of LY Corporation's commerce ecosystem — the main receiving ground for Mercari-style secondhand supply in Japan: trading cards, figures, retro games, camera gear, fashion, sneakers and electronics. Its prices are Japanese-only and invisible to most international tooling; this Actor is the bridge for price research, sourcing and market analysis.

> **Unofficial tool.** Not affiliated with or endorsed by LY Corporation (LINEヤフー株式会社) or Yahoo!フリマ. It collects **publicly available data only** (no login, no paywall), politely (strictly serial requests, ≥1.2 s apart, hard per-run budget, no block evasion), fetches **only URLs the site's robots.txt allows**, and extracts **item facts only** — **no seller information of any kind** (no seller IDs, ratings or locations), no user-posted hashtags or descriptions, no personal data (relevant e.g. under GDPR: no personal data is collected or processed). Users are responsible for ensuring their own use of the data complies with the source site's terms and applicable law.

***

### Who is this for?

- **Resellers & arbitrage** — current asking prices for anything traded secondhand in Japan: trading cards, figures, retro games, camera gear, sneakers, watches, denim. Pair with sold comps (below) to spot underpriced listings.
- **Overseas buyers & proxy-buying services** — know the going rate in Japan before quoting; Buyee/Zenmarket-style flows need exactly this data.
- **Market research** — price distributions, condition mix, brand mix and demand signals (likes, price-down flags) per item family, tracked over time.
- **Data teams** — a stable English schema over a Japanese-only source, with an analysis-ready shape (numeric prices, ISO timestamps, coarse + detailed condition).

**Looking for prices things actually SOLD for?** Use the companion actor **[Yahoo Auctions Japan Sold Prices](https://apify.com/jpopendata/japan-yahoo-auction-sold)** — its closed-auction (落札相場) search covers sold items including Yahoo!フリマ cross-listed ones. This Actor gives you the live asking-price side; that one gives you the realized-price side.

### Sample output (dataset item)

```json
{
  "itemTitle": "PSA10 クサイハナ AR ポケモンカード 黒炎の支配者 109/108 GEM MT",
  "priceJpy": 6880,
  "condition": "new",
  "conditionDetail": "new",
  "isSold": false,
  "listingStatus": "OPEN",
  "categoryPath": ["ゲーム、おもちゃ", "トレーディングカード"],
  "categoryId": 2420,
  "brandName": "ポケモンカードゲーム",
  "brandId": 167473,
  "likeCount": 2,
  "listedAt": "2026-08-25T23:49:04+09:00",
  "imageUrl": "https://auc-pctr.c.yimg.jp/i/auctions.c.yimg.jp/images.auctions.yahoo.co.jp/image/...",
  "imageCount": 2,
  "isPriceDown": true,
  "itemUrl": "https://paypayfleamarket.yahoo.co.jp/item/z669037918",
  "source": "Yahoo!フリマ (paypayfleamarket.yahoo.co.jp search)",
  "sourceUrl": "https://paypayfleamarket.yahoo.co.jp/",
  "license": "Publicly available data — unofficial tool; users are responsible for compliance with the source site's terms",
  "retrievedAt": "2026-08-26T13:12:44.000Z"
}
```

`condition` is `new` / `used`; `conditionDetail` is the site's grade code (`new`, or `used10`…`used80` — lower number = better condition). `likeCount` and `isPriceDown` signal demand and seller flexibility; `isSold`/`listingStatus` separate on-sale from sold-out listings.

### Input example

```json
{
  "keyword": "ポケモンカード",
  "priceMin": 1000,
  "priceMax": 50000,
  "condition": "used",
  "sortBy": "priceAsc",
  "maxItems": 100
}
```

`keyword` is required (Japanese keywords match best). `category` takes a numeric Yahoo!フリマ category id (the id in `/category/` URLs, e.g. `2420` = トレーディングカード) and matches it client-side against each item's category path. Price range, condition, category, sold status and sorting are applied **client-side after fetching** — the equivalent URL parameters are disallowed by the site's robots.txt, and this Actor strictly requests only robots-allowed URLs (the only query parameter it ever sends is `page=`, which the site's own pagination links use). Tight filters therefore discard part of what was fetched; raise `maxApiRequests` if a filtered run comes back incomplete.

### Pricing

Pay per result — see the pricing tab. One upstream page holds ~100 listings.

### FAQ

**Where does the data come from?**
Live from the public, login-free search pages on paypayfleamarket.yahoo.co.jp at run time. Every record embeds the source, source URL, a license note, and the retrieval timestamp.

**Is this an official Yahoo! / LY Corporation service?**
No. **Unofficial**, independently built and maintained, and **not affiliated with or endorsed by LY Corporation.** It reads only publicly available pages.

**Is seller information included?**
No — deliberately and verifiably not. Seller IDs, ratings and item location are **never extracted** (the test suite asserts recursively that no seller-derived value can appear in any output field). Price research needs the item and the price, not the person. User-posted hashtags and descriptions are not extracted either.

**Does it respect robots.txt?**
Yes, strictly. The keyword search page this Actor uses (`/search/<keyword>`) is open in the site's robots.txt; a set of filter URL-parameters (`sort=`, `order=`, `conditions=`, `sold=`, `open=`, `minPrice=`, `maxPrice=`, …) is disallowed there, so this Actor never sends them and applies those filters client-side instead.

**Can I get sold prices (相場) with this?**
Mostly no — the robots-allowed default feed lists almost exclusively on-sale items, and the sold-filter URL parameter is disallowed, so `soldOnly` can only filter what the feed returns. For realized sold prices use the companion **[Yahoo Auctions Japan Sold Prices](https://apify.com/jpopendata/japan-yahoo-auction-sold)** actor, whose closed search includes Yahoo!フリマ cross-listed items.

**Who is responsible for how the data is used?**
You are. The Actor collects publicly available factual data politely, but the legality of your specific use (redistribution, database rights, the source site's terms) is your responsibility as the user.

**How fresh and complete are the results?**
Listings are what the site's search returns at retrieval time, in relevance order (~100 per page). Treat each run as a snapshot; re-run for fresh prices.

**What about server load?**
Strictly serial requests, ≥1.2 s apart, ~100 items per request, hard per-run request budget (max 60), exponential backoff, no CAPTCHA/login/block evasion. If the site changes its page format, the Actor stops with a clear error instead of silently mis-parsing; if it blocks persistently, the run fails visibly.

### Search terms this Actor answers

paypay flea market scraper · yahoo fleamarket japan · yahoo flea market prices · japan secondhand prices · paypay fleamarket data · japan marketplace scraper · ヤフーフリマ データ · PayPayフリマ 価格 · japan used goods prices · mercari alternative japan data · japanese flea market api · pokemon card prices japan · japan collectibles asking prices · japan resale sourcing

### More Japan data Actors by the same developer

- **Yahoo Auctions Japan Sold Prices (ヤフオク落札相場)** — realized sold prices from the closed-auction search; the perfect companion to compare these asking prices against actual sold comps.
- **Japan Hobby & Collectibles Prices (駿河屋 Suruga-ya)** — new/used/marketplace asking prices from suruga-ya.jp.
- **Japan Government Tenders & Awards** — tender notices and award results from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **Japan Care Facilities** — long-term care providers across 35 service types (MHLW open data, CC BY).
- **Japan Government Subsidies & Grants** — open subsidy calls from the official jGrants API.
- **Japan Renewable Energy FIT/FIP Facilities** — METI-certified renewable installations, privacy-safe schema.
- **Japan Financial Licenses & Registrations** — FSA-licensed banks, securities firms, crypto exchanges and more.
- **Japan Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's official register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.
- **Japan Hotels & Ryokan Prices (jalan.net)** — hotel/ryokan prices, plans and ratings by prefecture and area.

***

*Unofficial tool; not affiliated with LY Corporation. Publicly available data only; users are responsible for compliance with the source site's terms and applicable law. No personal data and no seller data are collected.*

# Actor input Schema

## `keyword` (type: `string`):

REQUIRED. Search keyword for marketplace listings, e.g. "ポケモンカード", "Nikon F3", "ガンプラ". Japanese keywords match best.

## `category` (type: `string`):

Optional numeric Yahoo!フリマ category id to narrow the results (the id in paypayfleamarket.yahoo.co.jp/category/ URLs), e.g. 2420 = トレーディングカード. Matched client-side against each item's category path (leaf or ancestor). Leave empty for all categories.

## `priceMin` (type: `integer`):

Optional lower bound on the asking price in JPY. Applied client-side after fetching (the equivalent URL parameter is disallowed by the site's robots.txt), so tight ranges may need a higher request budget.

## `priceMax` (type: `integer`):

Optional upper bound on the asking price in JPY. Applied client-side after fetching.

## `condition` (type: `string`):

Filter by item condition. Applied client-side after fetching.

## `soldOnly` (type: `boolean`):

Keep only sold-out listings. NOTE: applied client-side (the sold= URL parameter is disallowed by the site's robots.txt), and the robots-allowed default feed lists almost exclusively on-sale items — for sold-price comps use the companion actor "Yahoo Auctions Japan Sold Prices" instead (its closed search includes Yahoo!フリマ cross-listed items).

## `sortBy` (type: `string`):

ranking = the source's native relevance order. priceAsc/priceDesc = by asking price. newest = most recently listed first. Sorting is applied client-side to the collected records.

## `maxItems` (type: `integer`):

Stop after this many dataset records.

## `maxApiRequests` (type: `integer`):

Hard budget of HTTP requests to paypayfleamarket.yahoo.co.jp for this run (one request = one ~100-item result page). Requests are strictly serial with >= 1.2 s spacing. When the budget runs out the run completes with complete=false in RUN\_SUMMARY.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. Default: no proxy. Never used for rotation/evasion — one client identity per run.

## Actor input object example

```json
{
  "keyword": "ポケモンカード",
  "category": "2420",
  "priceMin": 1000,
  "priceMax": 50000,
  "condition": "any",
  "soldOnly": false,
  "sortBy": "ranking",
  "maxItems": 10,
  "maxApiRequests": 10
}
```

# Actor output Schema

## `records` (type: `string`):

Structured marketplace listing records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keyword": "フィギュア",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-flea-market-paypay").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keyword": "フィギュア",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-flea-market-paypay").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keyword": "フィギュア",
  "maxItems": 10
}' |
apify call jpopendata/japan-flea-market-paypay --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-flea-market-paypay"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/PjIakABggJWv2TsOQ/builds/2yPo5NXH257MQ9fqb/openapi.json