Skip to main content
Use EXPIREAT to schedule a key for automatic deletion at a fixed point in time, given as a Unix timestamp in seconds. It behaves exactly like EXPIRE except that the deadline is absolute rather than relative, which is what you want when several keys must expire at the same moment, such as the end of an hour or of a billing period. Computing the deadline once and reusing it also avoids the drift that repeated relative expirations introduce. A timestamp in the past deletes the key right away. The optional condition works as it does for EXPIRE: NX only when the key has no expiration, XX only when it already has one, GT only when the new deadline is later than the current one, and LT only when it is earlier.

Syntax

Arguments

Important points

  • NX cannot be combined with XX, GT, or LT, and GT and LT cannot be used together.
  • A key with no expiration counts as an infinite one, so GT never sets an expiration on such a key 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.

Related topics

EXPIREATOverview