> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/definitions/types/predictions.md).

# Predictions

Prediction type IDs, API names, codes and developer\_name values for probabilities, value bets and model performance.

Use the `type_id` on a prediction or model-performance record to look up its exact API name, code and `developer_name`. All 36 types in this reference have `model_type: prediction`.

#### Correct Score: other scorelines (type 240)

For Correct Score predictions, the `Other_1`, `Other_2` and `Other_X` fields represent other scorelines grouped by match outcome:

| Field     | Meaning                          |
| --------- | -------------------------------- |
| `Other_1` | Other score; the home team wins. |
| `Other_2` | Other score; the away team wins. |
| `Other_X` | Other score; a draw.             |

Interpret “other” relative to the individual scorelines listed in the response. These labels do not specify a fixed scoreline cutoff; do not assume a particular goal range from the field names.

The tables reproduce the prediction rows from the full Types export checked on 15 October 2026. No prediction-type IDs above 9706 were present in that export. Preserve the returned spelling, punctuation and case when storing or matching identifiers.

### Using prediction types

A type catalogue is an identifier reference, not a guarantee that every type is returned by every prediction endpoint or every fixture. Match `type_id` to the ID column, request supported related data, and check the endpoint’s response shape and your subscription.

```
GET https://api.sportmonks.com/v3/core/types/240?api_token={{apiToken}}
```

To refresh the catalogue, retrieve all pages of [GET All Types](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/types/get-all-types), then retain rows whose `model_type` is `prediction`. The grouped entities response may contain only the types used by its listed entities and should not replace the full catalogue.

### General type

| ID | Name        | Code        | developer\_name |
| -- | ----------- | ----------- | --------------- |
| 32 | Probability | probability | PROBABILITY     |

### Match and total-goals probabilities

| ID   | Name                            | Code                               | developer\_name                     |
| ---- | ------------------------------- | ---------------------------------- | ----------------------------------- |
| 231  | Both Teams To Score Probability | both-teams-to-score-probability    | BTTS\_PROBABILITY                   |
| 232  | Half Time/Full Time Probability | half-time-full-time-probability    | HTFT\_PROBABILITY                   |
| 233  | First Half Winner Probability   | first-half-winner                  | FIRST\_HALF\_WINNER\_PROBABILITY    |
| 234  | Over/Under 1.5 Probability      | over-under-1\_5-probability        | OVER\_UNDER\_1\_5\_PROBABILITY      |
| 235  | Over/Under 2.5 Probability      | over-under-2\_5-probability        | OVER\_UNDER\_2\_5\_PROBABILITY      |
| 236  | Over/Under 3.5 Probability      | over-under-3\_5\_probability       | OVER\_UNDER\_3\_5\_PROBABILITY      |
| 237  | Fulltime Result Probability     | fulltime-result-probability        | FULLTIME\_RESULT\_PROBABILITY       |
| 238  | Team To Score First Probability | team\_to\_score\_first-probability | TEAM\_TO\_SCORE\_FIRST\_PROBABILITY |
| 239  | Double Chance Probability       | double\_chance-probability         | DOUBLE\_CHANCE\_PROBABILITY         |
| 240  | Correct Score Probability       | correct-score-probability          | CORRECT\_SCORE\_PROBABILITY         |
| 335  | Over/Under 0.5 Probability      | over-under-0\_5-probability        | OVER\_UNDER\_0\_5\_PROBABILITY      |
| 1679 | Over/Under 4.5 Probability      | over-under-4\_5-probability        | OVER\_UNDER\_4\_5\_PROBABILITY      |

### Team total-goals probabilities

