Get All Player Id Settings For Setting Type
GET/settings/v1/player/:player_id/setting_type/:setting_type_id/key
DEPRECATED - Use v2 instead. Get a list of all player setting documents for a specific Setting Type.
Required Permissions:
-
For any player (including themselves) any of:
setting:*:*,setting:read -
For the player themselves :
setting:read:self
Request
Path Parameters
Player to get settings for
Setting Type to get settings for. Must be one of the known setting types
Query Parameters
Possible values: non-empty and <= 256 characters
Setting Key to get settings for. If not specified, all settings for the setting type will be returned
Header Parameters
Precondition check if the resource's current ETag matches the provided values. * can be used to match any existing value.
See https://www.rfc-editor.org/rfc/rfc9110#name-if-match for more information
Precondition check if the resource's current ETag does NOT match the provided values. * can be used to match existing value, causing the request to fail.
See https://www.rfc-editor.org/rfc/rfc9110#name-if-none-match for more information
Precondition check if the resource's Last-Modified date is newer than the provided date. Ignored if the If-None-Match header is provided. Only valid for GET/HEAD endpoints.
See https://www.rfc-editor.org/rfc/rfc9110#name-if-modified-since for more information
Precondition check if the resource's Last-Modified date is older than the provided date. Ignored if the If-Match header is provided.
See https://www.rfc-editor.org/rfc/rfc9110#name-if-unmodified-since for more information
Responses
- 200
- 304
- 400
- 403
- 404
- 412
- 422
Successful Response
Response Headers
ETag
string
The ETag for the resource. Used for caching and preconditions.
Last-Modified
string
The Last-Modified date for the resource. Used for caching and preconditions.
- application/json
- Schema
- Example (from schema)
Schema
- MOD1
- Time Zone Aware Datetime
property name*
SettingData
Setting version/value document from a specific setting type/key for a player
Version of the Setting Type schema that was used to validate the value document.
Setting Value document
etag
object
ETag identifying the current version+value of the document
anyOf
string
last_modified
object
Timestamp when this setting was last modified
anyOf
Datetime that enforces that a timezone is given. Unix timestamps are allowed and forced into the UTC time zone
string
{}
The resource has not been modified from the provided preconditions.
Response Headers
ETag
string
The ETag for the resource. Used for caching and preconditions.
Last-Modified
string
The Last-Modified date for the resource. Used for caching and preconditions.
Error Codes:
-
setting_type_not_supported- The setting type is not supported at this time. Contact an administrator
- application/json
- Schema
- Example (from schema)
Schema
Default value: true
{
"auth_success": true,
"error_code": "string",
"desc": "string"
}
Error Codes:
-
auth_invalid_key_id- Invalid Authorization - Invalid Key ID in Access Token -
auth_invalid_version- Invalid Authorization - version -
auth_malformed_access- Invalid Authorization - malformed access token -
auth_not_jwt- Invalid Authorization -
auth_token_expired- Token is expired -
auth_token_format- Invalid Authorization - {} -
auth_token_invalid_claim- Token contained invalid claim value: {} -
auth_token_invalid_type- Invalid Authorization - Invalid Token Type -
auth_token_sig_invalid- Token Signature is invalid -
auth_token_unknown- Failed to parse token -
insufficient_permissions- Insufficient Permissions
- application/json
- Schema
- Example (from schema)
Schema
Default value: true
{
"auth_success": true,
"error_code": "string",
"desc": "string"
}
Error Codes:
-
setting_type_id_not_found- The setting type ID was not found
- application/json
- Schema
- Example (from schema)
Schema
Default value: true
{
"auth_success": true,
"error_code": "string",
"desc": "string"
}
The resource does not meet the provided preconditions.
Validation Error
- application/json
- Schema
- Example (from schema)
Schema
Array [
Array [
- MOD1
- MOD2
]
]
detail
object[]
loc
object[]
required
anyOf
string
integer
{
"detail": [
{
"loc": [
"string",
0
],
"msg": "string",
"type": "string"
}
]
}