Use SMISMEMBER to check several values for membership in a set in one call.
The reply holds one 1 or 0 per value, in the order given, so it lines up with your input list. A missing key yields all zeros rather than an error. It replaces a series of SISMEMBER round trips, which matters when checking a batch of ids against a blocklist or an entitlement set.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<member> | Yes | Yes | Member name. |
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 integers, one per queried member |
| RESP3 | Array of integers, one per queried 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.