Upstash Documentation

HEXPIRETIME

Get field expiry as timestamp.
2 min read

Use HEXPIRETIME to read the absolute expiration time of hash fields, as Unix timestamps in seconds.

The reply holds one value per requested field, in order: the timestamp when the field expires, -1 when the field exists but has no expiration, and -2 when the field or the key does not exist. Use HTTL when you want the remaining lifetime instead of the deadline, and HPEXPIRETIME for millisecond precision.

Syntax#

Arguments#

ArgumentRequiredRepeatableDescription
<key>YesNoRedis key targeted by the command.
FIELDS <numfields> <field> [<field> ...]YesNoFields 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.

ProtocolReply
RESP2Array of expiration timestamps or negative integer status codes, one per field
RESP3Array of expiration timestamps or negative integer status codes, one per field
Note

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.

Redis CLI
@upstash/redis
upstash_redis
ioredis
node-redis
redis-py
go-redis
jedis
redis-rs