/paypayfleamarket/users

POST /api/paypayfleamarket/users

Price: 1 credit

Get a Yahoo!フリマ (formerly PayPay フリマ) member profile by user id or profile URL: masked nickname, profile picture, total feedback count and the share of positive feedback, identity-verification and trusted-seller flags, the shipping-speed badge, the trading-record tier the source displays, and the follower and followee counts.

How to use it

Look up a Yahoo!フリマ / PayPay フリマ seller or buyer by id (e.g. 'p58634') or profile URL, for reputation checks. Returns nickname (the source publishes it masked, e.g. 'ttr********'), image, rating_count, good_ratio (percentage of positive feedback), is_kyc_completed, is_trusted, is_gold, ship_badge_level (none/relief/fast/fast_relief), trading_record_label and trading_record_level, follower_count and followee_count. Use paypayfleamarket/users/items for what they sell and paypayfleamarket/users/reviews for the feedback texts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Yahoo!フリマ user id or a full profile URL (examples: "p58634", "https://paypayfleamarket.yahoo.co.jp/user/p58634"; minLength: 1)

Response

• @type string (default: "PaypayfleamarketUser")
• id string required
• url string required
• nickname string nullable
• image string nullable
• rating_count integer nullable
• good_ratio number nullable
• is_deleted boolean nullable
• is_kyc_completed boolean nullable
• is_trusted boolean nullable
• is_gold boolean nullable
• ship_badge_level string nullable
• trading_record_label string nullable
• trading_record_level integer nullable
• external_trading_record_level integer nullable
• follower_count integer nullable
• followee_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — User not found (well-formed id but no such member on Yahoo!フリマ) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.