Skip to main content
Use HPEXPIRE to give individual hash fields a lifetime in milliseconds, after which those fields are removed from the hash. It is the millisecond form of HEXPIRE and behaves identically otherwise: expiration is per field, the hash survives as long as it has fields, and the key disappears when the last field expires. The finer precision matters for short-lived fields such as per-field locks or rate limit windows. FIELDS <numfields> introduces the field list and the count must match. The optional condition applies the new lifetime only in certain cases: NX when the field has no expiration, XX when it already has one, GT when the new expiration is later than the current one, and LT when it is earlier. The reply holds one status code per field: 1 when set, 0 when the condition prevented it, 2 when the field was deleted immediately, and -2 when it does not exist.

Syntax

Arguments

Important points

  • NX cannot be combined with XX, GT, or LT, and GT and LT cannot be used together.
  • A field with no expiration counts as an infinite one, so GT never sets an expiration on such a field and LT always does.

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.
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.