POST v3/me/teams/{id}/captain/remove

CAPTAIN — remove a teammate from the team. body { memberId, newCaptainId?, deleteTeam?, sentTextMessage? } — memberId = the target's member GUID. Captain-gated; the target must have a roster row on the route team. Wraps TeamApi.RemovePlayer (TeamApi.cs:2996 — re-gates IsSportAdmin || IsTeamAdmin || self, and enforces CanLeaveTeam). Removing a NON-captain just deletes. Removing the CAPTAIN requires either a newCaptainId (another member's GUID, from /captain/reassignoptions) or deleteTeam=true — else the BLL throws RemoveTeamCaptainError (170).

Request Information

Parameters

Name	Description	Additional information
id	team id (captain's team)	Define this parameter in the request URI.
inVO	{ memberId, newCaptainId?, deleteTeam?, sentTextMessage? }	Define this parameter in the request body.

Request body formats

application/json, text/json

Sample:

{
  "memberId": "sample string 1",
  "newCaptainId": "sample string 2",
  "deleteTeam": true,
  "sentTextMessage": true
}

application/xml, text/xml

Sample:

<CaptainRemoveMemberInVO xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/imLeagues.Web.API.Models.Input">
  <deleteTeam>true</deleteTeam>
  <memberId>sample string 1</memberId>
  <newCaptainId>sample string 2</newCaptainId>
  <sentTextMessage>true</sentTextMessage>
</CaptainRemoveMemberInVO>

application/x-www-form-urlencoded

Sample:

Sample not available.

multipart/form-data

Sample:

--MultipartDataMediaFormatterBoundary1q2w3e
Content-Disposition: form-data; name="memberId"

sample string 1
--MultipartDataMediaFormatterBoundary1q2w3e
Content-Disposition: form-data; name="newCaptainId"

sample string 2
--MultipartDataMediaFormatterBoundary1q2w3e
Content-Disposition: form-data; name="deleteTeam"

True
--MultipartDataMediaFormatterBoundary1q2w3e
Content-Disposition: form-data; name="sentTextMessage"

True
--MultipartDataMediaFormatterBoundary1q2w3e--