New odds ladder July 2021
New Odds ladder
Matchbook will begin using a new odds ladder, with a target date of July 2021.
You will need to ensure your integration is only submitting offers at values that are on the ladder.
New default minimum-liquidity parameter
Starting with Monday 03 September 9 am (GMT+1), Matchbook will introduce a change on the default value of the minimum-liquidity request query parameter on GET /edge/rest/events/... and GET /edge/rest/popular-markets requests.
Keep offers in play
Matchbook now allows you to keep an unmatched offer active when an event goes in play. This will give you more time to have your offer matched.
New market types
Starting with Monday 8th of April 2019 Matchbook will gradually introduce two new market types.
The two new market types being introduced are first_goalscorer and other. Both market types are detailed in the following sections.
Change to GET Offers Response Data
From Tuesday 5th of February 2019 there will be a change to the data returned by the GET /edge/rest/v2/offers and /edge/rest/offers APIs.
V2 offer endpoint released
V2 offer endpoint has been released find details here. https://insights.matchbook.com/live-delay-changes.
Difference between version 1 and version 2 is in InPlay delay and in new status delayed. We introduced a new REST API endpoint /v2/offers where if a submitted/edited placed through the endpoint won't match another offer currently in the market will not be subject to a live delay. This will mean that new prices will reach the market quicker and liquidity is available in play. Behaviour of offer placement through the original endpoint it is not changed.
In case of a delay applied to the offer being submitted, POST /edge/rest/v2/offers will return immediately and the offer returned will have a delayed status. The offer will remain in delayed status for the whole duration of the live delay. Once the delay elapses the offer will transition to one of the statuses already supported by the system (open or matched). Also for PUT /edge/rest/v2/offers response will be returned immediately after the offer modification is registered in the system without waiting for the live delay to elapse. However, the old offer remains in the system until such time as the delay has elapsed, after which the modification attempt will take place.