RealComposer

Linear Safe & Unsafe Practices

Direct Answer

Linear personal API keys act as your user across every team and are server-only. Prefer OAuth applications with read-only scopes for integrations, and verify the Linear-Signature header on webhooks before acting on issue events.

Credentials & Where They Belong

Server only
Personal API key

Acts as your user with your full permissions.

Server only
OAuth access token

Scoped access granted to an application.

Server only
Webhook signing secret

Verifies the Linear-Signature HMAC.

Safe Practices

  • Use OAuth apps with read scope for dashboards

    Public roadmaps and status pages only need read access.

  • Query only the fields you render

    GraphQL lets you request exact fields, keeping payloads and complexity low.

Unsafe Practices

  • Embedding a personal key in a public roadmap page

    Visitors can read private issues and create or edit work as you.

  • Skipping webhook signature checks

    Forged events can trigger automations in your systems.

The RealComposer Pattern

Store LINEAR_API_KEY in the vault and expose a cached pipeline that returns a slim list of public issues for roadmaps or status pages.

START BUILDING FREE

Frequently Asked Questions

Q:Is a Linear API key tied to a user?

Yes. Personal keys inherit that user access, so prefer OAuth apps or a dedicated bot account.

Multi-API Aggregation

Merge Linear Issues and Github Pull Requests into One Dashboard API

To solve merge linear issues and github pull requests into one dashboard api, never execute unauthenticated requests or embed private tokens directly in client bundles. RealComposer acts as a sub-10ms edge gateway running on Cloudflare Workers that securely injects credentials from your Secret Vault, normalizes responses, and prevents unauthorized API usage. Route calls through your RealComposer edge URL to guarantee complete privacy, robust origin validation, and low mobile latency.

Sub-10ms edgeView Recipe

Related Concepts