> 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/endpoints-and-entities/endpoints/transfer-rumours.md).
# Transfer rumours
> **📦 Partner add-on required**
>
> Transfer rumours data requires the **Transfer Rumours add-on. It** provides transfer speculation, news, and market updates.
>
> **Pricing:**
>
> * Starter: Not available
> * Growth: €99/month
> * Pro: €99/month
> * Enterprise: Included in negotiation
>
> [View pricing and add-ons →](https://www.sportmonks.com/football-api/plans-pricing)
Do you want the latest inside scoop before it hits the headlines? The **Transfer Rumours** endpoint delivers data on potential player moves, straight from the rumour mill. Whether it's speculation or serious chatter, you'll get all the details needed to inform your app visitors.
Each rumour entry provides:
* **Player** involved in the rumour
* **Destination team(s)** the player might join
* **Probability** of the transfer happening
* **Source** of the rumour
* **Monetary value** tied to the deal (if known)
> 💡 A single player can appear in multiple rumours, potentially linked to different destination teams (e.g., both Team A and Team B).
{% hint style="warning" %}
⚠️ These are *rumours*, not confirmed transfers.\
📌 This data is **not linked** to standard models like fixtures or events.\
🔗 Use the **dedicated transfer-rumours endpoints** to retrieve this data.
{% endhint %}
#### Include options
[`sport`](https://docs.sportmonks.com/v3/core-api/) [`player`](/v3/endpoints-and-entities/entities/team-player-squad-coach-and-referee.md#player) [`type`](https://docs.sportmonks.com/v3/core-api/) [`fromTeam`](/v3/endpoints-and-entities/entities/team-player-squad-coach-and-referee.md#team) [`toTeam`](/v3/endpoints-and-entities/entities/team-player-squad-coach-and-referee.md#team) [`position`](https://docs.sportmonks.com/v3/core-api/) [`detailedPosition`](https://docs.sportmonks.com/v3/core-api/) `status`
### Resolving status IDs
Each transfer rumour record contains a `status_id` field. Two options are available to resolve it to a human-readable value.
**Option 1: use the `status` include** to resolve the status inline on any rumour response:
http
```http
GET https://api.sportmonks.com/v3/football/transfer-rumours
?api_token={{apiToken}}&include=status
```
This adds a `status` object to each record with `id`, `name`, `code` and `developer_name`.
**Option 2: use the config endpoint** to fetch all possible values once and cache them locally:
http
```http
GET https://api.sportmonks.com/v3/football/transfer-rumours/config?api_token={{apiToken}}
```
The config endpoint returns all reference values for the transfer rumours entity, covering fee types (`transfer_fee_id`), transfer types (`type_id`), and rumour statuses (`status_id`). See GET Transfer Rumours Config for the full response.
**Possible status values:**
| id | Name | developer\_name |
| ----- | ---------------- | ------------------ |
| 90319 | Confirmed Rumour | `RUMOUR_CONFIRMED` |
| 90320 | Discarded Rumour | `RUMOUR_DISCARDED` |
| 90321 | Obsolete Rumour | `RUMOUR_OBSOLETE` |
| 90322 | Unsure Rumour | `RUMOUR_UNSURE` |
| 90323 | Recent Rumour | `RUMOUR_RECENT` |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/transfer-rumours.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
