Web service end point to update results for a booking(aka Atlas schedule) using BookingCode. This is the most recommended endpoint to be used by external test drivers. Neither result nor score is revealed to candidate on the UCS candidate website.
PUT https:///bookings/{booking_code}/results
Parameter name | Value | Description | Additional |
---|---|---|---|
booking_code | string | Alphanumeric unique identifier for this exam appointment (aka appointment ID, confirmation ID) |
Required |
The request body takes a complete Candidate Results Details resource, containing the following writable properties:
{
"result": "string",
"score": "string"
}
Name | Type | Description | Additional |
---|---|---|---|
result | string |
What was the outcome of scoring. If you do not wish to provide results to PSI, you can provide NA as a test result but it must also be accompanied with a score value (any integer, for example, 0). Possible values are:
|
|
score | string |
How much did the candidate score. The score can either be Integer or Real or AlphaNumeric. |
This request requires the use of one of following authorisation methods:
OAuth2
.
The following HTTP status codes may be returned, optionally with a response resource.
Status code | Description | Resource |
---|---|---|
200 | OK Expected response to a valid request |
|
400 | Bad Request Error details in case of error situation (When a matching booking code data is not found in Atlas). |
error |
500 | Internal Server Error Internal Server Error (When one or more components are down in Atlas system). In this case test driver is expected to retry to ensure guaranteed delivery. |
error |