# Delete a team `DELETE /api/v1/teams/{id}` `POST /api/v1/teams/{id}/delete` Marks the team as deleted and removes it from List and Retrieve. ## Permissions Send your API key in `X-API-Key`. Required permissions are **Teams → Write**. ## Headers - `X-Sport-Id` (integer, required) — The sport ID from [List sports](/api/sports/list.md). Use the sport the team belongs to. ## Path parameters - `id` (integer, required) — The team ID returned by [List teams](/api/teams/list.md). Use [Update a team](/api/teams/update.md) if you want to retain the team in the archived list. ## Request (DELETE) Set ASDINCLOUD_API_KEY, SPORT_ID, and TEAM_ID before running. ```sh curl --request DELETE \ --url "https://api.asdincloud.com/api/v1/teams/${TEAM_ID:?Set TEAM_ID}" \ --header "X-API-Key: $ASDINCLOUD_API_KEY" \ --header "X-Sport-Id: $SPORT_ID" ``` ## Request (POST) Set ASDINCLOUD_API_KEY, SPORT_ID, and TEAM_ID before running. ```sh curl --request POST \ --url "https://api.asdincloud.com/api/v1/teams/${TEAM_ID:?Set TEAM_ID}/delete" \ --header "X-API-Key: $ASDINCLOUD_API_KEY" \ --header "X-Sport-Id: $SPORT_ID" ``` ## Response **200 OK** Returns a confirmation. A repeat request for the same ID returns `404`. Example with fictional data and selected fields. ```json { "message_key": "entities.team.messages.deleted" } ``` ## Errors - `401` — The API key is missing or invalid. - `403` — The API key lacks one or more required permissions. - `404` — The team was not found in the selected sport. Requests with missing or unavailable sport context can also return this status. - `400` — The deletion could not be completed.