Get Football Club Contract Extensions

View all Football Data API endpoints →

Request a club's contract-extension listing to evaluate a renewals section distinct from incoming and outgoing transfers. Requires teamid. No extension response sample has been verified. Confirm player identities, effective dates, contract terms and statuses from the actual payload before publication. Renewal records should not be counted as new arrivals, and no negotiation or contract-management capability is established.

API Features

Renewal-specific club request A team identifier selects contract-extension information rather than a general transfer direction.
Extensions-versus-arrivals separation Keep contract renewals in their own editorial category instead of counting them as incoming players.
Contract-term evidence checks Display dates or terms only when validated response attributes supply them.
Read-only renewal research This catalogue GET is for information retrieval, not negotiating or editing contracts.

Live API Demo

GET /api/project/football/get-team-contract-extension-transfers-by-team-id

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/football/get-team-contract-extension-transfers-by-team-id?key=<API_KEY>&teamid=8633'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Does a contract-extension request need playerid?

Required teamid scopes this listing to the club. No separate playerid input is declared.

Are expiry dates and contract terms guaranteed?

No response has been demonstrated. Display only dates, terms and statuses actually supplied and verified.

Can renewals be counted as arrivals or used to edit contracts?

No. Keep renewals separate from new signings. This GET retrieves information; it cannot edit or negotiate contracts.

Related operations

Guides

View Subscription Plans →