v1.6.0

API Version 1.6.0

This patch feeds from v1.5.0, adding more information about event participants.

Additions:

• Added platform attribute to the Creator object, indicating which platform the user is streaming on.

Changes:

• Increased rate limits from 40 requests per minute to 200 requests per minute.

---

v1.5.0

API Version 1.5.0

This patch allows for the filtering of participants by UUID.

Additions:

• Added a new /v1/participant/{uuid} endpoint, accepting dashed and undashed UUIDs.

Changes:

• To ensure consistency between /v1/participant/ and v1/participants/ endpoints, a new team attribute has been added to the Creator object to indicate the participant's team.

---

v1.4.0

API Version 1.4.0

This patch makes previously hidden non-canon events from Season 3 visible. It also provides a way for developers to easily identify valid event keys for use in rundown endpoints.

Additions:

• Added a new /v1/events endpoint, returning a list of valid event keys.

Changes:

• Made the following event keys visible, as requested in #13: AF, P23, R2, PARTY, TR.
• Prevent internal fields from being shown in current-event history data.

---

v1.3.3

API Version 1.3.3

This patch adds a new attribute to the Creator object, accessible in the /v1/participants and v1/participants/{team} endpoints.

Changes:

• Added a new icon attribute to the Creator object.

---

v1.3.2

API Version 1.3.2

This patch fixes an issue on start-up that caused CORS to be disabled.

Changes:

• CORS has been enabled properly (#8).

---

v1.3.1

API Version 1.3.1

This patch fixes data inaccuracies within Time Machine (the historical data system).

Changes:

• /v1/rundown/{event} now gives correct event placement data for MCC 3.

---

v1.3.0

API Version 1.3.0

This minor release brings the API up-to-date with MCC Live by deprecating some now inactive features and fixing some minor bugs with the History system.

Changes:

• /v1/halloffame and /v1/halloffame/{game} have both been deprecated and will be removed in a future release of the API. You will have noticed that the in-game Hall of Fame is currently under maintenance, and we'll be bringing new statistics to the API as soon as possible once it's complete. We will not remove these endpoints until the API supports the new system.
• Fixed minor bugs with /v1/rundown/{event}.

v1.2.0

API Version 1.2.0

Our second API update brings significant changes to the historical side of available data, alongside some general performance improvements behind-the-scenes to support MCC Live's needs.

This update has no breaking changes and existing apps will work fine on modified endpoints, but you may need to make changes to suit the needs of your application.

Additions:

• /v1/rundown/{event} - returns summary data for the event you give including event scores, participants and the order of games. Any event from Season 3 beyond gives a full rundown of each game including its game and individual scores. Events before Season 3 will receive this data soon.

Changes:

• /v1/rundown - now returns data from the most recent numbered (canon) MCC event.
• RundownResponse - modified to include history and creators as per the updates above.

v1.1.0

API Version 1.1.0

This is our first update to the API directly since its launch. We've been happy with its stability and are introducing a few user-requested features, note that there are no breaking changes to existing endpoints. Keep those suggestions coming in and we hope to implement them in future releases!

Minor changes:

• /v1/halloffame - added a changedHands Boolean property to show if the holder gained the record last event.
• v1/participants - added a stream property which links to our internal value for where they are streaming, as suggested in #5.
• Better documentation on Swagger featuring more in-depth schemas for some endpoints.

This update corresponds with MCC Live's update to main-5106796e.