Skip to main content
Use HELLO to negotiate the protocol version of the connection and read the server handshake information. Passing <protover> switches the connection to RESP2 or RESP3. RESP3 adds native map, set, double, and push replies, so commands such as HGETALL or CONFIG GET come back as maps instead of flat arrays, and pub/sub messages arrive as push replies that do not block ordinary commands. AUTH authenticates in the same call and SETNAME names the connection, which lets a client complete its handshake in one round trip. Called without arguments, HELLO only reports the server version, the protocol in use, the connection id, and the current role, leaving the protocol unchanged.

Syntax

Arguments

Important points

  • This is a connection-oriented command and is available over native Redis TCP, not the stateless REST endpoint.

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.