# Booking Calendar

In the daily schedule, all sports events are listed with a “live-odds” attribute.

This attribute lists the match-booking state and can be in the following states: 

* ***booked*** (already booked),
* ***bookable*** (can be booked),
* ***buyable*** (need to be bought before it can be booked, contact your sales representative), and
* ***unavailable*** (currently not available at all for live booking)

### Endpoint Description <a href="#uofapibookingcalendar-endpointdescription" id="uofapibookingcalendar-endpointdescription"></a>

This endpoint is used to book a match for live coverage.

This is only for live odds where a customer can request a booking of a particular match.

| **HTTP** | **Endpoint**                               | **Description**                                               |
| -------- | ------------------------------------------ | ------------------------------------------------------------- |
| POST     | liveodds/booking-calendar/events/(id)/book | POST on this endpoint to put a match in the booking calendar. |

### Endpoint Parameters <a href="#uofapibookingcalendar-endpointparameters" id="uofapibookingcalendar-endpointparameters"></a>

| Parameter | Description                                          |
| --------- | ---------------------------------------------------- |
| *id*      | The ID for the sport event to get fixture data from. |

### Example Response <a href="#uofapibookingcalendar-exampleresponse" id="uofapibookingcalendar-exampleresponse"></a>

```xml
<response response_code="OK">
    <action>Request for booking an event : sr:match:12345678 from bookmaker: 1234 received</action>
    <message>OK.</message>
</response>
```