> For the complete documentation index, see [llms.txt](https://docs.odds88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.odds88.io/integration-process/recommended-integration-flow/optional-features/betbuilder-integration/bet-creation-flow.md).

# Bet creation flow

After a player makes the first selection, it is not needed to send a request to the BetBuilder price endpoint. For a BetBuilder bet to be created **at least two** selections have to be made.

When a player makes a second and every following selection, you will need to send a request to the **bet-builder-price** endpoint with selections the player made. In response to this request you will receive a price or rejection reason.

On any update player does to the BetBuilder selections (adding or removing a selection), you have to fetch the new, updated price via **bet-builder-price** endpoint.

If, upon adding a new selection and fetching a new price, the price is left unchanged, the selection has no effect on the price and thus, should not be added to the betslip. In this case, a corresponding message is displayed to the player - “**added selection does not increase price/odds**”.\
**The new selection should then be removed from the betslip.**

If, upon adding a new selection and fetching a new price, the returned price is 0, the selections are in conflict and the combination is therefore impossible.\
**The new selection should then be removed from the betslip.**

After the player finishes building a bet, it is possible to add this bet to Bet Slip with the last received odds for selected combination. From now on BetBuilder bet is treated as any other bet and **can be used** as a leg of a multibet in combination with any other market or another BetBuilder bet from another event.