Tabelog reviewer profile API

Use the Tabelog reviewer profile API to retrieve public reviewer profiles, contribution counts and restaurant references. Identify a reviewer by profile URL or reviewer ID to inspect their bio, contribution counts, public following relationships, visited venues and recommended restaurants with their published ratings. Inspect a reviewer’s contribution history and public connections, compare their recommended restaurants, or attribute reviews to a profile. Contribution counts and recommendations describe a public reviewer profile, rather than a new restaurant assessment generated by this request. The detail page provides request and response examples, supported parameters, and usage pricing.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
A tabelog.com/rvwr/<id>/ link (or the id).
Optional parameters (6)
Reviewer id.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "bio": "銀座を中心に年間250日は外食生活しています。時々地方へも。サービスも重視します!",
  "cached": false,
  "catchphrase": null,
  "collections": 0,
  "counters": {
    "いいね!": 1996,
    "写真": 1208,
    "口コミ数": 186,
    "訪問者数": 4584
  },
  "credits_used": 1,
  "followers": 36,
  "following": 25,
  "id": "015531341",
  "likes": 1996,
  "nickname": "ぶら〜り歩きの始まり始まり",
  "photos": 1208,
  "recommended": [
    {
      "area_genre": "銀座一丁目、有楽町、銀座 / 居酒屋",
      "comment": null,
      "dinner_rating": 5,
      "lunch_rating": null,
      "name": "SAPPORO大助",
      "prefecture": "東京",
      "rank": 1,
      "review_url": "https://tabelog.com/rvwr/015531341/rvwdtl/B516106654/"
    },
    {
      "area_genre": "茂原 / 台湾料理、ラーメン、居酒屋",
      "comment": null,
      "dinner_rating": 4.8,
      "lunch_rating": null,
      "name": "台湾食飲 喜喜",
      "prefecture": "千葉",
      "rank": 2,
      "review_url": "https://tabelog.com/rvwr/015531341/rvwdtl/B525927118/"
    },
    "… 8 more"
  ],
  "review_count": 187,
  "reviews": 186,
  "url": "https://tabelog.com/rvwr/015531341/",
  "visited_restaurants": 187,
  "visitors": 4584
}

Response result

Response structure

Inferred from examples
  • biostring
  • cachedboolean
  • catchphrasenull
  • collectionsinteger
  • countersobject
    • いいね!integer
    • 写真integer
    • 口コミ数integer
    • 訪問者数integer
  • credits_usedinteger
  • followersinteger
  • followinginteger
  • idstring
  • likesinteger
  • nicknamestring
  • photosinteger
  • recommended(object | string)[]
    • area_genrestring
    • commentnull
    • dinner_ratingnumber
    • lunch_ratingnull
    • namestring
    • prefecturestring
    • rankinteger
    • review_urlstring
  • review_countinteger
  • reviewsinteger
  • urlstring
  • visited_restaurantsinteger
  • visitorsinteger

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Tabelog reviewer profile API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.