POST v3/me/teams/{id}/challenges/handle

CAPTAIN — accept/reject an INCOMING challenge (type 0) or cancel an OUTGOING one (type 1). body { challengeId, action:"accept"|"delete", type:0|1 }. Captain-gated on the route team, plus a cross-team guard: the challenge's acceptor(type 0)/initiator(type 1) team must equal the route team. Wraps the page-pure TeamApi.HandleChallengeRequest (TeamApi.cs:7289 — re-gates IsTeamAdmin; accept → MarkAccepted() creates a published game).

Request Information

Parameters

Name	Description	Additional information
id	team id (captain's team)	Define this parameter in the request URI.
inVO	{ challengeId, action, type }	Define this parameter in the request body.

Request body formats

application/json, text/json

Sample:

{
  "challengeId": 1,
  "action": "sample string 2",
  "type": 3
}

application/xml, text/xml

Sample:

<CaptainChallengeHandleInVO xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/imLeagues.Web.API.Models.Input">
  <action>sample string 2</action>
  <challengeId>1</challengeId>
  <type>3</type>
</CaptainChallengeHandleInVO>

application/x-www-form-urlencoded

Sample:

Sample not available.

multipart/form-data

Sample:

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

1
--MultipartDataMediaFormatterBoundary1q2w3e
Content-Disposition: form-data; name="action"

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

3
--MultipartDataMediaFormatterBoundary1q2w3e--