New: MCP server monitoring is live. Start free

The in-app inbox

min

External channels (Slack, PagerDuty) are for interrupting people. The in-app inbox is for seeing the whole picture — including the safe stuff you intentionally don't get pinged about.

Where to find it

Inbox in the left nav. Or the bell icon in the top bar — same view, smaller.

How it's organized

Three columns: Open, Acknowledged, Resolved. Every change event lives in exactly one of these.

  • Open is your work queue. Anything new lands here.
  • Acknowledged means someone has eyes on it. The change isn't done, but it's not unowned.
  • Resolved means the work is finished — code updated, deprecation accepted, whatever the right answer was.

You move cards across columns with the two buttons on the change card. We cover the workflow in detail on Acknowledge & resolve.

Filters that matter

  • Severity — when you have ten minutes, filter to Breaking only. Read those.
  • Integration — pre-deploy check on the API your release touches.
  • Mine — what's been assigned to you.

The filter state is sticky per user, so the inbox you open tomorrow looks like the one you closed today.

Why the inbox sees more than your channels do

Your alert preferences route which severities go to Slack, PagerDuty, etc. The inbox shows everything — including safe changes you chose not to be pinged about. It's the source of truth; channels are an opinionated subset.

This means the inbox is where you'll catch the things you almost cared about. New endpoint added → safe → no Slack ping → but if you happen to be looking at the inbox the next morning, you might want to check it out.

Catch OpenAPI breaking changes early

Add your spec—diffs and alerts on every sync. No credit card to start; upgrade for faster polling, Slack or Teams, and more seats.