CommerceBrowser

Coupang

coupang.com

Unofficial Coupang provider for mobile shopping flows.

Tier: 🥇 Gold
Reward: ₩300,000
Auth: Browser
Operations: 4
Working now: 0 contributors
Status: Open

Scope

Targets the Coupang mobile/web surface, not a public API. A hunter needs a logged-in browser session or app-authenticated requests, plus pagination and anti-bot handling for search, product detail, order history, and shipment tracking.

Expected operations

search-productsSearch productsreadDifficulty: hard

GET the Coupang search results surface for keyword and filter-driven product discovery. Returns catalog hits with pricing, review, shipping, and Rocket Delivery signals from the mobile storefront.

Inputs

querystringrequired

Suggested surface — propose changes in your submission if the upstream differs.

Acceptance criteria

Provider scaffolded from the public @apifuse/provider-sdk
All listed operations implemented with Zod/Standard Schema input & output
Each operation declares exactly one of healthCheck or healthCheckUnsupported
Real upstream fixture data included where applicable
bun run check and bun run test pass
Auth, credential, and env-secret behavior documented (no real secrets committed)

Evidence to submit

Workspace repository and main commit link
SDK version/tag and the create command used
Operation list with input/output summaries
Health coverage table per operation
bun run check and bun run test output

Ready to claim?

Submit a claim. Your workspace will be prepared after confirmation.

Claiming a bounty requires a GitHub sign-in.

sorterstringoptional

Sort key such as popularity or price

scoreDesc

pagenumberoptional

Result page number

sizenumberoptional

Page size

rocket_deliverybooleanoptional

Filter to Rocket Delivery eligible items

true

Outputs

product_idproduct_namepriceoriginal_pricediscount_raterating_averagereview_countrocket_deliveryseller_namethumbnail_url

Acceptance

Changing the query and sort parameters must actually change the search results and their ordering.
Each product card must populate real fields such as product_id, price, rating_average, review_count, and rocket_delivery.
Pagination must return the next results without duplicates, and a missing q must be rejected as a validation error.

No account auth required for this operation.

get-product-detailGet product detailreadDifficulty: hard

Fetches a specific product page by product identifier from the mobile storefront. Returns the detailed merchandising payload including option, pricing, and seller data needed to decide purchase readiness.

Inputs

product_idstringrequired
Coupang product identifier
1234567890
vendor_item_idstringoptional
Variant or offer identifier when multiple sellers exist
3456789012

Outputs

product_idproduct_namebrandpricesale_priceoptions

list-ordersList ordersreadDifficulty: hard

Reads the authenticated order history view for recent purchases. The surface is session-bound and typically protected by login plus bot checks; it returns order summaries, item lines, and fulfillment state.

Inputs

statusstringoptional
Optional order state filter
DELIVERING
pagenumberoptional
Page number
1
page_sizenumberoptional
Page size
20

Outputs

order_idorder_dateorder_statusitem_countorder_totalreceiver_name

track-shipmentTrack shipmentreadDifficulty: hard

Loads the shipment tracking view for a given order or delivery number. The response reflects live courier progress, estimated delivery windows, and the current tracking step shown in the app.

Inputs

order_idstringrequired
Order identifier
20240618-1234567
tracking_numberstringoptional
Courier tracking number if separate from order ID
987654321012

Outputs

order_idtracking_numberdelivery_companydelivery_statuscurrent_stepestimated_delivery_date

Acceptance

For a given product_id the product name, brand, price, and shipping info must be returned consistently.
Products with options must expose choices like size, color, and model inside the options array.
A non-existent product ID must be treated as an explicit lookup failure, not an empty detail payload.

No account auth required for this operation.

Acceptance

The recent order list must be visible only within an authenticated session; unauthenticated access must be blocked as an auth failure.
Applying the status filter must separate the list by states such as DELIVERING and COMPLETE.
Each order must populate order_id, order_total, delivery_status, and product_name with real values.

Auth required for this operation.

Acceptance

A current delivery stage and estimated arrival date must be resolvable by order number or tracking number.
Pre-shipment, in-transit, and completed states must be distinguished by real status values.
An invalid number must return a lookup failure rather than a fabricated status.

Auth required for this operation.