Get Football Club Outgoing Transfers

View all Football Data API endpoints →

Request a club's outgoing-transfer listing to evaluate a departures page using the returned move statuses and dates. Requires teamid. No departure payload has been verified. Confirm identity, timing and move type before describing a record as a completed permanent departure. Do not automatically remove a player from a squad or infer termination merely because an outgoing record appears.

API Features

Club-departure request scope A team ID selects the outgoing-transfer operation independently of the arrivals read.
Departure timing checks Validate dates and statuses before deciding when a listed move affects an application.
Permanent-move interpretation caution Do not equate every outgoing record with a permanent departure.
Roster removal safeguard Keep roster updates separate until the transfer and squad evidence support the change.

Live API Demo

GET /api/project/football/get-team-players-out-transfers-by-team-id

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/football/get-team-players-out-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

How do I request a club's outgoing transfers?

Confirm teamid and call this departures-specific operation. Incoming moves are retrieved separately.

Does an outgoing record mean a permanent departure?

Not necessarily. Verify identity, dates, move type and status; do not infer permanent departure or contract termination.

Can I automatically remove listed players from the squad?

Do not do so. Check effective status and roster evidence first, and retain disagreements for review.

Related operations

Guides

View Subscription Plans →