Customer Stories

2026 Q3 in review: custom domains

LALars Delgado1 min read

The change is backwards compatible, so integrations built against the old shape carry on unchanged. This has been the most requested change on the board for a while, and it is now live for every workspace.

How it works

There is nothing to do on your side; the change is already in front of you. Nothing about billing changes, on any plan. The API returns the same fields it always has, with one addition.

  1. Enable a Linear two-way sync.
  2. Enable changelog email previews.
  3. Enable custom fields.
  4. Enable dark mode.

Limits

The limit is generous enough that most teams will never meet it. Existing setups keep working exactly as they did — nothing needs migrating. The setting lives under Settings, and defaults to the behaviour you already had.

Common pitfalls

The docs page for this was rewritten alongside it. If you were using the workaround, you can drop it — the built-in path covers the same ground.

curl -sS https://api.example.test/v2/posts \
  -H "Authorization: Bearer $BULLETIN_API_KEY"
  • beta
  • breaking
840 views

Keep reading

  • Three questions the inbox should answer

    The limit is generous enough that most teams will never meet it. We are watching the numbers for a week before turning it on by default. How it works. Anything already in flight w…

    BRBruno Okafor1 min read
  • PinnedProduct

    How Cyberdyne cut triage time in half

    Keyboard access and screen reader labels were part of the work, not a follow up. Nothing about billing changes, on any plan. Before you start. The API returns the same fields it a…

    LELena Petrov1 min read
  • Pinned

    What we learned shipping an RSS feed

    Keyboard access and screen reader labels were part of the work, not a follow up. The change is backwards compatible, so integrations built against the old shape carry on unchanged…

    SASana Novak1 min read