JSON Format

Introduction

This document specifies the JSON format used to represent contest data. This format is used by the Contest API and the Contest Package Format.

General design principles

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

JSON property types

Property types are specified as one of the standard JSON types, or one of the more specific types defined below. Implementations must be consistent with respect to the optional parts of each type, e.g. if the optional .uuu is included in any absolute timestamp it must be included when outputting all absolute timestamps.

• Strings (type string in the specification) are built-in JSON strings.
• Numbers (type number in the specification) are built-in JSON numbers.
• Booleans (type boolean in the specification) are built-in JSON booleans.
• Integers (type integer in the specification) are JSON numbers that are restricted to be integer. They should be represented in standard integer representation (-)?[0-9]+.
• Absolute timestamps (type TIME in the specification) are strings containing human-readable timestamps, given in ISO 8601 extended combined date/time format with timezone: yyyy-mm-ddThh:mm:ss(.uuu)?[+-]zz(:mm)? (or timezone Z for UTC).
• Relative times (type RELTIME in the specification) are strings containing human-readable time durations, given in a slight modification of the ISO 8601 extended time format: (-)?(h)*h:mm:ss(.uuu)?
• Identifiers (type ID in the specification) are given as strings consisting of characters [a-zA-Z0-9_.-] of length at most 36 and not starting with a - (dash) or . (dot) or ending with a . (dot). IDs are unique within each endpoint. IDs are assigned by the person or system that is the source of the object, and must be maintained by downstream systems. For example, the person configuring a contest on disk will typically define the ID for each team, and any CCS or CDS that exposes the team must use the same ID.
• Geographic locations (type LOCATION in the specification) are represented as a JSON object; see Location under Object definitions below.
• File references (type FILE in the specification) are represented as a JSON object; see File under Object definitions below.
• Arrays (type array of <type> in the specification) are built-in JSON arrays of some type defined above. Unless specifically mentioned, no meaning is implied or can be inferred from the order of objects in an array.
• Nullable types (type <type> ? in the specification) are either a value of a type defined above, or null.

Object definitions

This section defines the contest data model — the JSON objects used throughout this suite of specifications.

Table column description

In the tables below, the columns are:

• Name: Property name; object sub-properties are indicated as property.subproperty.
• Type: Data type of the property; one of the types listed above.
• Description: Description of the meaning of the property and any special considerations. Required means that the property must be present and must not be null. Default values specify how missing or null values should be interpreted.

Referential integrity

Some properties in objects are references to the id of other objects (type ID or array of ID). When such a property has a non-null value, the referenced object must exist. How this constraint is enforced in practice is context-specific: see the Contest API and Contest Package Format specifications.

Location

Geographic location objects have the following properties:

File

File reference objects have the following properties:

For images, the supported mime types are image/png, image/jpeg, and image/svg+xml.

For images in SVG format, i.e. those having a mime type of image/svg+xml, the values of width and height should be the viewport width and height in pixels when possible, but otherwise the actual values don't matter as long as they are positive and represent the correct aspect ratio.

Known values of tags include:

• light: an image suitable for use on white or light backgrounds.
• dark: an image suitable for use on black or dark backgrounds.

An image should list both values if it is suitable for multiple contexts.

Notification object

Notification objects are used to communicate changes to contest data. They are delivered via the Contest API event feed and webhooks and stored on disk in the Contest Package Format as event-feed.ndjson.

The general format for notification objects is:

{"type": "<type>", "id": "<id>", "data": <JSON data for object> }

The known notification types are: contest, judgement-types, languages, problems, groups, organizations, teams, persons, accounts, state, submissions, judgements, runs, clarifications, awards, commentary.

Each notification object signals that an object or a collection has changed (and hence the contents of the corresponding endpoint) to data.

If type is contest, then id must be null.

If id is not null, then the notification concerns the object of the given type with that id.

If id is null, then the notification concerns the entire collection of the given type.

Examples

Event:

{
   "type": "contest",
   "data": {
      "id": "dress2016",
      "name": "2016 ICPC World Finals Dress Rehearsal",
      "start_time": null,
      "countdown_pause_time": "0:03:38.749",
      "duration": "2:30:00"
  }
}

Means that the contest object with id dress2016 has been updated to the given data.

Event:

{
   "type": "problems",
   "data": [
      {"id":"asteroids","label":"A","name":"Asteroid Rangers","ordinal":1,"color":"blue","rgb":"#00f","time_limit":2,"test_data_count":10},
      {"id":"bottles","label":"B","name":"Curvy Little Bottles","ordinal":2,"color":"gray","rgb":"#808080","time_limit":3.5,"test_data_count":15}
   ]
}

