/dhgate/stores

POST /api/dhgate/stores

Price: 10 credits

Get a single DHgate store (seller) by id or store URL. Returns the store name, location, opening date, description, positive feedback percentage, transaction count, positive review count, overall review score, DHgate service scores (on-time delivery, repurchase rate), the positive/neutral/negative feedback breakdown over the last 2, 6 and 12 months and in total, and the service-detail scores (items as described, communication, delivery time, shipping charges).

How to use it

Fetch one DHgate store by its numeric id (or store URL). Returns id, seller_id, name, url, country, opened_at, description, positive_feedback_percent, transaction_count, positive_review_count, review_score, service_scores (name/value), the feedback_last_2_months/6/12 and feedback_total windows (positive/neutral/negative counts) and service_detail_scores.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• currency string — Currency the prices are returned in (default: "USD"; one of: "USD", "EUR", "GBP", "CAD", "AUD", "JPY", "RUB", "BRL", "INR", "MXN", "KRW", "TRY", "SEK", "NOK", "DKK", "PLN", "CHF", "NZD", "SGD", "HKD", "THB", "ILS", "AED", "SAR", "ZAR", "CZK")
• ship_to_country string — Ship-to country — drives shipping cost and delivery estimates (default: "US"; one of: "US", "GB", "CA", "AU", "DE", "FR", "IT", "ES", "NL", "BE", "SE", "NO", "DK", "FI", "IE", "PT", "PL", "CH", "AT", "CZ", "GR", "RU", "BR", "MX", "CL", "AR", "JP", "KR", "CN", "HK", "TW", "SG", "MY", "TH", "ID", "PH", "VN", "IN", "AE", "SA", "IL", "TR", "ZA", "NZ")
• store string required — Store id or store URL (examples: "22224092", "https://www.dhgate.com/store/22224092"; minLength: 1)

Response

• @type string (default: "DhgateStore")
• id string required
• seller_id string nullable
• name string nullable
• url string nullable
• country string nullable
• opened_at string nullable
• description string nullable
• positive_feedback_percent number nullable
• transaction_count integer nullable
• positive_review_count integer nullable
• review_score integer nullable
• service_scores array (default: [])
  • @type string (default: "DhgateStoreScore")
  • name string required
  • value string nullable
• feedback_last_2_months object nullable
  • @type string (default: "DhgateStoreFeedbackWindow")
  • positive integer nullable
  • neutral integer nullable
  • negative integer nullable
• feedback_last_6_months object nullable
  • @type string (default: "DhgateStoreFeedbackWindow")
  • positive integer nullable
  • neutral integer nullable
  • negative integer nullable
• feedback_last_12_months object nullable
  • @type string (default: "DhgateStoreFeedbackWindow")
  • positive integer nullable
  • neutral integer nullable
  • negative integer nullable
• feedback_total object nullable
  • @type string (default: "DhgateStoreFeedbackWindow")
  • positive integer nullable
  • neutral integer nullable
  • negative integer nullable
• service_detail_scores array (default: [])
  • @type string (default: "DhgateStoreServiceDetail")
  • name string required
  • score number nullable
  • max_score number nullable
  • compared_to_industry string nullable
  • rating_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 — Store not found on DHgate 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.