mb_bet_update: Perform a Bet Update Action
In xanadunf/matchbook: Wrapper for the Matchbook.com API

Description Usage Arguments Value See Also Examples

This function provides bet update functionality. Its possible to update a single bet by entering in a single value for each of the bet_id, side, odds and stake parameters. It also possible to update multiple bets at once by passing a vector for each of the bet_id, side, odds and stake parameters. In this instance, its imperative that the order in each of the vectors is preserved i.e. that the runner_id, side, odds and stake for the first update are the first elements of each parameter vector, and that the bet_id, side, odds and stake values for the second update are the second elements of each parameter vector and so on. There is a cap of 25 on the number of updates that can be placed at one time.

1	mb_bet_update(session_data, bet_id, side, stake, odds)

`session_data`	A session object returned from a successful mb_login attempt. It contains details about your user preferences and security details.
`bet_id`	The id of the bet that you want to update.
`side`	The side that you want place a bet. This has to be one of either 'back' or 'lay'.
`stake`	The amount that want to stake for this bet. The currency used is the currency you specified when you set up your Matchbook.com account. A real number format is required.
`odds`	The odds you want to place a bet at. The odds type is based on the information from your session_data, which is the default setting saved for your account.

The status and details of your bet updates are returned. The data frame has the following fields:

id: the bet id
event-id: the event id on which the original bet was placed
event-name: the name of the event on which the original bet was placed
event-id: the event id on which the original bet was placed
market-id: the market id on which the original bet was placed
market-name: the name of the market on which the original bet was placed
runner-id: the runner id on which the original bet was placed
runner-name: the name of the runner on which the original bet was placed
temp-id: the temporary id of the update
exchange-type: the exchange type. This should always be 'back-lay'
side: the side the bet was placed on
odds: the odds the bet was placed on
odds-type: the odds-type of the odds field
decimal-odds: the decimal version of the odds
stake: the stake placed
potential-profit: the potential profit if the matched component of this wager is successful
remaining-potential-profit: the potential profit if the un-matched component of this wager is first matched and then has a successful outcome
currency: The currency the bet stake was placed with
created-at: The date the bet was placed
status: The bet status. Status 'open' indicates an unmatched bet, 'matched' indicates a fully matched bet, 'cancelled' indicates a cancelled bet. For bets with status='open', the 'stake' and 'remaining' fields are key to determining the exact status. If the 'remaining' value is less than 'stake' but greater than zero, then the bet has been partially matched for a 'stake'-'remaining' amount. If the bet is fully un-matched, then the 'stake' and 'remaining' values will be equal.

mb_get_bets,mb_bet_place,mb_bet_cancel

## Not run: my_session <- mb_login("my_user_name","verysafepassword"); 
new_odds_value <- 20
mb_bet_update(session_data=my_session,bet_id=12345,odds=new_odds_value)
## End(Not run)