--- title: Redis API Integration on Truto slug: redis category: Default canonical: "https://truto.one/integrations/detail/redis/" --- # Redis API Integration on Truto **Category:** Default **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Roles** — The Role object represents a role of a User. - **Users** — The User object represents a User. ## How it works 1. **Link your customer's Redis account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Redis.** The Proxy API is a 1-to-1 mapping of the Redis API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Provision scoped Redis access for customer environments** — Identity and access management SaaS products can dynamically create and manage Redis ACL users and roles in their customers' Redis instances. This enables just-in-time, least-privilege access provisioning without customers manually configuring permissions. - **Sync feature flag rules into customer-owned Redis for sub-millisecond evaluation** — Feature flag and experimentation platforms can push flag configurations directly into a customer's Redis, eliminating the latency of external API calls. The customer's backend reads flags locally, enabling real-time feature evaluation at scale. - **Stream high-throughput event data into customer Redis pipelines** — Analytics and CDP platforms can write event streams directly into a customer's Redis Streams instead of sending thousands of HTTP webhooks. This provides a reliable, high-speed ingestion buffer that customers can consume with their own data processing systems. - **Manage session blocklists for instant token revocation** — Authentication SaaS providers can write revoked token IDs into a customer's Redis with automatic TTL-based expiration. The customer's API gateway checks Redis locally, ensuring banned or logged-out users are blocked instantly without calling back to the auth provider. - **Synchronize real-time security rules to customer infrastructure** — Fraud prevention and security SaaS products can continuously sync IP blocklists, risk scores, and detection rules into a customer's Redis. The customer's edge infrastructure checks these sets at line-rate speed for autonomous threat blocking. ## What you can build - **Just-in-time Redis user provisioning** — Automatically create temporary, scoped Redis ACL users with specific key-pattern permissions when engineers request production access, and revoke them when the access window expires. - **Role-based access control sync for Redis instances** — Map your product's permission model to Redis ACL roles, enabling customers to manage Redis access policies directly from your SaaS dashboard using Truto's Unified User Directory API. - **Low-latency configuration push to customer Redis** — Push feature flags, policy rules, or ML model weights directly into a customer's Redis with TTL-based expiration, so their applications evaluate data locally in under a millisecond. - **Real-time event firehose via Redis Streams** — Offer a Redis Streams destination that writes structured event data directly into customer environments, replacing fragile webhook delivery with a durable, high-throughput ingestion buffer. - **Automated Redis user directory audit trail** — Continuously list and monitor Redis users and their assigned roles across customer instances, surfacing permission drift and unauthorized access changes in your compliance dashboard. - **Ephemeral shared state for distributed workflows** — Write and read transient data like distributed locks, rate-limiting counters, or session tokens in a customer's Redis so both your SaaS and their backend operate on the same real-time state. ## FAQs ### What Unified APIs does Truto support for Redis? Truto maps Redis to the Unified User Directory API, which exposes Users and Roles resources. This lets you programmatically manage Redis ACL users and their role assignments through a standardized interface. ### Are there pre-built tools available for Redis on Truto? Redis tools are built on request. Truto works with you to build the specific tools your integration requires — whether that's ACL management commands, key-value operations, Pub/Sub, or Streams — tailored to your use case. ### How does authentication work for connecting to a customer's Redis instance? Redis supports password-based authentication (AUTH command) and ACL-based authentication with username and password. Truto handles credential management securely so your end users can connect their Redis instances without exposing raw credentials in your application code. ### Does this integration work with Redis Cloud, AWS ElastiCache, and self-hosted Redis? Truto can integrate with any Redis deployment that supports the standard Redis protocol (RESP), including Redis Cloud, AWS ElastiCache, Azure Cache for Redis, and self-hosted instances. Specific cloud management API integrations can be scoped during onboarding. ### How does the Unified User Directory API map to Redis concepts? Users map to Redis ACL users created via ACL SETUSER, and Roles map to Redis ACL categories or custom permission sets that scope access to specific commands and key patterns. This lets you manage Redis access control through the same API you use for other directory integrations. ### Can Truto handle Redis-specific quirks like the RESP protocol instead of REST? Yes. Truto abstracts away protocol-level differences so you interact with a consistent API regardless of whether the underlying system uses REST, RESP, or another protocol. Redis command execution is wrapped behind Truto's unified interface.