Dianping Merchant & Review Data API · Live

Pull live Dianping data
in the time it takes
to read this sentence.

Taste/environment/service sub-scores, Must-Eat List (必吃榜) rankings, average cost per person, and photo-rich reviews — structured and delivered as clean JSON or CSV. No proxies to manage, no CAPTCHAs to solve, no HTML to parse.

See a Live Response
100K+ Merchants Tracked
8M+ Reviews
4 Categories Covered
Real-Time Data Refresh
GET /v1/dianping/merchant
LIVE
// request timestamp 2026-07-22 04:31:10 UTC { "merchant_id": "DP-951223", "name": "陈麻婆豆腐, 锦江区成都", "category": "Sichuan, Traditional", "overall_rating": 4.6, "sub_scores": { "taste": 9.4, "environment": 7.8, "service": 8.2 }, "must_eat_list_rank": 1, "avg_cost_per_person": 68, "currency": "CNY", "review_count": 14200, "status": "open", "fetched_in_ms": 1738 }
TRUSTED BY CLIENTS ACROSS MULTIPLE INDUSTRIES
Food Tech China Retail Restaurant Analytics Market Research Logistics Technology
500+
GLOBAL CLIENTS SERVED
300+
PROJECTS DELIVERED
50M+
MONTHLY API CALLS
24/7
DEDICATED SUPPORT
Why Choose Our Dianping API

A single star rating hides three different scores — and a Must-Eat List badge changes everything.

Dianping's real signal lives in its taste, environment, and service sub-scores, its Must-Eat List (必吃榜) rankings, and its photo-heavy user reviews — a review-and-discovery model quite different from a simple aggregate star rating. Our infrastructure resolves all of it as structured fields.

01

Zero blocking, zero maintenance

We run rotating residential IPs, headless rendering, and CAPTCHA-solving behind every request. When Dianping changes its layout, we patch our parsers — your integration never breaks.

02

Sub-score breakdown resolved

Every merchant response separates taste (口味), environment (环境), and service (服务) scores instead of one blended rating.

03

Must-Eat List ranking detection

We flag whether a merchant holds a Must-Eat List (必吃榜) badge and its rank within category and city, a major discovery signal.

04

Built for scale from day one

From a 100-merchant test batch to citywide catalog monitoring, the same endpoint and response shape scale with you.

Dianping API Features

Everything you need to keep Dianping data flowing.

Real-time Extraction

Trigger an on-demand pull for any merchant ID or keyword and get a fresh response — not a stale cache.

🧩

Custom Field Selection

Request only the fields you need — sub-scores, rankings, reviews — to cut payload size and parsing time.

🏅

Must-Eat List Rank Extraction

Pull a merchant's 必吃榜 rank within its city and category where it holds one.

📸

Photo-rich Review Extraction

Pull user review text, sub-scores, and attached photos in a single structured call.

📦

Bulk & Scheduled Requests

Submit thousands of merchant IDs in one batch job or schedule recurring pulls on a custom cadence.

📊

Historical Rating Tracking

Store and query sub-score and ranking history per merchant to power trend-analysis tools.

What Data Can You Access?

Every field a merchant page shows — sub-scores and rankings included.

CoreMerchant name & IDOutlet name, category, address
ScoresOverall star ratingAggregate rating out of 5
ScoresTaste sub-score (口味)Food quality rating out of 10
ScoresEnvironment sub-score (环境)Ambience rating out of 10
ScoresService sub-score (服务)Service rating out of 10
RankingMust-Eat List rank (必吃榜)Category & city rank where awarded
PricingAverage cost per person (人均)Typical spend per diner
VouchersGroup-buy voucher price团购价 vs list price where offered
MediaUser review photosPhotos attached to individual reviews
ReviewsIndividual reviewsText, sub-scores, date, check-in flag
TagsSignature dish tagsMost-mentioned dishes across reviews
OperationsOperating hoursOpen/closed status, hours per day
Supported Dianping Categories

Dining, entertainment, beauty, and hotels — one integration.

Switch the category parameter to pull from a different part of Dianping's local-services catalog with the same consistent response shape.

🍜

Dining (美食)

Restaurant sub-scores, rankings, and voucher deals.

🎬

Entertainment (休闲娱乐)

KTV, cinemas, and leisure venue listings.

💆

Beauty & Spa (丽人)

Salon, spa, and wellness service listings.

🏨

Hotels (酒店)

Hotel listings with the same sub-score model.

China-wide

Coverage across major and secondary Chinese cities

Rank-aware

Must-Eat List rank resolved by city and category

Real-time

Scores and pricing data checked on every request

Dianping API Endpoints

A small set of endpoints that cover the whole merchant lifecycle.

