PPlatformAppStores

Linear Integration Directory

Workspace

Linear · Productivity & collaboration suites

Best for: Formal companies building OAuth- or API-based workflow, collaboration, engineering, analytics, support, or AI-agent integrations for Linear workspaces.

Overview

Linear’s Integration Directory lists apps and add-ons created by Linear and external developers. It organizes integrations across engineering, automation, customer experience, analytics, collaboration, security and compliance, bug reporting, media and design, agents, and AI clients. Developers can build integrations with Linear’s GraphQL API and TypeScript SDK, authenticate with OAuth 2.0 or API keys, and submit qualifying applications for directory consideration. Linear generally accepts useful integrations built by formal companies; scripts, low-effort applications, and hobbyist applications are generally not accepted.

How to build & ship

  1. 1Review Linear’s developer documentation and select the required API, SDK, authentication, and platform surfaces.
  2. 2Create an OAuth 2.0 application, configure callback URLs, request necessary scopes, and use an API key where appropriate.
  3. 3Build against Linear’s GraphQL API, optionally using the TypeScript SDK, webhooks, filtering, pagination, and attachments.
  4. 4Prepare a 320×320 color icon, a 320×320 monochrome icon, and one to three 1600×1000 showcase images in accepted formats.
  5. 5Submit Linear’s form and assets, then await directory review and acceptance.

Key APIs & SDKs

GraphQL API
TypeScript SDK
OAuth 2.0
Webhooks
MCP and agent surfaces

Integration types

Connector
Workflow action
Bot

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: Personal API keys, Client-credentials OAuth tokens for server-to-server applications
  • Security review: Not publicly specified
  • A separate security-review requirement is not publicly specified; directory review and acceptance are required for submission.
  • Complete Linear’s submission form, provide the requested icon and showcase assets, and await Linear’s evaluation for usefulness and directory suitability; contact integrations@linear.app for questions or asset submission.
  • Global GraphQL limits are 2,500 requests/hour for API keys, 5,000 requests/hour for OAuth apps, and 600 requests/hour for unauthenticated requests; a maximum single-query complexity of 10,000 points and endpoint-specific limits also apply.
Auth docs Store policies

Monetization

Onboarding
Not publicly specified
Commission
Not publicly specified
Merchant of Record
Not publicly specified

Pros & cons for builders

Pros

  • Broad official surface across engineering, collaboration, customer experience, analytics, automation, and AI.
  • Documented GraphQL, OAuth 2.0, TypeScript SDK, webhook, rate-limit, and agent surfaces.
  • Established submission path with specified form, asset requirements, and acceptance criteria.

Cons

  • Directory acceptance is discretionary.
  • Linear generally prefers formal-company integrations over scripts, low-effort applications, and hobbyist apps.
  • Public commercial terms are not specified.

Frequently asked questions

How do I get my app approved on Linear Integration Directory?

Complete Linear’s submission form, provide the requested icon and showcase assets, and await Linear’s evaluation for usefulness and directory suitability; contact integrations@linear.app for questions or asset submission.

What authentication does Linear Integration Directory use?

Linear Integration Directory apps primarily authenticate with OAuth 2.0, also supporting Personal API keys, Client-credentials OAuth tokens for server-to-server applications.

How is Linear Integration Directory monetized?

Linear Integration Directory supports not publicly specified monetization. Typical commission: Not publicly specified. Onboarding fee: Not publicly specified.

Is a security review required to list on Linear Integration Directory?

Linear Integration Directory's public materials do not specify a universal security-review requirement. A separate security-review requirement is not publicly specified; directory review and acceptance are required for submission.