Means that endpoint contests/<contest_id>/problems has been updated to:

[
   {"id":"asteroids","label":"A","name":"Asteroid Rangers","ordinal":1,"color":"blue","rgb":"#00f","time_limit":2,"test_data_count":10},
   {"id":"bottles","label":"B","name":"Curvy Little Bottles","ordinal":2,"color":"gray","rgb":"#808080","time_limit":3.5,"test_data_count":15}
]

and the child endpoints contests/<contest_id>/problems/asteroids and contests/<contest_id>/problems/bottles are updated accordingly.

Event:

{
   "type": "submissions",
   "id": "187",
   "data": {
      "id": "187",
      "team_id": "123",
      "problem_id": "10-asteroids",
      "language_id": "1-java",
      "time": "2014-06-25T11:22:05.034+01",
      "contest_time": "1:22:05.034",
      "entry_point": "Main",
      "files": [{"href":"contests/wf14/submissions/187/files","filename":"files.zip","mime":"application/zip"}]   
   }
}

Means that the submission object with id 187 has been updated to the given data.

API information

The API information object provides metadata about the API and the data provider.

Properties of API information objects:

Properties of the provider object:

Examples

{
   "version": "draft",
   "version_url": "https://ccs-specs.icpc.io/draft/contest_api",
   "provider" : {
      "name": "DOMjudge",
      "version" : "8.3.0DEV/4ac31de71",
      "logo": [{
         "href": "/api/logo",
         "hash": "36dcf7975b179447783cdfc857ce9ae0",
         "filename": "logo.png",
         "mime": "image/png",
         "width": 600,
         "height": 600
      }]
   }
}

Contests

Properties of contest objects:

The typical use of countdown_pause_time is when a contest director wishes to pause the countdown to the start of a contest. For example, this may occur because of technical issues or to make an announcement. When the contest countdown is paused, the value of countdown_pause_time should be set to the expected time remaining before the start of the contest after the pause is lifted. If countdown_pause_time is set, then the start_time must be set to null, thereby, setting an undefined start_time (the start_time is undefined since the length of the pause may be unknown). The countdown_pause_time may be changed to indicate the approximate delay until the contest starts. Countdown is resumed by setting a new start_time and resetting countdown_pause_time to null.

Examples

{
   "id": "wf2014",
   "name": "2014 ICPC World Finals",
   "formal_name": "38th Annual World Finals of the ACM International Collegiate Programming Contest",
   "start_time": "2014-06-25T10:00:00+01",
   "duration": "5:00:00",
   "scoreboard_freeze_duration": "1:00:00",
   "scoreboard_type": "pass-fail",
   "penalty_time": "0:20:00",
   "banner": [{
       "href": "https://example.com/api/contests/wf2014/banner",
       "filename": "banner.png",
       "mime": "image/png",
       "width": 1920,
       "height": 240
   }]
}

{
   "id": "dress2016",
   "name": "2016 ICPC World Finals Dress Rehearsal",
   "start_time": null,
   "countdown_pause_time": "0:03:38.749",
   "duration": "2:30:00",
   "scoreboard_type": "pass-fail",
   "penalty_time": "0:20:00"
}

Judgement Types

Judgement types are the possible responses from the system when judging a submission.

Properties of judgement type objects:

Known judgement types

The list below contains standardized identifiers for known judgement types. These identifiers should be used by a server. Please create a pull request at https://github.com/icpc/ccs-specs when there are judgement types missing.

The column Big 5 lists the "big 5" equivalents, if any. A * in the column means that the judgement is one of the "big 5".

The Translation column lists other judgements the judgement can safely be translated to, if a system does not support it.

Simplified judgement types

In contests with limited visibility or access rules, a simplified judgement type ID defines how each judgement type will be simplified for users without access.

For instance, in a contest where teams cannot see the specific reason another team's submission was rejected, teams might see their own judgement types, but judgements from other teams would return the corresponding simplified judgement type instead.

If not using simplified judgements, the property simplified_judgement_type_id must not be set.

A judgement type may be used both as original and simplified judgement type, but must then simplify to itself and have simplified_judgement_type_id equal to id. For example, AC (aka correct) would typically map to AC also as simplified judgement type.

If a system is interested in finding the set of judgement types that are only original judgement types, only simplified judgement types or both, one can use this logic:

