--- title: LaunchDarkly API Integration on Truto slug: launchdarkly category: Default canonical: "https://truto.one/integrations/detail/launchdarkly/" --- # LaunchDarkly 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. - **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 LaunchDarkly 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 LaunchDarkly.** The Proxy API is a 1-to-1 mapping of the LaunchDarkly 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 - **Automate developer onboarding and RBAC provisioning** — Internal developer platforms and IT automation tools can provision new engineers into LaunchDarkly, assign them to the correct Teams, and grant environment-scoped custom roles — all without manual setup. This ensures consistent access governance across engineering organizations. - **Centralize identity and access management across DevOps tools** — Security and compliance platforms can pull LaunchDarkly account members, team memberships, and role assignments into a unified view alongside other tools. This enables access reviews, license auditing, and SOC 2 compliance reporting without custom API work. - **Sync organizational structure for scoped feature flag governance** — Workforce management and IDP platforms can keep LaunchDarkly Teams and Roles in sync with upstream identity providers, ensuring that when an engineer moves teams or leaves the company, their LaunchDarkly permissions update automatically. - **Power entitlement-aware user provisioning from billing platforms** — Billing and subscription management tools can map customer tiers to LaunchDarkly roles and team memberships, so that when a customer upgrades their plan, the right people get the right level of access to flag management capabilities. ## What you can build - **Automated LaunchDarkly user provisioning** — Provision and deprovision LaunchDarkly account members automatically when employees join or leave, using Truto's Unified User Directory API. - **Team membership sync** — Keep LaunchDarkly Teams in sync with your product's group or team model, ensuring engineers are always assigned to the correct feature flag governance boundaries. - **Custom role assignment on onboarding** — Automatically assign LaunchDarkly custom roles (e.g., Writer scoped to Staging) during user provisioning based on team, seniority, or project affiliation. - **Cross-tool access review dashboard** — Pull LaunchDarkly users, groups, and roles into a unified access review interface alongside other connected tools to streamline compliance audits. - **Offboarding access revocation** — Automatically remove LaunchDarkly account members and strip role assignments when an employee is offboarded from your HR or identity system. ## FAQs ### What authentication method does the LaunchDarkly integration use? LaunchDarkly supports API access tokens (personal and service tokens) for REST API authentication. Enterprise plans also support SCIM provisioning via bearer tokens. Truto handles token management and auth flows so your end users can connect their LaunchDarkly accounts securely. ### What data can I access through the Unified User Directory API for LaunchDarkly? The Unified User Directory API maps to LaunchDarkly's Account Members (Users), Teams (Groups), and Custom Roles (Roles). This covers the internal users who manage feature flags — not the end-user Contexts that evaluate flags in applications. ### Are there rate limits on the LaunchDarkly API? Yes, LaunchDarkly enforces rate limits on its REST API, typically returning HTTP 429 responses when limits are exceeded. Truto handles rate limiting, retries, and backoff automatically so your integration remains reliable without custom retry logic. ### Can I access feature flags, environments, or targeting rules through this integration? The current Unified API coverage focuses on User Directory resources (Users, Groups, Roles). Feature flags, environments, and targeting rules are available in LaunchDarkly's API and can be supported through Truto's custom tooling — built on request to match your specific workflow needs. ### Does the integration support write operations like creating users or assigning roles? Truto's Unified User Directory API is designed to support both read and write operations. The exact supported operations for LaunchDarkly are configured when the integration is built. Contact Truto to confirm specific write capabilities for your use case. ### What's the difference between LaunchDarkly Account Members and Contexts? Account Members are the internal employees (engineers, PMs) who log into LaunchDarkly to manage flags. Contexts are the end-users, devices, or tenants whose attributes are evaluated by feature flags at runtime. The Unified User Directory API maps to Account Members, not Contexts.