Linear

Linear (via Apideck)

Access Linear through Apideck's Issue Tracking unified API — one of 6 Issue Tracking connectors that share the same method surface. Code you write here ports to Jira, GitHub, GitLab and 2 other Issue Tracking connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Linear plumbing.

Beta connector. Linear is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.

Quick facts

• Apideck serviceId: linear
• Unified API: Issue Tracking
• Auth type: oauth2
• Status: beta
• Gotchas: page
• Linear docs: https://developers.linear.app
• Homepage: https://linear.app/

When to use this skill

Activate this skill when the user explicitly wants to work with Linear — for example, "create a ticket in Linear" or "comment on an issue in Linear". This skill teaches the agent:

1. Which Apideck unified API covers Linear (Issue Tracking)
2. The correct serviceId to pass on every call (linear)
3. Linear-specific auth and coverage caveats

For the full method surface (parameters, pagination, filtering), use your language SDK skill:

• apideck-node, apideck-python, apideck-dotnet, apideck-java, apideck-go, apideck-php, or apideck-rest

For the raw OpenAPI spec:

• Issue Tracking: https://specs.apideck.com/issue-tracking.yml · API Explorer

Minimal example (TypeScript)

import { Apideck } from "@apideck/unify";

const apideck = new Apideck({
  apiKey: process.env.APIDECK_API_KEY,
  appId: process.env.APIDECK_APP_ID,
  consumerId: "your-consumer-id",
});

// List tickets in Linear
const { data } = await apideck.issueTracking.tickets.list({
  serviceId: "linear",
});

Portable across 6 Issue Tracking connectors

The Apideck Issue Tracking unified API exposes the same methods for every connector in its catalog. Switching from Linear to another Issue Tracking connector is a one-string change — no rewrite, no new SDK.

// Today — Linear
await apideck.issueTracking.tickets.list({ serviceId: "linear" });

// Tomorrow — same code, different connector
await apideck.issueTracking.tickets.list({ serviceId: "jira" });
await apideck.issueTracking.tickets.list({ serviceId: "github" });

This is the compounding advantage of using Apideck over integrating Linear directly: code against the unified Issue Tracking API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.

Linear via Apideck Issue Tracking

Linear is a modern issue tracker for product teams. Apideck maps its Team/Issue model.

Entity mapping

Coverage highlights

• ✅ Team list (collections)
• ✅ Issues (tickets) — create, list, update, delete
• ⚠️ Users, comments, tags — may be partial; verify with coverage endpoint
• ❌ Projects, Cycles, Roadmaps — use Proxy with Linear's GraphQL API

Auth

• Type: OAuth 2.0, managed by Apideck Vault
• Workspace binding: each connection targets one Linear workspace. For multi-workspace scenarios, use the separate linear-multiworkspace connector.
• API: Linear is GraphQL-only upstream; Apideck abstracts this. For raw GraphQL queries use Proxy.

Example: list issues in a team

const { data } = await apideck.issueTracking.collectionTickets.list({
  serviceId: "linear",
  collectionId: "team_abc123",
});

Escape hatch: Proxy API

When an endpoint isn't covered by the Issue Tracking unified API, use Apideck's Proxy to call Linear directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Linear's own API:

curl 'https://unify.apideck.com/proxy' \
  -H "Authorization: Bearer ${APIDECK_API_KEY}" \
  -H "x-apideck-app-id: ${APIDECK_APP_ID}" \
  -H "x-apideck-consumer-id: ${CONSUMER_ID}" \
  -H "x-apideck-service-id: linear" \
  -H "x-apideck-downstream-url: <target endpoint on Linear>" \
  -H "x-apideck-downstream-method: GET"

See Linear's API docs for available endpoints.

Sibling connectors

Other Issue Tracking connectors that share this unified API surface (same method signatures, just change serviceId):

jira (beta), github (beta), gitlab (beta), gitlab-server (beta), linear-multiworkspace (beta).

See also

• Issue Tracking OpenAPI spec · API Explorer
• apideck-connector-coverage — programmatic coverage checks
• apideck-best-practices — architecture, Vault, pagination, error handling
• apideck-node — TypeScript / Node SDK patterns
• Linear official docs