• The set of original judgement types are the ones that have simplified_judgement_type_id set.
• The set of simplified judgement types are the ones that appear in simplified_judgement_type_id.
• The set judgement types that are both is the intersection of these two sets.

This assumes the system is using simplified judgement types. If it is not (i.e. if simplified_judgement_type_id is not set for any judgement type), all judgement types are original only.

Examples

[{
   "id": "RE",
   "name": "Rejected",
   "penalty": true,
   "solved": false
}, {
   "id": "TLE",
   "name": "Time Limit Exceeded",
   "penalty": true,
   "solved": false,
   "simplified_judgement_type_id": "RE"
}, {
   "id": "WA",
   "name": "Wrong Answer",
   "penalty": true,
   "solved": false,
   "simplified_judgement_type_id": "RE"
}, {
   "id": "CE",
   "name": "Compiler Error",
   "penalty": false,
   "solved": false,
   "simplified_judgement_type_id": "CE"
}, {
   "id": "AC",
   "name": "Accepted",
   "penalty": false,
   "solved": true,
   "simplified_judgement_type_id": "AC"
}]

{
   "id": "AC",
   "name": "Accepted",
   "penalty": false,
   "solved": true,
   "simplified_judgement_type_id": "AC"
}

Languages

Languages that are available for submission at the contest.

Properties of language objects:

Properties of Command objects:

The compiler and runner objects are intended for informational purposes. It is not expected that systems will synchronize compiler and runner settings via this interface.

Known languages

Below is a list of standardized identifiers for known languages with their name, extensions and entry point name (if any). When providing one of these languages, the corresponding identifier should be used. The language name and entry point name may be adapted e.g. for localization or to indicate a particular version of the language. In case multiple versions of a language are provided, those must have separate, unique identifiers. It is recommended to choose new identifiers with a suffix appended to an existing one. For example cpp17 to specify the ISO 2017 version of C++.

Examples

[{
   "id": "java",
   "name": "Java",
   "entry_point_required": true,
   "entry_point_name": "Main class",
   "extensions": ["java"],
   "compiler": {
      "command": "javac",
      "args": "-O {files}",
      "version": "javac 11.0.4",
      "version_command": "javac --version"
   },
   "runner": {
      "command": "java",
      "version": "openjdk version \"11.0.4\" 2019-07-16"
   }
}, {
   "id": "cpp",
   "name": "GNU C++",
   "compiler": {
      "command": "gcc",
      "args": "-O2 -Wall -static {files}",
      "version": "gcc (Ubuntu 8.3.0-6ubuntu1) 8.3.0"
   },
   "entry_point_required": false,
   "extensions": ["cc", "cpp", "cxx", "c++", "C"]
}, {
   "id": "python3",
   "name": "Python 3",
   "entry_point_required": true,
   "entry_point_name": "Main file",
   "extensions": ["py"]
}]

Problems

The problems to be solved in the contest.

Properties of problem objects:

Examples

[{"id":"asteroids","label":"A","name":"Asteroid Rangers","ordinal":1,"color":"blue","rgb":"#00f","time_limit":2,"memory_limit":2048,"output_limit":8,"code_limit":128,"test_data_count":10,"statement":[{"href":"contests/wf14/problems/asteroids/statement","mime":"application/pdf","filename":"A.pdf"}],"attachments":[{"href":"contests/wf14/problems/asteroids/attachments/testing_tool.py","mime":"text/x-python","filename":"testing_tool.py"}]},
 {"id":"bottles","label":"B","name":"Curvy Little Bottles","ordinal":2,"color":"gray","rgb":"#808080","time_limit":3.5,"memory_limit":1024,"output_limit":8,"code_limit":128,"test_data_count":15}
]

{"id":"asteroids","label":"A","name":"Asteroid Rangers","ordinal":1,"color":"blue","rgb":"#00f","time_limit":2,"memory_limit":2048,"output_limit":8,"code_limit":128,"test_data_count":10,"statement":[{"href":"contests/wf14/problems/asteroids/statement","mime":"application/pdf","filename":"A.pdf"}],"attachments":[{"href":"contests/wf14/problems/asteroids/attachments/testing_tool.py","mime":"text/x-python","filename":"testing_tool.py"}]}

Groups

Grouping of teams. At the World Finals these are the super regions; at other contests these may be the different sites, divisions, or types of contestants.

Teams may belong to multiple groups. For instance, there may be a group for each site, a group for university teams, a group for corporate teams, and a group for ICPC-eligible teams. Teams could belong to two or three of these. When there are different kinds of groups for different purposes (e.g. sites vs divisions), each group or set of groups should have a different type property (e.g. "type":"site" and "type":"division").

