-
Notifications
You must be signed in to change notification settings - Fork 7
Submissions
Submissions are sent via HTTP POST to the following endpoint:
POST http(s)://{server}/api/v2/submit/{evaluationId}
The evaluationId is the ID of the evaluation run the participant is currently competing in.
Authentication is handled via a session cookie obtained at login. If no session cookie is present, a session query parameter can be passed instead:
POST http(s)://{server}/api/v2/submit/{evaluationId}?session={sessionToken}
The session token can be found in the DRES UI under the User Profile (top-right menu).
The request body must be JSON. Set the Content-Type: application/json header on the request.
Structure:
{
"answerSets": [
{
"taskId": "optional-task-id",
"taskName": "optional-task-name",
"answers": [ ... ]
}
]
}taskId and taskName are optional — DRES will infer the current active task if omitted. At least one answer is required per answer set.
There are three ways to build an answer:
A) Text answer — provide only the text field:
{
"answerSets": [
{
"answers": [
{ "text": "your answer here" }
]
}
]
}B) Media item answer — provide mediaItemName (and optionally mediaItemCollectionName):
{
"answerSets": [
{
"answers": [
{
"mediaItemName": "video001",
"mediaItemCollectionName": "my-collection"
}
]
}
]
}C) Temporal answer — provide mediaItemName, start, and end in milliseconds:
{
"answerSets": [
{
"answers": [
{
"mediaItemName": "video001",
"mediaItemCollectionName": "my-collection",
"start": 12000,
"end": 18000
}
]
}
]
}| Status | Meaning |
|---|---|
200 |
Submission accepted with a verdict (correct or wrong) |
202 |
Submission accepted, verdict pending (e.g. awaiting human judgement) |
400 |
Malformed request or run not accepting submissions |
401 |
Not authenticated |
404 |
Evaluation ID not found |
412 |
Submission rejected by a submission filter (e.g. duplicate) |