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
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/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'
Query Result
Use Cases
- Add a separate renewals section to a club transfer page.
- Create a contract-extension review queue for an editor to verify returned terms.
- Reconcile renewal player IDs with the club roster without treating them as signings.
- Audit whether returned extension dates support a season-specific editorial summary.
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.