Use HPEXPIRETIME to read the absolute expiration time of hash fields, as Unix timestamps in milliseconds.
The reply holds one value per requested field, in order: the timestamp at which it expires, -1 when the field exists but has no expiration, and -2 when the field or the key does not exist. It is the millisecond form of HEXPIRETIME and reports a deadline rather than the time left, which is the value to compare against a clock.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
FIELDS <numfields> <field> [<field> ...] | Yes | No | Fields to target. Give the field count first, then that many field names. |
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 | Array of expiration timestamps or negative integer status codes, one per field |
| RESP3 | Array of expiration timestamps or negative integer status codes, one per field |
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.