Access Token

Refresh Token

Linear

Issue attachment (e.g. support ticket, pull request).

The time at which the entity was archived. Null if the entity has not been archived.

The time at which the entity was created.

Whether the user account is active or disabled (suspended).

Whether the user is an organization administrator.

[DEPRECATED] Hash for the user to be used in calendar URLs.

A short description of the user, either its title or bio.

The user's display (nick) name. Unique within each organization.

Whether the user is a guest in the workspace and limited to accessing a subset of teams.

Unique hash for the user to be used in invite URLs.

Whether the user is the currently authenticated user.

The last time the user was seen online. If null, the user is currently online.

The emoji to represent the user current status.

A date at which the user current status should be cleared.

Memberships associated with the user. For easier access of the same data, use `teams` query.

The last time at which the entity was meaningfully updated, i.e. for all changes of syncable properties except those
    for which updates should not produce an update to updatedAt (see skipUpdatedAtKeys). This is the same as the creation time if the entity hasn't
    been updated after creation.

The non-Linear user who created the attachment.

An URL to the external user's avatar image.

The external user's display name. Unique within each organization. Can match the display name of an actual user.

The last time the external user was seen interacting with Linear.

Organization the external user belongs to.

Indicates if attachments for the same source application should be grouped in the Linear UI.

The user to whom the issue is assigned to.

The time at which the issue was automatically archived by the auto pruning process.

The time at which the issue was automatically closed by the auto pruning process.

The order of the item in its column on the board.

The bot that created the issue, if applicable.

The time at which the issue was moved into canceled state.

The time at which the issue was moved into completed state.

Returns the number of Attachment resources which are created by customer support ticketing systems (e.g. Zendesk).

The cycle that the issue is associated with.

The issue's description in markdown format.

[Internal] The issue's description as a Prosemirror document.

[Internal] The issue's description content as YJS state.

The estimate of the complexity of the issue..

The users favorite associated with this issue.

History entries associated with the issue.

Issue's human readable identifier (e.g. ENG-123).

Integration type that created this issue, if applicable.

Inverse relations associated with this issue.

Id of the labels associated with this issue.

The last template that was applied to this issue.

Previous identifiers of the issue if it has been moved between teams.

The priority of the issue. 0 = No priority, 1 = Urgent, 2 = High, 3 = Normal, 4 = Low.

The project that the issue is associated with.

The projectMilestone that the issue is associated with.

[Internal] The time at which the issue's SLA will breach.

[Internal] The time at which the issue's SLA began.

The time until an issue will be snoozed in Triage view.

The order of the item in relation to other items in the organization.

The time at which the issue was moved into started state.

The time at which the issue entered triage.

The workflow state that the issue is associated with.

The order of the item in the sub-issue list. Only set if the issue has a parent.

The team that the issue is associated with.

A flag that indicates whether the issue is in the trash bin.

Information about the source which created the attachment.

An accessor helper to source.type, defines the source type of the attachment.

Content for the subtitle line in the Linear attachment widget.

Content for the title line in the Linear attachment widget.

Location of the attachment which is also used as an identifier.

Attachments

[Internal] The comment content as a Prosemirror document.

A url pointing to the avatar representing this bot.

The display name of the external user on behalf of which the bot acted.

The document content that the comment is associated with.

[Internal] The document content as a Prosemirror document.

The document content state as a base64 encoded string.

The document that the content is associated with.

The issue that the content is associated with.

The project that the content is associated with.

The project milestone that the content is associated with.

The time at which the document content was restored from a previous version.

The issue that the comment is associated with.

The parent comment under which the current comment is nested.

The project update that the comment is associated with.

The text that this comment references. Only defined for inline comments.

Emoji reaction summary, grouped by emoji type.

The time the resolvingUser resolved the thread.

[Internal] The content of the project update as a Prosemirror document.

The diff between the current update and the previous one.

The diff between the current update and the previous one, formatted as markdown.

The health of the project at the time of the update.

[Internal] Serialized JSON representing current state of the project properties when posting the project update.

Whether project update diff should be hidden.

The project that the update is associated with.

Comments

A set of issues to be resolved in a specified amount of time.

The time at which the cycle was automatically archived by the auto pruning process.

The completion time of the cycle. If null, the cycle hasn't been completed.

The number of completed issues in the cycle after each day.