Groups must exist for any combination of teams that must be ranked on a group scoreboard, which means groups may be created for combinations of other groups. For instance, if there is a requirement to show a scoreboard for teams in each of D divisions at every one of S sites, then in addition to the D + S groups there will also be DxS combined/product groups. It is recommended that these groups have a type like "type":"<group1>-<group2>", e.g. "type":"site-division".

Properties of group objects:

Known group types

The list below contains standardized identifiers for known group types. These identifiers should be used when the purpose of a group matches.

Examples

[
  {"id":"asia-74324325532","icpc_id":"7593","name":"Asia"}
]

[
  {"id":"42425","name":"Division 2","type":"division"}
]

Organizations

Teams can be associated with organizations which will have some associated information, e.g. a logo. Typically organizations will be universities.

Properties of organization objects:

Examples

[{"id":"inst123","icpc_id":"433","name":"Shanghai Jiao Tong U.","formal_name":"Shanghai Jiao Tong University"},
 {"id":"inst105","name":"Carnegie Mellon University","country":"USA","country_subdivision":"US-PA",
  "country_flag":[{"href":"http://example.com/api/contests/wf14/flags/USA/56px","filename":"56px.png","mime":"image/png","width":56,"height":56},
          {"href":"http://example.com/api/contests/wf14/flags/USA/160px","filename":"160px.png","mime":"image/png","width":160,"height":160}],
  "country_subdivision_flag":[{"href":"http://example.com/api/contests/wf14/flags/US-PA/56px","filename":"56px.png","mime":"image/png","width":56,"height":56},
          {"href":"http://example.com/api/contests/wf14/flags/US-PA/160px","filename":"160px.png","mime":"image/png","width":160,"height":160}],
  "logo":[{"href":"http://example.com/api/contests/wf14/organizations/inst105/logo/56px","filename":"56px.png","mime":"image/png","width":56,"height":56},
          {"href":"http://example.com/api/contests/wf14/organizations/inst105/logo/160px","filename":"160px.png","mime":"image/png","width":160,"height":160}]
 }
]

Teams

Teams competing in the contest.

Properties of team objects:

Properties of team location objects:

Examples

[{"id":"team11","icpc_id":"201433","label":"11","name":"Shanghai Tigers","organization_id":"inst123","group_ids":["asia-74324325532"]},
 {"id":"team123","label":"123","name":"CMU1","organization_id":"inst105","group_ids":["8","11"]}
]

Persons

Persons involved in the contest.

Properties of person objects:

Examples

[{"id":"john-smith","team_ids":["43"],"icpc_id":"32442","name":"John Smith","email":"john.smith@kmail.com","sex":"male","role":"contestant"},
 {"id":"osten-umlautsen","team_ids":["43","44"],"icpc_id":null,"name":"Östen Ümlautsen","sex":null,"role":"coach"},
 {"id":"bill","name":"Bill Farrell","sex":"male","title":"Executive Director","role":"staff"}
]

Accounts

The accounts used for accessing the contest, as well as information about the account currently accessing the API. Note that the Contest API also provides a contests/<id>/account endpoint (singular) which returns the account of the currently authenticated client; this endpoint does not appear in a Contest Package.

Properties of account objects:

Accounts exist in the API primarily for configuration from a contest package, or an administrator comparing one CCS to another. It is expected that non-admin clients never see passwords, and typically do not see accounts other than their own.

Examples

[{"id":"stephan","username":"stephan","name":"Stephan's home account","type":"judge","ip":"10.0.0.1"},
 {"id":"team45","username":"team45","type":"team","ip":"10.1.1.45","team_id":"45"}
]

{"id":"nicky","username":"nicky","type":"admin"}

Access

The access object describes which endpoints and properties are visible to the current client, and what capabilities the client has. It is only available via the Contest API; the corresponding file does not appear in a Contest Package.

Properties of access objects:

Properties of endpoint objects:

Examples

{
   "capabilities": ["contest_start"],
   "endpoints": [
     { "type": "contest", "properties": ["id","name","formal_name",...]},
     { "type": "problems", "properties": ["id","label",...]},
     { "type": "submissions", "properties": ["id","language_id","reaction",...]}
     ...
   ]
}

or:

{
   "capabilities": ["team_submit"],
   "endpoints": [
     { "type": "contest", "properties": ["id","name","formal_name",...]},
     { "type": "problems", "properties": ["id","label",...]},
     { "type": "submissions", "properties": ["id","language_id",...]},
     ...
   ]
}

