Service
한국 온라인 식료품 및 상품 데이터(가격, 할인, 품절 여부, 배송 유형)를 조회합니다.
99.94%30일 가동률평균 응답214ms
행을 선택하면 해당 API의 레퍼런스로 이동합니다.
| Method | API | Path | Summary |
|---|---|---|---|
| POST | /v1/market-kurly/count-products | Returns the current number of public Market Kurly search results for a keyword by calling the lightweight count endpoint, without a user session. Use when you need to know how many products match a keyword before deciding whether to fetch product rows. Do NOT use to retrieve product rows or prices — use market-kurly:search-products instead. Returns query, count (a stable integer), and source_url (the upstream count URL). | |
| POST | /v1/market-kurly/product-detail | Reads the public Market Kurly product detail page for a known product identifier and normalizes the matching product row, without login. Use when you already have a Market Kurly product_id and need best-effort detail-page data (price, discount, sold-out state, delivery types, product image). Do NOT use for keyword discovery — use market-kurly:search-products instead. Detail pages are read from public SSR page data, so prices may be absent and item may be missing when the row cannot be found. Returns item (the normalized product row when present) and source_url (the public detail URL, useful for diagnosing upstream schema changes). | |
| POST | /v1/market-kurly/search-products | Searches the public Market Kurly catalog by keyword and returns normalized product rows without a user login. Use when you need a read-only keyword search of Market Kurly products from public web/API endpoints. Do NOT use when only the number of matching products is needed — use market-kurly:count-products instead. Do NOT use when you already have a product_id — use market-kurly:product-detail instead. Results are paginated by page and capped by limit (max 50). Returns query, page, items (product_id, name, current_price, original_price, discount_rate, sold_out, delivery_types, image_url, product_url), and source_url (the upstream search URL, kept for audit). |
sandbox key를 발급받고 첫 예약 생성까지 진행합니다.
파트너 credential은 APIFuse이 보관합니다. 발급받는 것은 하나의 managed key입니다.
예약 확정, 배달 상태 변경 같은 이벤트를 webhook으로 수신합니다.
서비스 장애와 게이트웨이 에러를 하나의 에러 모델로 정규화합니다.