The `Float` scalar type represents signed double-precision fractional values as specified by [IEEE 754](https://en.wikipedia.org/wiki/IEEE_floating_point).

Float

The number of completed estimation points after each day.

The number of in progress estimation points after each day.

The total number of issues in the cycle after each day.

The overall progress of the cycle. This is the (completed estimate points + 0.25 * in progress estimate points) / total estimate points.

The total number of estimation points after each day.

The team that the cycle is associated with.

Period after which automatically closed and completed issues are automatically archived in months.

Period after which issues are automatically closed in months. Null/undefined means disabled.

The canceled workflow state which auto closed issues will be set to. Defaults to the first canceled state.

The cooldown time after each cycle in weeks.

Auto assign completed issues to current cycle.

Auto assign started issues to current cycle.

Auto assign issues to current cycle if in active status.

The day of the week that a new cycle starts.

What to use as an default estimate for unestimated issues.

The default workflow state into which issues are set when they are opened by team members.

The default template to use for new projects created for the team.

The default template to use for new issues created by members of the team.

The id of the default template to use for new issues created by members of the team.

The default template to use for new issues created by non-members of the team.

The id of the default template to use for new issues created by non-members of the team.

The workflow state into which issues are moved when a PR has been opened as draft.

Whether to group recent issue history entries.

Settings for all integrations associated with that team.

Unique hash for the team to be used in invite URLs.

Whether to allow zeros in issues estimates.

Whether to add additional points to the estimate scale.

The issue estimation type to use. Must be one of "notUsed", "exponential", "fibonacci", "linear", "tShirt".

Whether issues without priority should be sorted first.

[DEPRECATED] Whether to move issues to bottom of the column when changing state. Use setIssueSortOrderOnStateChange instead.

[INTERNAL] Whether new users should join this team by default.

The team's unique key. The key is used in URLs.

The workflow state into which issues are moved when they are marked as a duplicate of another issue. Defaults to the first canceled state.

Memberships associated with the team. For easier access of the same data, use `members` query.

The workflow state into which issues are moved when a PR has been merged.

The workflow state into which issues are moved when a PR is ready to be merged.

The organization that the team is associated with.

Whether an issue needs to have a priority set before leaving triage.

The workflow state into which issues are moved when a review has been requested for the PR.

Where to move issues when changing state.

Whether to send new issue comment notifications to Slack.

Whether to send new issue status updates to Slack.

Whether to send new issue notifications to Slack.

The workflow state into which issues are moved when a PR has been opened.

The states that define the workflow associated with the team.

The timezone of the team. Defaults to "America/Los_Angeles"

Whether triage mode is enabled for the team or not.

The workflow state into which issues are set when they are opened by non-team members or integrations if triage is enabled.

Issues that weren't completed when the cycle was closed.

Cycles

The documents content in markdown format.

[Internal] The documents content as a Prosemirror document.

[Internal] The documents content as YJS state.

The last template that was applied to this document.

The organization that the template is associated with. If null, the template is associated with a particular team.

The team that the template is associated with. If null, the template is global to the workspace.

The project that the document is associated with.

The time at which the project was automatically archived by the auto pruning process.

The time at which the project was moved into canceled state.

The time at which the project was moved into completed state.

The number of completed issues in the project after each week.

The number of completed estimation points after each week.

The project's content in markdown format.

[Internal] The project's content as YJS state.

The project was created based on this issue.

The number of in progress estimation points after each week.

Settings for all integrations associated with that project.

The total number of issues in the project after each week.

The last template that was applied to this project.

The overall progress of the project. This is the (completed estimate points + 0.25 * in progress estimate points) / total estimate points.

The time until which project update reminders are paused.

Project updates associated with the project.

The overall scope (total estimate points) of the project.

The total number of estimation points after each week.

The sort order for the project within the organization.

[INTERNAL] The resolution of the project's start date.

The time at which the project was moved into started state.

The estimated completion date of the project.

[INTERNAL] The resolution of the project's estimated completion date.

A flag that indicates whether the project is in the trash bin.

The order of the item in the project resources list.

Documents

The organization that the emoji belongs to.

Whether member users are allowed to send invites.

Allowed authentication providers, empty array means all are allowed.

The time at which deletion of the organization was requested.

The month at which the fiscal year starts. Defaults to January (0).

How git branches are formatted. If null, default formatting will be used.

Whether the Git integration linkback messages should be sent to private repositories.

Whether the Git integration linkback messages should be sent to public repositories.

Rolling 30-day total upload volume for the organization, in megabytes.

Previously used URL keys for the organization (last 3 are kept and redirected).

The day at which to prompt for project updates.

The hour at which to prompt for project updates.

The frequency at which to prompt for project updates.

The feature release channel the organization belongs to.

Whether the organization is using a roadmap.

Whether SAML authentication is enabled for organization.

Whether SCIM provisioning is enabled for organization.

Which day count to use for SLA calculations.

The organization's subscription to a paid plan.

Templates associated with the organization.

The time at which the trial of the plus plan will end.

Number of active users in the organization.

Linear API Integration Profile

Data Collections

API Operations

Integration Scenarios

Continuously Import Tasks to my App

Update Task

Create Task

Two-way realtime sync of Tasks

Get all Tasks

Tasks Unified API

Similar Integrations

Build every single integration your customers need with AI