Contest state

Current state of the contest, specifying whether it's running, the scoreboard is frozen or results are final.

Properties of state objects:

These state changes must occur in the order listed in the table above, as far as they do occur, except that thawed and finalized may occur in any order. For example, the contest may never be frozen and hence not thawed either, or, it may be finalized before it is thawed. I.e., the following sequence of inequalities must hold:

started < frozen < ended < thawed    < end_of_updates,
                   ended < finalized < end_of_updates.

A contest that has ended, been thawed (or was never frozen) and is finalized must not change. Thus, end_of_updates can be set once both finalized is set and thawed is set if the contest was frozen.

Examples

{
  "started": "2014-06-25T10:00:00+01",
  "ended": null,
  "frozen": "2014-06-25T14:00:00+01",
  "thawed": null,
  "finalized": null,
  "end_of_updates": null
}

Submissions

Submissions, a.k.a. attempts to solve problems in the contest.

Properties of submission objects:

The entry_point property must be included for submissions in languages which do not have a single, unambiguous entry point to run the code. In general the entry point is the string that needs to be specified to point to the code to be executed. Specifically, for Python it is the file name that should be run, and for Java and Kotlin it is the fully qualified class name (that is, with any package name included, e.g. com.example.myclass for a class in the package com.example in Java). For C and C++ no entry point is required and it must therefore be null.

The files property provides the file(s) of a given submission as a zip archive. These must be stored directly from the root of the zip file, i.e. there must not be extra directories (or files) added unless these are explicitly part of the submission content.

Examples

[{"id":"187","team_id":"123","problem_id":"10-asteroids",
  "language_id":"1-java","time":"2014-06-25T11:22:05.034+01","contest_time":"1:22:05.034","entry_point":"Main",
  "files":[{"href":"contests/wf14/submissions/187/files","filename":"files.zip","mime":"application/zip"}]}
]

Note that the relative link for files points to the location https://example.com/api/contests/wf14/submissions/187/files since the base URL for the API is https://example.com/api/.

Judgements

Judgements for submissions in the contest.

Properties of judgement objects:

A judgement must have at least one of judgement_type_id or simplified_judgement_type_id specified iff it is completed. If both judgement_type_id and simplified_judgement_type_id are present, they should be consistent with the simplification rules specified in the judgement-types endpoint.

When a judgement is started, each of judgement_type_id, end_time and end_contest_time will be null (or missing). These are set when the judgement is completed.

Examples

[{"id":"189549","submission_id":"wf2017-32163123xz3132yy","judgement_type_id":"CE","start_time":"2014-06-25T11:22:48.427+01",
  "start_contest_time":"1:22:48.427","end_time":"2014-06-25T11:23:32.481+01","end_contest_time":"1:23:32.481"},
 {"id":"189550","submission_id":"wf2017-32163123xz3133ub","judgement_type_id":null,"start_time":"2014-06-25T11:24:03.921+01",
  "start_contest_time":"1:24:03.921","end_time":null,"end_contest_time":null}
]

Runs

Runs are judgements of individual test cases of a submission. This is intended to provide (among other things) live updates of judging progress.

Properties of run objects:

Examples

[{"id":"1312","judgement_id":"189549","ordinal":28,"judgement_type_id":"TLE",
  "time":"2014-06-25T11:22:42.420+01","contest_time":"1:22:42.420","run_time":0.123}
]

Clarifications

Clarification message sent between teams and judges, a.k.a. clarification requests (questions from teams) and clarifications (answers from judges).

Properties of clarification message objects:

The recipients of a clarification are the union of to_team_ids and to_group_ids. A clarification is sent to all teams if from_team_id, to_team_ids and to_group_ids are null. Note that if from_team_id is not null, then both to_team_ids and to_group_ids must be null. That is, teams cannot send messages to other teams or groups.

Clarifications between a team and the judges are typically private. If the judges replies to a clarification and chooses to include additional recipients, then in order to preserve referential integrity the reply_to_id should be removed for everyone who couldn't see the original message.

Examples

[{"id":"wf2017-1","from_team_id":null,"to_team_ids":null,"to_group_ids":null,"reply_to_id":null,"problem_id":null,
  "text":"Do not touch anything before the contest starts!","time":"2014-06-25T11:59:27.543+01","contest_time":"-0:15:32.457"}
]

