Use RPUSH to add one or more elements to the tail of a list, creating the list when the key does not exist.
Elements are appended in the order given, so RPUSH key a b c leaves the list as a, b, c. The reply is the length of the list after the push, and a key holding another type returns an error.
Appending with RPUSH and consuming from the head with LPOP is the standard first-in, first-out queue, and it is the form most job queues use because the natural reading order with LRANGE then matches the order of insertion.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<element> | Yes | Yes | Element to push. |
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 | Integer |
| RESP3 | Integer |
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.