Override a key-value in the progress store. Generally, you should first use the POST form of this method to avoid overwriting values which may have been set more recently from another client.
PUT /api/v1/user/66a5db1f-2785-498d-9068-e24ddbba03f2/progress/adventure HTTP/1.1
Authorization: Bearer ...
Content-Type: application/json
{
"key": "adventure",
"value": { "some": "data" },
"timestamp": 1554760285
}
----------------------------------------
HTTP/1.1 204 No Content
ETag: W/"a-bAsFyilMr4Ra1hIU5PyoyFRunpI"Authentication is required, and access is restricted to the user.
| Name | Description | Value |
|---|---|---|
| userId | the ID of the user as a GUID with dashes | string |
| key | the key of the key-value pair to return | string |
| Name | Description | Value |
|---|---|---|
| key | the key of the progress data to store (this needs to match the key in the URL) | string |
| value | the data to store at this key | object |
| timestamp | the timestamp this data was written locally; a Unix timestamp in seconds | number |
Successful responses are code 204. Error responses are standard.
NONE