Skip to content

Serverless Redis

Serverless Redis exposes Redis-compatible commands through an HTTPS API. It is intended for lightweight application storage, automation, and service integrations that prefer HTTP access over a raw Redis TCP connection.

The service supports Upstash-compatible HTTP access patterns.

Access control

Requests require a bearer token:

1
Authorization: Bearer <token>

Replace <token> with the issued access token. If you need a token, contact dev@intellij.io.

Do not commit tokens to source control or share them in logs.

Endpoints

All public endpoints require HTTPS.

Domain Protocol Notes
redis.websocket.cn HTTPS General Redis-compatible HTTP endpoint
upstash.websocket.cn HTTPS Upstash-compatible HTTP endpoint
valkey.websocket.cn HTTPS Valkey-compatible HTTP endpoint

Example base URL:

1
https://redis.websocket.cn

Request format

The HTTP interface is compatible with Upstash Redis REST access patterns. Use the same request structure, headers, and command payload format as Upstash-compatible clients.

Examples

Ping the hosted endpoint

1
2
3
4
curl -i -X POST https://redis.websocket.cn \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '["PING"]'

Compatibility notes

  • The service supports Upstash-compatible HTTP access patterns.
  • Use HTTPS for all public domains.
  • Use the bearer token on every request.
  • Prefer short-lived keys or explicit expiration commands such as EXPIRE when storing temporary data.

Troubleshooting

Symptom Check
401 or 403 response Confirm the bearer token is present, valid, and not expired
400 response Confirm the request body follows the Upstash-compatible request format
Connection failure Confirm the domain uses HTTPS and the endpoint is reachable
Unexpected command response Confirm the command is supported by the backend Redis-compatible service

For support or token requests, contact: dev@intellij.io