GetUserTimestamps
Jump to navigation
Jump to search
Description
Returns different timestamps for each user info Currently only Recordings Timestamp is fully working, the rest of then CAN NOT be used
Devices should cache recordings info based on this timestamp, while it is not modified, the users recordings from cache are valid
This method should be consumed through one of these approach:
- Action based: When a action is performed from the devices and it may show recordings info: Access to EPG, Recordings section, etc.
- Pol-ing in background each X minutes (configurable parameter required). The minimum recommended time for now is 5 mins.
This method only can be used by logged user.
When does values change:
- Pins (TO BE DONE)
- Recordings
- Cache time expires (Config, or because a Recording changes its state)
- New recording Added
- Recording Cancelation
- Recording Deletion
- Recording protection
- Rights (TO BE DONE)
- Services (TO BE DONE)
- Tags (TO BE DONE)
Parameters
- token (String, required)
- A valid token for identifying the API session context. The token can be anonymous or logged.
Returns
Returns a JSON object containning different timestamps
Example:
{
- "StatusCode": 0,
- "Severity": 1,
- "StatusMessage": "OK",
- "Content": {
- "Pins": 1574415643,
- "Recordings": 1574674243,
- "Rights": 1609459206,
- "Services": 1574415643,
- "Tags": 1574415643,
- }
}
Exceptions
- None
Caching
This method is not cached.
Known issues
- None
Version history
API Version Number | Change description | Changes author |
---|---|---|
7.1.drop2 | Initial method design | José Manuel Escartín |