> 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/get-transfer-rumours-config.md). # GET Transfer Rumours Config Returns all configuration values for the transfer rumours entity: fee types, transfer types, and rumour status values. Use this as a reference to resolve the `transfer_fee_id`, `type_id`, and `status_id` fields on any transfer rumour record without making additional includes. {% tabs %} {% tab title="Request" %} ```http GET https://api.sportmonks.com/v3/football/transfer-rumours/config ?api_token={{apiToken}} ``` {% endtab %} {% tab title="Response" %} ```json { "fee": [ { "id": 78365, "name": "Confirmed Amount", "code": "confirmed-amount", "developer_name": "CONFIRMED_AMOUNT", "model_type": "fee", "stat_group": null }, { "id": 78366, "name": "Free transfer", "code": "free-transfer", "developer_name": "FREE_TRANSFER", "model_type": "fee", "stat_group": null }, { "id": 78367, "name": "Estimated Amount", "code": "estimated-amount", "developer_name": "ESTIMATED_AMOUNT", "model_type": "fee", "stat_group": null }, { "id": 78368, "name": "Unknown Amount", "code": "unkown-amount", "developer_name": "UNKNOWN_AMOUNT", "model_type": "fee", "stat_group": null }, { "id": 78369, "name": "No Amount", "code": "no-amount", "developer_name": "NO_AMOUNT", "model_type": "fee", "stat_group": null } ], "transfers": [ { "id": 218, "name": "Loan", "code": "loan-transfer", "developer_name": "LOAN_TRANSFER", "model_type": "transfer", "stat_group": null }, { "id": 219, "name": "Transfer", "code": "transfer", "developer_name": "TRANSFER", "model_type": "transfer", "stat_group": null }, { "id": 220, "name": "Free Transfer", "code": "free-transfer", "developer_name": "FREE_TRANSFER", "model_type": "transfer", "stat_group": null }, { "id": 9688, "name": "End of loan", "code": "end-of-loan", "developer_name": "END_OF_LOAN", "model_type": "transfer", "stat_group": null }, { "id": 78370, "name": "Contract extension", "code": "contract-extension", "developer_name": "CONTRACT_EXTENSION", "model_type": "transfer", "stat_group": null }, { "id": 83609, "name": "Loan", "code": "loan", "developer_name": "LOAN", "model_type": "transfer", "stat_group": null } ], "statuses": [ { "id": 90319, "name": "Confirmed Rumour", "code": "rumour-confirmed", "developer_name": "RUMOUR_CONFIRMED", "model_type": "rumour-status", "stat_group": null }, { "id": 90320, "name": "Discarded Rumour", "code": "rumour-discarded", "developer_name": "RUMOUR_DISCARDED", "model_type": "rumour-status", "stat_group": null }, { "id": 90321, "name": "Obsolete Rumour", "code": "rumour-obsolete", "developer_name": "RUMOUR_OBSOLETE", "model_type": "rumour-status", "stat_group": null }, { "id": 90322, "name": "Unsure Rumour", "code": "rumour-unsure", "developer_name": "RUMOUR_UNSURE", "model_type": "rumour-status", "stat_group": null }, { "id": 90323, "name": "Recent Rumour", "code": "rumour-recent", "developer_name": "RUMOUR_RECENT", "model_type": "rumour-status", "stat_group": null } ] } ``` {% endtab %} {% tab title="Field Description" %} The response contains three top-level arrays. **`fee`** - fee type values for the `transfer_fee_id` field on a rumour record | Field | Description | Type | | ---------------- | -------------------------------------------------------------- | ------- | | `id` | The fee type id. Matches `transfer_fee_id` on a rumour record. | integer | | `name` | Human-readable fee type name. | string | | `code` | URL-safe code for the fee type. | string | | `developer_name` | Stable machine-readable identifier. | string | **`transfers`** - transfer type values for the `type_id` field on a rumour record | Field | Description | Type | | ---------------- | ----------------------------------------------------------- | ------- | | `id` | The transfer type id. Matches `type_id` on a rumour record. | integer | | `name` | Human-readable transfer type name. | string | | `code` | URL-safe code for the transfer type. | string | | `developer_name` | Stable machine-readable identifier. | string | **`statuses`** - rumour status values for the `status_id` field on a rumour record | Field | Description | Type | | ---------------- | ------------------------------------------------------ | ------- | | `id` | The status id. Matches `status_id` on a rumour record. | integer | | `name` | Human-readable status name. | string | | `code` | URL-safe code for the status. | string | | `developer_name` | Stable machine-readable identifier. | string | | {% endtab %} | | | | {% endtabs %} | | | | Query Parameter | Required | Description | | --------------- | -------- | ---------------------- | | `api_token` | YES | Your unique API token. | **Pagination** NO **Include options** `none` **When to use this endpoint** Call this once at application startup and cache the result. The values in all three arrays are stable reference data that do not change frequently. Mapping `status_id`, `transfer_fee_id`, and `type_id` from this cached response is more efficient than using the `status` or `type` includes on every rumour request. **Code Example** {% tabs %} {% tab title="Javascript" %} ```javascript const response = await fetch( "https://api.sportmonks.com/v3/football/transfer-rumours/config ?api_token=YOUR_TOKEN" ); const config = await response.json(); // Map status IDs to names for quick lookup const statusMap = Object.fromEntries( config.statuses.map(s => [s.id, s.name]) ); // e.g. { 90319: "Confirmed Rumour", 90320: "Discarded Rumour", ... } ``` {% endtab %} {% tab title="Python" %} ```python import http.client import json conn = http.client.HTTPSConnection("api.sportmonks.com") conn.request("GET", "/v3/football/transfer-rumours/config?api_token=YOUR_TOKEN") res = conn.getresponse() config = json.loads(res.read().decode("utf-8")) status_map = {s["id"]: s["name"] for s in config["statuses"]} # e.g. {90319: "Confirmed Rumour", 90320: "Discarded Rumour", ...} ``` {% endtab %} {% tab title="PHP" %} ```php "Confirmed Rumour", 90320 => "Discarded Rumour", ...] ``` {% endtab %} {% endtabs %} --- # 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/endpoints-and-entities/endpoints/transfer-rumours/get-transfer-rumours-config.md?ask=&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.