Quri

Relay (email deliverability)

Last updated 2026-06-14

What this unlocks

Connect Relay and Quri reads your email send stats — totals sent, bounced, complained, suppressed, and failed — and turns them into a Deliverability Health report: rates, trend, a 0–100 score, and plain fixes. Aggregate counts only, never recipient details, so you catch a souring sender reputation before mailboxes start filtering you.

Connect it in Quri

  1. Open /app/connect in Quri and choose Relay from the list of sources.
  2. Paste your Relay stats base URL and read key into the connect form.
  3. Save the connection so Quri can pull your aggregate delivery stats on a schedule.
  4. Open /app/comms/health — your Deliverability Health report appears after the first scheduled run.

Get your credentials

  1. Sign in to Relay and open the stats/API section for your sending account.
  2. Copy the stats base URL Relay exposes for delivery metrics.
  3. Create a read-only stats key (scoped to aggregate counts, not recipient data).
  4. Keep both values handy; you paste them into Quri at /app/connect.

Access Quri reads with

  • Read-only access to aggregate delivery counts — sent, bounced, complained, suppressed, failed.
  • No recipient addresses or message contents are ever read — only the totals Quri needs to score deliverability.

Troubleshooting

I connected Relay but Deliverability Health still says computing.
The report is materialized on a schedule, not on the spot. Until the first run lands for your workspace, the screen shows a computing state. Re-check the base URL and read key at /app/connect if it stays empty.
Does Quri read who I emailed?
No. The Relay stats read returns aggregate counts only — totals sent, bounced, complained, suppressed, and failed. No recipient addresses or message bodies cross into Quri.
Why is my health score low even though emails are sending?
A low score reflects bounce, complaint, or hard-failure rates above the SES warning lines. Open /app/comms/health to see which rate is elevated and the recommended fix, such as cleaning your list or cutting send frequency.