Get Notifications Page
GET/notification/v1/player/:player_uuid/notification
Get recent notifications ordered from the newest to the oldest.
It is important to stress that this endpoint returns notifications in reverse order compared to the streaming API. The first notification returned from this will be the newest one we can find, and older ones will be further down the page (or on later pages).
This API is useful for displaying a list of the most recent notifications to the user, only requesting further pages when the user requests a bigger list.
Client are expected to poll this endpoint regularly.
This version can be used for any client provided its id (with proper permissions)
Required Permissions:
-
For any player (including themselves) any of:
notification:player:*,notification:player:read -
For the player themselves any of:
notification:player:self:*,notification:player:self:read
Request
Path Parameters
Query Parameters
Possible values: >= 1 and <= 100
Default value: 10
Return results starting at this index (inclusive). If none provided then will start at the latest notification. You cannot depend on the format of this string, and it must be considered opaque
All notifications including and before this (chronologically) provided id will be ignored when returning results. You cannot depend on the format of this string, and it must be considered opaque
Header Parameters
If you provide the ETag that matches the current ETag for this content, will return a 304 response - indicating that the content has not changed
Responses
- 200
- 304
- 400
- 403
- 409
- 422
- 503
Successful Response
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
notifications
object[]
List of notifications
Possible values: <= 4096 characters
Base Message for the notification
Possible values: non-empty and <= 4096 characters
Path to get additional data about this notification
custom_data
object
Custom values for the notification
Possible values: non-empty
ETag for the resource at rh_url at the time of this notification
Unique Identifier for the notification. You cannot depend on the format of this string, and it must be considered opaque
When this notification was added
Cursor to use for the next request
{
"notifications": [
{
"message": "string",
"rh_url": "string",
"custom_data": {},
"etag": "string",
"notification_id": "string",
"created": "2024-07-29T15:51:28.071Z"
}
],
"cursor": "string"
}
Not Modified
Error Codes:
-
bad_id- Passed client id is not a valid id
- 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:
-
too_many_listening_to_single_client- An enumeration.
- application/json
- Schema
- Example (from schema)
Schema
Default value: true
{
"auth_success": true,
"error_code": "string",
"desc": "string"
}
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"
}
]
}
Error Codes:
-
connection_limit_reached- An enumeration.
- application/json
- Schema
- Example (from schema)
Schema
Default value: true
{
"auth_success": true,
"error_code": "string",
"desc": "string"
}