Use ZMSCORE to get the scores of several members of a sorted set in one call.
The reply holds one score per member, in the order requested, with null for members that are not in the set, so it lines up with your input list. A missing key yields all nulls rather than an error. It replaces a series of ZSCORE round trips when you need to read a batch of scores, such as the current rating of every item on a page.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<member> | Yes | Yes | Member name. |
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 bulk-string scores or null values, one per member |
| RESP3 | Array of double scores or null values, one per member |
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.