Linear's GraphQL API provides programmatic access to the full project management workflow. Master the node/connection pagination model, issues, cycles, teams, webhooks, and the TypeScript SDK for building integrations and automating engineering workflows.
0 / 5 completed
1 / 5
A developer queries the Linear GraphQL API with { issues { nodes { id title state { name } } } }. What does the nodes field represent in Linear's API pattern?
Linear's GraphQL API uses a connection/node pattern for paginated collections. A connection type (e.g., IssueConnection) contains nodes (the current page of items) and pageInfo (cursor pagination info). This follows the Relay specification for cursor-based pagination in GraphQL.
2 / 5
A team uses Linear cycles in their engineering workflow. What is a cycle in Linear's terminology?
A Linear cycle is Linear's term for a sprint — a time-boxed work period with defined start/end dates. Teams add issues to cycles to plan iterations. The Linear API's cycle and cycles queries expose cycle details including issue assignments and completion metrics.
3 / 5
A developer uses the @linear/sdk TypeScript SDK to create an issue: await linearClient.createIssue({ teamId, title, labelIds }). What does the teamId parameter require?
In Linear, issues belong to teams — organizational units that own projects, workflows, and issue states. The teamId in createIssue must be a valid Linear team UUID. Each team has its own issue number sequence, states, and labels, so the team determines the issue's workflow and identifier prefix.
4 / 5
A Linear webhook is configured for the Issue resource type. What triggers a webhook event delivery?
Linear webhooks deliver POST requests to your endpoint when subscribed resources change. For the Issue resource type, events fire on issue creation, updates (title, state, assignee, priority, labels), and deletion. The payload includes the action type, entity data, and webhook signatures for verification.
5 / 5
A query to the Linear API uses after: "cursor123" in the variables. What pagination style does Linear's GraphQL API use?
Linear's API uses cursor-based pagination following the GraphQL Relay specification. The after parameter accepts an opaque cursor string from the previous response's pageInfo.endCursor. This approach is stable under concurrent writes (unlike offset pagination) and is suitable for large, frequently updated datasets.