Method Endpoint Description Typical use
GET /v1/dianping/merchant Full merchant profile by ID or URL Sub-score & ranking monitoring
GET /v1/dianping/search Keyword or category search results Market & competitor discovery
GET /v1/dianping/reviews Paginated reviews with sub-scores & photos Sentiment & photo mining
GET /v1/dianping/group-buy-deals Active group-buy voucher deals & pricing Promo & voucher intelligence
GET /v1/dianping/must-eat-rankings Must-Eat List (必吃榜) rankings by city & category Discovery & ranking analysis
GET /v1/dianping/category Category tree & node metadata Taxonomy mapping
POST /v1/dianping/bulk Submit up to 10,000 merchant IDs per batch job Citywide catalog monitoring
Live API Response Example

This is exactly what comes back. No extra parsing needed.


        
Popular Dianping API Use Cases

Built for the teams that live and die by Dianping data.

📈

Sub-score & Ranking Monitoring

Track taste, environment, and service sub-score movement over time for key merchants.

🔍

Local Market Research

Analyze merchant density, cuisine trends, and Must-Eat List patterns across cities.

🛡️

Multi-location Consistency Checks

Verify sub-scores and voucher pricing consistency across chain locations.

💬

Photo-review Sentiment Mining

Pull review text and photos together to power visual sentiment analysis models.

🏅

Must-Eat List Tracking

Monitor which merchants enter or drop off the 必吃榜 ranking by city and category.

📦

Aggregator Comparison Tools

Build side-by-side comparisons of ratings and pricing across Chinese local-services platforms.

🏆

Competitive Benchmarking

Track how a merchant's sub-scores compare against nearby competitors in the same category.

🧭

ML Training Data

Generate labeled merchant, sub-score, and photo-review datasets for recommendation models.

How the Dianping API Works

From API key to structured data in five steps.

1

Get your API key

Sign up and generate a key from your dashboard in under two minutes.

2

Choose an endpoint

Pick /merchant, /reviews, /search or /must-eat-rankings depending on what you need.

3

Send the request

Call the endpoint with a merchant ID, keyword, or URL and your city and category.

4

We handle the hard part

Proxies, headless rendering, CAPTCHA-solving, and parsing all happen behind the scenes.

5

Receive structured data

Get clean JSON or CSV back in seconds, ready to drop into your pipeline.

Developer-Friendly Integration

Built by people who read the docs too.

One consistent JSON schema across every endpoint and every category. No SDK lock-in — plain REST calls work from any language or platform.

Predictable REST design

Standard HTTP verbs, query params, and status codes — nothing proprietary to learn.

JSON, CSV, or webhook delivery

Get results inline, as a downloadable file, or pushed to your endpoint when a batch job finishes.

Sandbox & test keys

Free sandbox environment with sample merchant IDs so you can build before you pay.

Postman collection & SDK snippets

Import a ready-made collection or copy request snippets for Python, Node.js, and cURL.

Quickstart
API Performance & Reliability

Numbers we publish because we track them daily.

99.9%
Uptime SLA
<3s
Avg. response time
99.3%
Successful extraction rate
10K+
Concurrent requests supported
Security & Compliance

Compliant by design, not as an afterthought.

🔒

Encrypted in transit

All requests and responses travel over TLS 1.2+. API keys can be scoped and rotated anytime.

⚖️

PIPL & global alignment

Our extraction workflows are built around China's Personal Information Protection Law alongside GDPR guidelines.

🌐

Public-data-only policy

We collect only publicly accessible listing data — never login-gated or private account information.

ISO 9001:2015 Certified ISO/IEC 27001:2013 Certified IAF Multilateral Recognition GDPR-aligned workflows
API Documentation & Resources

Everything to go from key to production.

Guide

Quickstart Guide

Get your first API response back in under five minutes.

Read guide →
Reference

Full API Reference

Every endpoint, parameter, and response field documented in detail.

View reference →
Tool

Postman Collection

Import ready-made requests for every Dianping API endpoint.

Download →
Code

SDKs & Code Samples

Python, Node.js, PHP, and Ruby snippets for every use case.

Browse samples →
Frequently Asked Questions

Still deciding? Here's what most teams ask first.

We collect only publicly accessible merchant and review data using automated tools, following publicly available web-data guidelines. We recommend reviewing your own use case with legal counsel, especially for redistribution.

Every request to /merchant, /reviews, and /must-eat-rankings triggers a live pull — you're not reading from a stale cache. Bulk jobs complete within minutes depending on batch size.

Yes. The /merchant endpoint returns 口味 (taste), 环境 (environment), and 服务 (service) as three distinct sub-scores alongside the overall rating.

Yes — where a merchant holds a Must-Eat List badge, the /merchant and /must-eat-rankings endpoints return its rank within category and city.

Our infrastructure retries automatically across a rotating proxy pool. You're only billed for successfully returned responses.

Yes, every account starts with a free sandbox key and sample credits so you can test all endpoints before committing to a plan.

Brand Image
INQUIRE NOW