Subscribe to the 'map obsolescence' event.
GET/maps/events/obsoleted
This endpoint allows clients to subscribe to server-sent events (SSE) that notify them when any map in the inventory has become obsolete. Additionally, the endpoint sends an event if the check against the server fails. The response includes information about any obsoleted maps and any errors encountered during the check.
Warning: Only maps that are both obsoleted and in a "Ready" (fully downloaded) state will be included. Maps that are obsoleted but not fully downloaded or are waiting for deletion will not be considered as obsoleted by this event.
Request
Responses
- 200
- application/json
- Schema
- Example (from schema)
Schema
-
typeis the specific error type (e.g.,ClientError,InternalServerError). -
msgis the associated error message (a string). - MOD1
- MOD2
- MOD3
- MOD4
- MOD5
- MOD6
- MOD7
- MOD8
- MOD9
- MOD10
- MOD11
- MOD12
- MOD13
- MOD14
- MOD15
- MOD16
error
object
nullable
Represents various types of errors that can occur in the application.
When serialized, it will be represented in the following format:
{
"type": "ErrorType",
"msg": "ErrorMessage"
}
Where:
oneOf
Possible values: [ClientError]
Possible values: [InternetConnectionError]
Possible values: [UnauthorizedError]
Possible values: [InternalServerError]
Possible values: [MissingDataError]
Possible values: [ParsingFailedError]
Possible values: [WritingDataError]
Possible values: [ForbiddenError]
Possible values: [NotAllowedError]
Possible values: [ValidationError]
Possible values: [SQLError]
Possible values: [StorageLimitExceededError]
Possible values: [StorageUnavailable]
Possible values: [ConflictError]
Possible values: [MatomoError]
Possible values: [ProcessInterrupted]
The last time the inventory was checked against the server to determine if there are any obsolete maps.
Indicates whether there is any map in the inventory that is obsoleted.
{
"error": {
"msg": "string",
"type": "ClientError"
},
"lastCheck": "2026-01-01T11:09:06.000Z",
"obsoleted": true
}