| ID  | Name                            | Code                              | developer\_name                      |
| --- | ------------------------------- | --------------------------------- | ------------------------------------ |
| 326 | Home Over/Under 3.5 Probability | home-over-under-3\_5\_probability | HOME\_OVER\_UNDER\_3\_5\_PROBABILITY |
| 327 | Away Over/Under 3.5 Probability | away-over-under-3\_5\_probability | AWAY\_OVER\_UNDER\_3\_5\_PROBABILITY |
| 328 | Away Over/Under 2.5 Probability | away-over-under-2\_5\_probability | AWAY\_OVER\_UNDER\_2\_5\_PROBABILITY |
| 330 | Home Over/Under 2.5 Probability | home-over-under-2\_5\_probability | HOME\_OVER\_UNDER\_2\_5\_PROBABILITY |
| 331 | Home Over/Under 1.5 Probability | home-over-under-1\_5\_probability | HOME\_OVER\_UNDER\_1\_5\_PROBABILITY |
| 332 | Away Over/Under 1.5 Probability | away-over-under-1\_5\_probability | AWAY\_OVER\_UNDER\_1\_5\_PROBABILITY |
| 333 | Away Over/Under 0.5 Probability | away-over-under-0\_5\_probability | AWAY\_OVER\_UNDER\_0\_5\_PROBABILITY |
| 334 | Home Over/Under 0.5 Probability | home-over-under-0\_5\_probability | HOME\_OVER\_UNDER\_0\_5\_PROBABILITY |

### Corner probabilities

| ID   | Name                                | Code                                 | developer\_name                          |
| ---- | ----------------------------------- | ------------------------------------ | ---------------------------------------- |
| 1585 | Corners Over/Under 10.5 Probability | corners-over-under-10\_5-probability | CORNERS\_OVER\_UNDER\_10\_5\_PROBABILITY |
| 1683 | Corners Over/Under 5 Probability    | corners-over-under-5-probability     | CORNERS\_OVER\_UNDER\_5\_PROBABILITY     |
| 1684 | Corners Over/Under 11 Probability   | corners-over-under-11-probability    | CORNERS\_OVER\_UNDER\_11\_PROBABILITY    |
| 1685 | Corners Over/Under 6 Probability    | corners-over-under-6-probability     | CORNERS\_OVER\_UNDER\_6\_PROBABILITY     |
| 1686 | Corners Over/Under 7 Probability    | corners-over-under-7-probability     | CORNERS\_OVER\_UNDER\_7\_PROBABILITY     |
| 1687 | Corners Over/Under 9 Probability    | corners-over-under-9-probability     | CORNERS\_OVER\_UNDER\_9\_PROBABILITY     |
| 1688 | Corners Over/Under 10 Probability   | corners-over-under-10-probability    | CORNERS\_OVER\_UNDER\_10\_PROBABILITY    |
| 1689 | Corners Over/Under 8 Probability    | corners-over-under-8-probability     | CORNERS\_OVER\_UNDER\_8\_PROBABILITY     |
| 1690 | Corners Over/Under 4 Probability    | corners-over-under-4-probability     | CORNERS\_OVER\_UNDER\_4\_PROBABILITY     |

### Value bets

| ID | Name     | Code     | developer\_name |
| -- | -------- | -------- | --------------- |
| 33 | Valuebet | valuebet | VALUEBET        |

### Model performance and predictability

| ID  | Name                   | Code                   | developer\_name          |
| --- | ---------------------- | ---------------------- | ------------------------ |
| 241 | Historical Log Loss    | historical-log-loss    | HISTORICAL\_LOG\_LOSS    |
| 242 | Model Hit Ratio        | model-hit-ratio        | MODEL\_HIT\_RATIO        |
| 243 | Model Predictability   | model-predictability   | MODEL\_PREDICTABILITY    |
| 244 | Model Predictive Power | model-predictive-power | MODEL\_PREDICTIVE\_POWER |
| 245 | Models Log Loss        | models-log-loss        | MODELS\_LOG\_LOSS        |

### Live Predictions

The [Live Predictions tutorial](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions/predictions/live-predictions) documents `type_id: 237` for live full-time result probabilities: `FULLTIME_RESULT_PROBABILITY`. This uses the same type ID listed above. Do not assume every pre-match probability type is supported in live predictions.

### Predictability versus fixture eligibility

Types 241–245 describe model-performance and predictability data. Separately, the fixture metadata type `37072` (`PREDICTION_STATUS`, `model_type: metadata`) exposes `values.predictable`. It is a metadata type, so it is not one of the 36 prediction types in these tables. See [Metadata types](https://docs.sportmonks.com/v3/definitions/types/metadata) for its response shape.

### Related documentation

[Probabilities](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions/predictions/probabilities) · [Value Bet](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions/predictions/value-bet) · [Live Predictions](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/odds-and-predictions/predictions/live-predictions) · [Types definitions](https://docs.sportmonks.com/v3/definitions/types)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportmonks.com/v3/definitions/types/predictions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.