---
title: Confluent API Integration on Truto
slug: confluent
category: Application Development
canonical: "https://truto.one/integrations/detail/confluent/"
---

# Confluent API Integration on Truto



**Category:** Application Development  
**Status:** Generally available

## Unified APIs

### Unified User Directory API

- **Organizations** — Organizations are the top level entity in the source application. Users are associated with an organization.
- **Roles** — The Role object represents a role of a User.
- **Users** — The User object represents a User.

### Unified Usage Metering API

- **Organizations** — Represents the organizations that are using the products.
- **Products** — Products represent the services or products that are being used by the organization for a particular integration.
- **Usage** — Returns the usage data across products for the organization.
- **Workspaces** — 

## How it works

1. **Link your customer's Confluent 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 Confluent.** The Proxy API is a 1-to-1 mapping of the Confluent 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

- **Audit Confluent access and permissions for security compliance** — Security and compliance SaaS platforms can pull service accounts, users, and role bindings from a customer's Confluent Cloud environment to detect misconfigurations, overly permissive API keys, or dormant accounts — all through Truto's Unified User Directory API.
- **Track Confluent Cloud spend across environments** — Cloud FinOps and cost observability tools can aggregate usage and billing data across a customer's Confluent environments and clusters, helping teams understand which workloads drive networking, storage, and compute costs using Truto's Unified Usage Metering API.
- **Centralize identity management across streaming infrastructure** — Identity governance and administration (IGA) platforms can include Confluent alongside other SaaS tools in a unified view of who has access to what, by syncing Confluent users, service accounts, and role assignments into their product.
- **Automate infrastructure inventory for data platform teams** — Internal developer platforms and infrastructure management tools can offer customers a live view of their Confluent organizations, environments, and cluster topology — enabling self-service governance without requiring teams to log into the Confluent console.

## What you can build

- **Confluent service account access review dashboard** — Surface all Confluent service accounts and their role bindings so security teams can identify unused or overly permissive credentials in one view.
- **Cross-environment usage breakdown** — Show Confluent Cloud usage metrics broken down by organization, environment, and cluster so FinOps teams can attribute streaming costs to specific teams or projects.
- **Unified user directory with Confluent RBAC** — Include Confluent users and roles alongside other connected apps in a single identity governance interface for access reviews and compliance reporting.
- **Confluent organization and workspace mapper** — Automatically map Confluent organizations and environments into your product's workspace model, giving customers a normalized view of their streaming infrastructure.
- **Dormant API key detection alerts** — Flag Confluent API keys tied to service accounts with no recent activity, helping customers reduce their attack surface proactively.

## FAQs

### How does authentication work for Confluent integrations?



### Which Confluent APIs does Truto map to?

Truto maps Confluent's Identity and Access Management (IAM) APIs to the Unified User Directory API (Organizations, Roles, Users) and Confluent's billing and metrics endpoints to the Unified Usage Metering API (Organizations, Products, Usage, Workspaces). Specific tools are built on request based on your requirements.

### Can I read or write data to Confluent topics through Truto?

Truto's current Unified APIs for Confluent focus on the control plane — user directory and usage metering. Data plane operations like producing or consuming messages from topics are not covered by the existing Unified APIs but can be discussed as a custom integration request.

### Does Truto handle Confluent API rate limits and pagination?

Yes. Truto abstracts away pagination and rate limit handling for Confluent's Cloud API, so you don't need to implement retry logic or cursor management in your application code.

### What data can I pull from Confluent's user directory?

Through the Unified User Directory API, you can retrieve Confluent users, service accounts, and their associated role bindings at the organization level. This is useful for security audits, compliance checks, and identity governance workflows.

### Are Confluent tools available out of the box or built on request?

Confluent tools are currently built on request. Truto's team will work with you to scope the specific endpoints and data models you need, mapped to the Unified User Directory and Unified Usage Metering APIs.
