OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
GraphQL issues expose IDs, descriptions, timestamps and related metadata with cursor pagination. Archived resources are hidden unless explicitly included.
Linear GraphQL issue retrieval ↗
Queries, fetching updates and archived resources · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
GraphQL issues expose IDs, descriptions, timestamps and related metadata with cursor pagination. Archived resources are hidden unless explicitly included.
Linear GraphQL issue retrieval ↗
Queries, fetching updates and archived resources · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Issue filters and sorting can narrow by properties and updated time. GraphQL field selection alone does not establish SQL joins and aggregation.
Linear GraphQL issue retrieval ↗
Queries, fetching updates and archived resources · Checked 2026-10-16
Access cost barrier -
-
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
The reviewed developer sources do not establish a complete minimum-plan entitlement and fixed-fee statement for this portfolio.
Linear API rate and complexity limits ↗
OAuth request and complexity budgets; response headers · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 10.0/10
Customer authorization without discretionary provider approval
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
OAuth applications request customer authorization and scopes; Linear recommends OAuth for applications used by others. User/team permissions and organization controls still constrain access.
Linear OAuth application authorization ↗
Authorization flow and scopes · Checked 2026-10-16
Downstream permission -
-
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Applicable third-party processing, AI-use and redistribution terms require a separate contractual review.
Linear OAuth application authorization ↗
Authorization flow and scopes · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 7.5/10
Create and update in one business domain
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
issueCreate and issueUpdate are documented mutations with success flags and selected response fields. GraphQL HTTP 200 can still contain partial errors.
Linear issue mutations ↗
Creating and editing issues; GraphQL error handling · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Customers can build or choose applications using the documented API and the disclosed authorization route.
Linear OAuth application authorization ↗
Authorization flow and scopes · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Issue webhook payloads include create, update and remove actions, entity data and a unique delivery ID. Updated-time polling and explicit archive inclusion support reconciliation.
Linear issue webhooks ↗
Data change events and delivery ID · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
OAuth apps receive 5,000 requests/hour per user or app user, plus a 2,000,000-point hourly complexity budget. Endpoint-specific limits and reset headers also apply.
Linear API rate and complexity limits ↗
OAuth request and complexity budgets; response headers · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Issue data-change payloads expose create/update/remove action plus entity data and delivery identity. This does not establish coverage of every Linear resource.
Linear issue webhooks ↗
Data change events and delivery ID · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Restart issue enumeration and follow endCursor/hasNextPage through the authorized collection with includeArchived: true to rebuild current issue state. This recovers a current snapshot (not deleted payloads, intermediate history or a retained webhook log); permissions and concurrent changes still require reconciliation.
Linear GraphQL issue retrieval ↗
Queries & Mutations; Archived resources; linked Pagination guide (first/after and pageInfo) · Checked 2026-10-16
Linear complete cursor pagination ↗
Fetching all results; first/after and pageInfo.hasNextPage/endCursor · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Issue CSV and GraphQL records can be retained externally. Authenticated images require separate downloads; complete comment history, configuration and native automation restore remain unverified.
Linear issue exports ↗
CSV issue export and workspace export scope · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
The reviewed extraction guide does not establish contractual retrieval rights after cancellation.
Linear issue exports ↗
CSV issue export and workspace export scope · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Issue CSV and GraphQL records can be retained externally. Authenticated images require separate downloads; complete comment history, configuration and native automation restore remain unverified.
Linear issue exports ↗
CSV issue export and workspace export scope · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Linear OAuth application authorization ↗
Authorization flow and scopes · Checked 2026-10-16
Rights to custom logic -
-
Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate.
Native workflow ownership, reusable export and independent execution rights remain unresolved.
Linear OAuth application authorization ↗
Authorization flow and scopes · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
OAuth applications request customer authorization and scopes; Linear recommends OAuth for applications used by others. User/team permissions and organization controls still constrain access.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
GraphQL issues expose IDs, descriptions, timestamps and related metadata with cursor pagination. Archived resources are hidden unless explicitly included. Issue filters and sorting can narrow by properties and updated time. GraphQL field selection alone does not establish SQL joins and aggregation.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Customer-authorized application | OAuth 2.0 | Integration provider | No | customer authorization | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The reviewed developer sources do not establish a complete minimum-plan entitlement and fixed-fee statement for this portfolio.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
issueCreate and issueUpdate are documented mutations with success flags and selected response fields. GraphQL HTTP 200 can still contain partial errors.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Issue webhook payloads include create, update and remove actions, entity data and a unique delivery ID. Updated-time polling and explicit archive inclusion support reconciliation. OAuth apps receive 5,000 requests/hour per user or app user, plus a 2,000,000-point hourly complexity budget. Endpoint-specific limits and reset headers also apply. Current issue state can be rebuilt by repeating cursor enumeration with includeArchived: true; this does not recover deleted payloads or intermediate changes.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Issue data-change payloads expose create/update/remove action plus entity data and delivery identity. This does not establish coverage of every Linear resource. | Linear issue webhooks ↗Data change events and delivery IDChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Restart issue enumeration and follow endCursor/hasNextPage through the authorized collection with includeArchived: true to rebuild current issue state. This recovers a current snapshot (not deleted payloads, intermediate history or a retained webhook log); permissions and concurrent changes still require reconciliation. | Linear GraphQL issue retrieval ↗Queries & Mutations; Archived resources; linked Pagination guide (first/after and pageInfo)Checked 2026-10-16 Linear complete cursor pagination ↗Fetching all results; first/after and pageInfo.hasNextPage/endCursorChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Issue CSV and GraphQL records can be retained externally. Authenticated images require separate downloads; complete comment history, configuration and native automation restore remain unverified.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights).
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopeLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. GraphQL issues expose IDs, descriptions, timestamps and related metadata with cursor pagination. Archived resources are hidden unless explicitly included. | Linear GraphQL issue retrieval ↗Queries, fetching updates and archived resourcesChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. GraphQL issues expose IDs, descriptions, timestamps and related metadata with cursor pagination. Archived resources are hidden unless explicitly included. | Linear GraphQL issue retrieval ↗Queries, fetching updates and archived resourcesChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Issue filters and sorting can narrow by properties and updated time. GraphQL field selection alone does not establish SQL joins and aggregation. | Linear GraphQL issue retrieval ↗Queries, fetching updates and archived resourcesChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Customer authorization without discretionary provider approvalLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. OAuth applications request customer authorization and scopes; Linear recommends OAuth for applications used by others. User/team permissions and organization controls still constrain access. | Linear OAuth application authorization ↗Authorization flow and scopesChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. The reviewed developer sources do not establish a complete minimum-plan entitlement and fixed-fee statement for this portfolio. | Linear API rate and complexity limits ↗OAuth request and complexity budgets; response headersChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Applicable third-party processing, AI-use and redistribution terms require a separate contractual review. | Linear OAuth application authorization ↗Authorization flow and scopesChecked 2026-10-16 |
| Which external write operations are documented? | Create and update in one business domainLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. issueCreate and issueUpdate are documented mutations with success flags and selected response fields. GraphQL HTTP 200 can still contain partial errors. | Linear issue mutations ↗Creating and editing issues; GraphQL error handlingChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Customers can build or choose applications using the documented API and the disclosed authorization route. | Linear OAuth application authorization ↗Authorization flow and scopesChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Issue webhook payloads include create, update and remove actions, entity data and a unique delivery ID. Updated-time polling and explicit archive inclusion support reconciliation. | Linear issue webhooks ↗Data change events and delivery IDChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. OAuth apps receive 5,000 requests/hour per user or app user, plus a 2,000,000-point hourly complexity budget. Endpoint-specific limits and reset headers also apply. | Linear API rate and complexity limits ↗OAuth request and complexity budgets; response headersChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Issue CSV and GraphQL records can be retained externally. Authenticated images require separate downloads; complete comment history, configuration and native automation restore remain unverified. | Linear issue exports ↗CSV issue export and workspace export scopeChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. The reviewed extraction guide does not establish contractual retrieval rights after cancellation. | Linear issue exports ↗CSV issue export and workspace export scopeChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Customers can implement external logic against the assessed API. Ownership and reusable export of native workflow artifacts remain unresolved (customer integration code does not establish those rights). | Linear OAuth application authorization ↗Authorization flow and scopesChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Linear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Native workflow ownership, reusable export and independent execution rights remain unresolved. | Linear OAuth application authorization ↗Authorization flow and scopesChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedLinear / customer-authorized OAuth, GraphQL issues and related team metadata, issue webhooks and CSV issue exports; native workflow ownership and enterprise administration are separate. Issue CSV and GraphQL records can be retained externally. Authenticated images require separate downloads; complete comment history, configuration and native automation restore remain unverified. | Linear issue exports ↗CSV issue export and workspace export scopeChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Applicable downstream processing and redistribution terms
- Post-cancellation retrieval rights
- Native workflow artifact ownership and independent execution
- Whole-product completeness beyond the declared objects and routes
- Complete commercial entitlement for the assessed portfolio
- Retained webhook history, deleted issue payloads and intermediate changes after an outage
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.