Prefer ZRANGE with BYSCORE and REV in new code: ZRANGE <key> <max> <min> BYSCORE REV [LIMIT <offset> <count>] [WITHSCORES].
Use ZREVRANGEBYSCORE to list the members in a score range, ordered from the highest score down.
The bounds are given highest first, <max> before <min>. They are inclusive by default, become exclusive when prefixed with (, and accept +inf and -inf. WITHSCORES returns the scores and LIMIT <offset> <count> pages through the result, which is the usual way to fetch "the top N above a threshold".
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<max> | Yes | No | Maximum score: a number, +inf, or (score for an exclusive bound. |
<min> | Yes | No | Minimum score: a number, -inf, or (score for an exclusive bound. |
WITHSCORES | No | No | Include sorted-set scores. |
LIMIT <offset> <count> | No | No | Skip <offset> matches and return at most <count>; a <count> of -1 returns all remaining. |
Important points#
- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
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 members, or flat member/score array with WITHSCORES |
| RESP3 | Array of members, or array of member/score pairs with WITHSCORES |
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
This command is not supported yet in @upstash/redis.