--- title: Height API Integration on Truto slug: height category: Ticketing canonical: "https://truto.one/integrations/detail/height/" --- # Height API Integration on Truto **Category:** Ticketing **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. - **Workspaces** — Workspaces represent concepts like teams, workspaces, projects in apps that support them ## How it works 1. **Link your customer's Height 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 Height.** The Proxy API is a 1-to-1 mapping of the Height 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 Height workspace members into your user directory** — If your product manages user identities or access controls, you could pull Height Users, Groups, and Workspaces via Truto's Unified User Directory API to keep your directory in sync with your customers' Height accounts. - **Map Height users to assignees in external systems** — SaaS platforms that orchestrate work across multiple tools need a canonical user list. Syncing Height Users through Truto allowed your product to reliably map ticket assignees, reviewers, and owners against identities in systems like Slack, Okta, or your own app. - **Migrate and archive Height user and workspace data** — Since Height shut down in September 2025, teams that stored historical Height data need to extract Users, Groups, and Workspace metadata for migration to surviving platforms. Truto's Unified User Directory API provides a consistent schema for this extraction. ## What you can build - **User identity sync from Height workspaces** — Automatically import Height Users and Groups into your product's internal directory so downstream features like assignment, notifications, and access control stay accurate. - **Workspace discovery and mapping** — Let your end users connect their Height account and browse available Workspaces so your product can scope data access to the correct organizational boundary. - **Group-based permission mirroring** — Read Height Groups via Truto and mirror those membership structures into your own role or permission model, reducing manual setup for your customers. - **Historical user data export for post-shutdown migration** — Offer your customers a one-click extraction of their Height Users, Groups, and Workspace metadata into a normalized format they can re-import into Linear, Shortcut, or another active tool. ## FAQs ### Is the Height API still available? No. Height officially shut down on September 24, 2025, and its APIs are permanently offline. Any existing integrations should be treated as deprecated. Truto retains the integration definition for historical reference and data migration scenarios where cached data may still be accessible. ### What Unified APIs does Truto support for Height? Truto supports the Unified User Directory API for Height, which covers Users, Groups, and Workspaces. Ticketing-specific tools (Tasks, Comments, Lists) are not currently available but can be built on request. ### What authentication method did Height use? Height supported OAuth 2.0 and API key-based authentication. Truto managed the auth flow so your end users could connect their Height accounts without your team handling token exchange or refresh logic. ### Can Truto help build ticketing integrations modeled on Height's data structure? Yes. While Height itself is offline, its data model — cascading sub-tasks, chat-centric comments, custom attributes, and list-based organization — is a useful reference for Truto's Unified Ticketing API. If you need ticketing tools built for Height-like patterns on other platforms, Truto can build them on request. ### Should I build a new Height integration today? No. Since Height is permanently shut down, new integrations will not function. If you have existing customers with historical Height data they need extracted, Truto can assist with migration tooling. For active ticketing integrations, consider connecting to Linear, Shortcut, or similar platforms through Truto. ### Are there rate limits or pagination concerns for the Height integration? Height's API historically enforced rate limits and paginated list responses. Truto handled pagination and rate-limit retries automatically. Since the API is now offline, these constraints are no longer relevant for new requests.