--- title: Linear API Integration on Truto slug: linear category: Ticketing canonical: "https://truto.one/integrations/detail/linear/" --- # Linear API Integration on Truto **Category:** Ticketing **Status:** Generally available ## Unified APIs ### Unified User Directory API - **Me** — - **Users** — The User object represents a User. ### Unified Ticketing API - **Attachments** — Attachments are the files associated with a ticket or a comment. - **Collections** — Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. You can differentiate between these grouping systems using the type attribute of a Collection. - **Comments** — Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments. - **Tags** — Tags represent a common classification approach used in various ticketing systems. A Ticket may have one or more Tags associated with them. - **Teams** — Teams represent the grouping system used for Users. These are usually called groups, teams, agent groups, etc. in the underlying products. A User can belong to one or more Teams. - **Ticket Status** — Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **Users** — Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc. ### Unified Search API - **Search** — Search endpoint for all the apps. ## How it works 1. **Link your customer's Linear 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 Linear.** The Proxy API is a 1-to-1 mapping of the Linear 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 - **Escalate customer issues directly to engineering** — Support and helpdesk platforms can let agents create Linear issues from bug reports without leaving their tool. Truto handles the ticket creation, attachment uploads, and bi-directional status sync so the support team knows when engineering has shipped the fix. - **Sync product feedback to engineering backlogs** — Product feedback and roadmapping platforms can link feature requests to Linear tickets, pull project and cycle data, and sync status changes back — giving product managers and customer-facing teams real-time visibility into engineering progress. - **Auto-create tickets from failed tests or alerts** — QA, testing, and monitoring tools can search Linear for existing issues, create new tickets with the right team, labels, and priority when something breaks, and attach logs or recordings — all without manual engineering triage. - **Track engineering dependencies in sales and CRM workflows** — CRM platforms can let reps link deals to Linear tickets blocking a sale, monitor ticket status changes, and trigger automated alerts when a feature ships — turning engineering velocity into closed revenue. - **Centralize ticket visibility across multiple tools** — Operations and workflow platforms can aggregate Linear tickets alongside issues from other ticketing systems using Truto's Unified Ticketing API, giving teams a single pane of glass without building separate integrations for each tool. ## What you can build - **Two-way ticket status sync** — Keep ticket states synchronized between your platform and Linear so that when an engineer marks an issue as completed, your product reflects the change automatically. - **One-click issue escalation from support UI** — Let support agents create Linear tickets pre-filled with conversation context, screenshots as attachments, and the correct team assignment — without switching tools. - **Cross-platform comment threading** — Push comments from your product into Linear issues and pull Linear comments back, so engineers and non-technical stakeholders stay aligned without context switching. - **Duplicate issue detection before creation** — Use the Unified Search API to check whether a Linear issue already exists for a given problem before creating a new ticket, reducing backlog noise. - **Automated ticket routing with labels and team assignment** — Create tickets in the correct Linear team's triage queue, apply tags like 'Bug' or 'Feature Request', and set priority levels programmatically based on your product's business logic. - **Project and cycle progress dashboard** — Pull Linear collections data — projects and cycles — into your product so users can visualize sprint progress and release timelines alongside their own workflows. ## FAQs ### What authentication method does the Linear integration use? Linear supports OAuth 2.0 for user-level authentication. Truto manages the full OAuth flow, token storage, and refresh cycle so your end users can connect their Linear workspace securely without you handling credentials. ### Which Unified APIs does Truto support for Linear? Linear is supported through the Unified Ticketing API (Tickets, Ticket Status, Comments, Attachments, Collections, Tags, Teams, Users), the Unified User Directory API (Me, Users), and the Unified Search API (Search). ### How does Linear's data model map to Truto's Unified Ticketing API? Linear Issues map to Tickets, Workflow States to Ticket Status, Labels to Tags, Projects and Cycles to Collections, and Linear Teams and Users map directly to their Truto counterparts. Comments and Attachments map one-to-one. ### Does Linear have API rate limits I should worry about? Yes, Linear's API enforces rate limits on its GraphQL endpoint. Truto handles pagination and request management under the hood, but for high-volume syncs you should design around reasonable polling intervals or rely on webhook-driven updates where possible. ### Can I create tickets with custom fields or specific priorities via Truto? Truto's Unified Ticketing API supports standard fields like title, description, priority, assignee, team, labels, and status. If you need specific custom field support or additional operations beyond what the unified model covers, Truto can build tailored tools on request. ### What if I need a capability that isn't covered by the Unified APIs? Linear has no pre-built Truto tools yet, but tools are built on request. If you need access to Linear-specific features like SLA tracking, relations, or custom views, reach out to Truto and they will build the tooling for your use case.