Challonge premier badge
Challonge Premier
Werbung auslenden + Unterstützen Sie uns
Werbung schließen

1.0.4 2017-04-10

Added endpoint for match reopen

Fixed bug where updating a completed match with scores but no winner_id resulted in a match stuck in "pending" state.

Invalid state transitions (e.g. reopening an already open match) are now rescued and returned with typical error formatting.


1.0.3 2016-02-22

Score updates to ongoing matches are now supported, so you may update a match's scores without reporting the winner. As was previously the case, when reporting a match's winner, you must always provide the final scores.


1.0.2 2014-07-28

Added support for participant check-in.

New API end points:

New tournament attributes (see tournaments/update for description):

  • start_at
  • check_in_duration

New participant attribute

  • checked_in_at


1.0.1 2014-07-13

Added endpoints for match attachments

Added include_attachments option to matches/show


1.0.0 2013-10-17

The current API has been labeled v1, and its root URL has moved to https://api.challonge.com/v1. Deprecated routes (challonge.com/api) will continue to work, and we'll give plenty of notice before removing them.

API v2 efforts are underway. Planned additions include OAuth 2.0, read access to all tournaments, improved organization support, and data model changes for tournaments with group stages.


0.16.0 2013-02-26

player1_votes and player2_votes can now be stored on Match records.


0.15.0 2012-12-07

Tournament publish no longer necessary. It will return the same response as show for backward compatibility.

participants_count is now an attribute of a tournament.

signup_cap can now be specified for a tournament.

review_before_finalizing removed from tournament. Review is now required.

POST tournaments/:tournament_id/finalize added. Call once all matches are completed to end a tournament.

on_waiting_list is now an attribute of a participant.


0.14.0 2011-01-12

JSON support added across the board.


0.13.0 2010-12-07

Exposed the following match fields:

identifier
player1_prereq_match_id
player2_prereq_match_id
player1_is_prereq_match_loser
player2_is_prereq_match_loser