My Matches

Start a match

Starts a ready match as the personal API key owner, moving it to in-progress. The owner must be a captain, co-captain, or org owner of the creating or accepted team, and the match must be in the ready state. Requires matches.user_matches:read-write and API writes access. Supports an optional Idempotency-Key header for safe retries.

post/matches/{matchId}/start

Path parameters

matchIdstring required

Match ID.

Response

The match was started 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