[{"id":"1","from_team_id":"34","to_team_ids":null,"to_group_ids":null,"reply_to_id":null,"problem_id":null,
  "text":"May I ask a question?","time":"2017-06-25T11:59:27.543+01","contest_time":"1:59:27.543"},
 {"id":"2","from_team_id":null,"to_team_ids":["34"],"reply_to_id":"1","problem_id":null,
  "text":"Yes you may!","time":"2017-06-25T11:59:47.543+01","contest_time":"1:59:47.543"}
]

[{"id":"1","from_team_id":"34","text":"May I ask a question?","time":"2017-06-25T11:59:27.543+01","contest_time":"1:59:27.543"},
 {"id":"2","to_team_ids":["34","57","69"],"to_group_ids":["1336"], "reply_to_id":"1","text":"Yes you may!","time":"2017-06-25T11:59:47.543+01","contest_time":"1:59:47.543"}
]

Awards

Awards such as medals, first to solve, etc.

Properties of award objects:

Semantics

• Awards are not final until the contest is.
• An award may be created at any time, although it is recommended that a system creates the awards it intends to award before the contest starts.
• If an award has a non-null team_ids, then it must be kept up to date during the contest. E.g. if "winner" will not be updated with the current leader during the contest, it must be null until the award is updated.
• If an award is present during the contest this means that if the contest would end immediately and then become final, that award would be final. E.g. the "winner" during the contest should be the current leader. This is of course subject to what data the client can see; the public client's winner may not change during the scoreboard freeze but an admin could see the true current winner.

Known awards

For some common award cases the following IDs should be used.

Examples

[{"id":"gold-medal","citation":"Gold medal winner","team_ids":["54","23","1","45"]},
 {"id":"first-to-solve-a","citation":"First to solve problem A","team_ids":["45"]},
 {"id":"first-to-solve-b","citation":"First to solve problem B","team_ids":[]}
]

Commentary

Commentary on events happening in the contest.

Properties of commentary objects:

For the message, if a literal { is needed, \{ must be used. Similarly for a literal \, \\ must be used.

Known tags

Below is a list of known tags. If any of the tags below are used, they must have the corresponding meaning. If the any of the meanings below are needed, the corresponding tag should be used. There is no requirement that any of the tags below are used.

Examples

[{"id":"143730", "time":"2021-03-06T19:02:02.328+00", "contest_time":"0:02:02.328", "message": "{t:314089} made a submission for {p:anttyping}. If correct, they will solve the first problem and take the lead", "team_ids": ["314089"], "problem_ids": ["anttyping"]}, 
 {"id": "143736", "time": "2021-03-06T19:02:10.858+00", "contest_time": "0:02:10.858", "message": "{t:314089} fails its first attempt on {p:anttyping} due to WA", "team_ids": ["314089"], "problem_ids": ["anttyping"]}, 
 {"id": "143764", "time": "2021-03-06T19:03:07.517+00", "contest_time": "0:03:07.517", "message": "{t:314115} made a submission for {p:march6}. If correct, they will solve the first problem and take the lead", "team_ids": ["314115"], "problem_ids": ["march6"]}
]

Scoreboard

Scoreboard of the contest.

Since this is generated data, only the GET method is allowed in the Contest API, irrespective of role.

Properties of the scoreboard object.

The scoreboard rows array is sorted according to rank and alphabetical on team name within identically ranked teams. Here alphabetical ordering means according to the Unicode Collation Algorithm, by default using the en-US locale.

Properties of scoreboard row objects:

Properties of problem data objects:

Examples

{
  "time": "2014-06-25T14:13:07.832+01",
  "contest_time": "4:13:07.832",
  "state": {
    "started": "2014-06-25T10:00:00+01",
    "ended": null,
    "frozen": "2014-06-25T14:00:00+01",
    "thawed": null,
    "finalized": null,
    "end_of_updates": null
  },
  "rows": [
    {"rank":1,"team_id":"123","score":{"num_solved":3,"total_time":"5:40:00","time":"3:25:00"},"problems":[
      {"problem_id":"1","num_judged":3,"num_pending":1,"solved":false},
      {"problem_id":"2","num_judged":1,"num_pending":0,"solved":true,"time":"0:20:00"},
      {"problem_id":"3","num_judged":2,"num_pending":0,"solved":true,"time":"0:55:00"},
      {"problem_id":"4","num_judged":0,"num_pending":0,"solved":false},
      {"problem_id":"5","num_judged":3,"num_pending":0,"solved":true,"time":"3:25:00"}
    ]}
  ]
}