Use TTL to read how much longer a key will live, in seconds.
The reply is -1 when the key exists but has no expiration and -2 when the key does not exist, so these two are never confused with a real remaining lifetime. Values are rounded to whole seconds; use PTTL for millisecond precision and EXPIRETIME when you want the absolute deadline rather than the time left.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
Important points#
- Negative integer replies are sentinel values, not durations or timestamps; see the response description for missing or persistent data.
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Integer: remaining lifetime in seconds, -1 if the key has no expiration, -2 if the key does not exist |
| RESP3 | Integer: remaining lifetime in seconds, -1 if the key has no expiration, -2 if the key does not exist |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.