My Matches

Refuse a match challenge

Refuses a pending challenge as the personal API key owner. The owner must be a captain, co-captain, or org owner of the challenged team. Requires matches.user_matches:read-write and API writes access. Supports an optional Idempotency-Key header for safe retries.

post/matches/{matchId}/challenges/refuse

Path parameters

matchIdstring required

Match ID.

Request body

reasonstring

Optional reason shown to the challenging team.

Response

The challenge was refused successfully.

successtrue required

timestampstring required

Response generation time (ISO 8601).

Changes

Changed in 2 of the 21 revisions of this API.11

Jun 24, 2026fd9c943724311See the full diff
- ○
  endpoint added
  endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Jun 4, 2026f22bd61fd5951See the full diff
- ▲
  api path removed without deprecation
  api-path-removed-without-deprecation
This revision also has 377 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history