Skip to main content

Match Set Validation

This guide explains the set progression rules for POST /api/v1/matches/verified.

If your source system validates scores before calling the API, implement these rules exactly. Partners should reject invalid score progressions locally instead of sending them to WPPR and waiting for a 400.

Rules​

  • set_1 is always required for both teams.
  • set_2 and set_3 are optional, but if sent for one team they must be sent for the other.
  • Every submitted set must have a winner. Tied scores are rejected.
  • Never send 0:0 for an unplayed set. Omit it instead.
  • A two-set match must end 2:0 (same team wins both sets).
  • A three-set match requires the first two sets to be split 1:1, with set_3 as the decider.

Valid Patterns​

TeamSet 1Set 2Set 3
Team 16——
Team 24——
✓Match is valid
TeamSet 1Set 2Set 3
Team 166—
Team 242—
✓Match is valid
TeamSet 1Set 2Set 3
Team 123—
Team 266—
✓Match is valid
TeamSet 1Set 2Set 3
Team 1466
Team 2614
✓Match is valid
TeamSet 1Set 2Set 3
Team 1632
Team 2466
✓Match is valid
TeamSet 1Set 2Set 3
Team 17——
Team 25——
✓Match is valid

Invalid Patterns​

Try It Yourself​

Try It: Match Score Validator

Team 1

Set 1:
Set 2:
Set 3:

Team 2

Set 1:
Set 2:
Set 3: