---
title: Keeper  API Integration on Truto
slug: keeper
category: Default
canonical: "https://truto.one/integrations/detail/keeper/"
---

# Keeper  API Integration on Truto



**Category:** Default  
**Status:** Generally available

## Unified APIs

### Unified User Directory API

- **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams.
- **Users** — The User object represents a User.

## How it works

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

- **Sync Keeper Teams and Users for Automated Access Control** — SaaS companies can pull user and group data from their customers' Keeper environments to automatically assign roles, permissions, and workspace access — eliminating manual user management and reducing provisioning errors.
- **Detect Offboarded Users and Revoke Access in Real Time** — By continuously syncing user status from Keeper's directory, B2B apps can immediately terminate sessions and revoke permissions when a customer's employee or contractor is deactivated, closing security gaps during offboarding.
- **Map Keeper Group Structures to Product Workspaces** — SaaS platforms serving enterprise customers can read Keeper Teams (Groups) to automatically organize users into the correct projects, channels, or permission tiers — so end users never have to manually configure team mappings.
- **Streamline IT Onboarding Workflows with Directory Data** — IT automation and HR platforms can detect new users and group assignments in Keeper to trigger downstream provisioning workflows like license allocation, device ordering, or training enrollment without manual intervention.

## What you can build

- **Auto-Provisioned User Accounts from Keeper Directory** — Automatically create and configure user accounts in your product when new users appear in a customer's Keeper environment, mapped to the correct roles based on their Keeper group membership.
- **Real-Time Offboarding and Session Termination** — Instantly detect when a user is suspended or removed in Keeper and automatically revoke their active sessions and data access in your application.
- **Group-Based Permission Mapping** — Let customers define permission rules that map Keeper Teams to specific feature access levels or workspaces inside your product, keeping authorization in sync without manual updates.
- **User Directory Dashboard for Admins** — Surface a live view of all synced Keeper users and groups inside your admin console so customer IT admins can verify that directory data is accurate and up to date.
- **Automated License Usage Reporting** — Track the number of active Keeper users synced into your platform to generate accurate license utilization reports for billing or compliance purposes.

## FAQs

### What data can I access from Keeper through Truto?

Truto's Unified User Directory API provides access to Users and Groups from Keeper. This lets you read user profiles (names, emails, status) and group/team structures for directory syncing and access control workflows.

### Are there pre-built Truto tools for Keeper, or is it built on request?

Keeper integration tools are built on request. Once you reach out, Truto will build and configure the connector for your specific use case, handling authentication, pagination, and API-specific quirks on your behalf.

### How does authentication work for the Keeper integration?

Truto manages the full auth flow for your end users connecting their Keeper accounts. The specific auth method (API key, OAuth, or admin credentials) is configured during the connector build process so your team doesn't need to implement it directly.

### Can I write data back to Keeper, or is it read-only?

The Unified User Directory API focuses on reading Users and Groups. Write operations depend on what Keeper's APIs support and what is configured during the on-request build. Contact Truto to discuss specific write requirements like user provisioning or group updates.

### How does Truto handle Keeper's zero-knowledge encryption model?

Truto integrates at the administrative and directory layer — syncing user and group metadata — rather than accessing encrypted vault contents. This means the integration respects Keeper's zero-knowledge architecture while still providing the directory data your application needs.

### What Unified APIs does the Keeper integration support?

Keeper is supported under Truto's Unified User Directory API, which standardizes access to Users and Groups across identity providers. This means you can use the same API schema to read Keeper directory data as you would for any other supported identity platform.
