# Bet365 Result

## HTTP Request

<mark style="color:blue;">`GET`</mark> `https://bet365-sports-odds.p.rapidapi.com/v1/bet365/result`

curl "<https://bet365-sports-odds.p.rapidapi.com/v1/bet365/result?event\\_id=86255646>"

#### Path Parameters

| Name      | Type   | Description                      |
| --------- | ------ | -------------------------------- |
| event\_id | string | Event ID (FI) from Bet365 Inplay |

#### Headers

| Name            | Type   | Description |
| --------------- | ------ | ----------- |
| x-rapidapi-key  | string |             |
| x-rapidapi-host | string |             |

{% tabs %}
{% tab title="200 " %}

```
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
you can send multiple event\_ids in one request with event\_id=1,2,3,4 up to max 10 ids.
{% endhint %}

## HTTP Response

{% file src="/files/-M0LPqLW6CL6xCbQVPjj" %}
bet365\_result.json
{% endfile %}

> league.id/home.id/away.id returned from bet365/result might be different than bet365/upcoming.

[Fields Explanation](/bet365-api/bet365-fields-explanation.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://1394697259.gitbook.io/bet365-api/bet365-result.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.