[DEPRECATED] GET /v3/bidder/active-bids
const url = 'https://api-ha-prod-p8.handbid.dev/v3/bidder/active-bids?limit=20';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api-ha-prod-p8.handbid.dev/v3/bidder/active-bids?limit=20' \ --header 'Authorization: Bearer <token>'⚠️ DEPRECATED (HAN-1849, 2026-05-21). Replaced by GET /v3/bidder/my-activity which surfaces derived Winning / Losing / Won / Lost statuses + a non-bid purchases[] rail in a single bundled response. This endpoint will be removed one release cycle after iOS confirms migration.
Why replaced: wrong status semantics. Returns raw bids.status (winning/losing/purchase) instead of the derived 4-state lifecycle iOS needs. Also surfaces a single mixed list when iOS wants competition-rail items separate from one-shot purchases.
NEW (HAN-1584, 2026-05-19). Home-screen rail. Items the authenticated user is currently bidding on.
Active-bid item statuses: 1 open, 4 available, 5 pending, 7 closing, 8 extended. Items in final states (2 sold, 6 unsold, 9 reserved, 10 closed, 13 direct-purchase) drop off — the user finds those on /v3/bidder/my-items or they simply disappear.
Bid statuses included: winning, losing, outbid, purchase. (Excludes removed, replaced, failed, etc.) (Note: outbid is not actually a real bids.status value in prod — verified during HAN-1843 audit. The /my-activity endpoint correctly omits it from its CTE.)
Response: { items: [ItemCard...], totalCount }. Each item is a standard ItemCardSerializer card + 3 extra fields, ALL describing the user’s single latest bid on this item (deterministic resolution via (dateInserted DESC, id DESC)):
myLastBidAmount— decimal string of the latest bid’s amount.myBidStatus—winning|losing|outbid|purchase.myLastBidAt— int epoch.
Sort: myLastBidAt DESC, i.id DESC.
Cache: 15s TTL, tag V3CacheTags::userActiveBids — flushed on any bid by the user or any item state transition on items they’ve bid on.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Default 20, range 1-100
Example
20Responses
Section titled “ Responses ”Successful response