logo
The nextAsks property defines the upcoming valid bid amounts for an auctioned item. It helps clients display what the next acceptable bids will be, based on the current state of the auction.

What Influences nextAsks?

nextAsks is calculated from:
  • The current highest bid, or the startingBid if no bids have been placed
  • The calculation also considers the user context when a user has an active bid on the item.
  • The rules in the bidIncrementTable
The system rounds the current amount down to the nearest valid increment and then applies the increment rule to generate the upcoming asks.

How It Works

  • If no bids exist yet, the startingBid is used as the base
  • The first value in nextAsks is always the minimum next valid bid
  • Each subsequent ask increases by the applicable step from the bidIncrementTable
  • If the startingBid is off-increment, the first ask is the startingBid, and the second ask snaps to the increment grid

📘 Example A: Starting Bid Aligned to Increment

  • startingBid: 1100
  • Increment: 50
Resulting nextAsks:
json
[1100, 1150, 1200, 1250, ...]
All values align with the increment rule.

📘 Example B: Starting Bid Off-Increment

  • startingBid: 1170
  • Increment: 50
Resulting nextAsks:
json
[1170, 1200, 1250, 1300, ...]
  • 1170 is accepted as-is for the first ask
  • 1200 is the first value that aligns with the increment rule
  • All following asks increase from 1200 in steps of 50

💡 Why It Matters

  • nextAsks helps you render bid buttons, sliders, or preset options in the UI
  • It ensures clients always show valid and enforceable bid amounts
  • It reflects dynamic increments based on bid ranges — no hardcoding required