New — Iris AI drafts your firewall, routing & rate-limit rules. Explore AI features →
Changelog
Security

Let webhooks and health checks through an app behind sign-in

List the paths that work without sign-in, with the methods each one allows. A webhook path can check the sender's signature before it lets a request in.

Let webhooks and health checks through an app behind sign-in

An app behind sign-in still gets calls from things that can't sign in: GitHub posting a webhook, an uptime checker asking for /health. Until now the only way to let them through was an older API setting that listed the protected paths, and it didn't work on an endpoint with users.

Now Sign-in has a Paths that skip sign-in card. Above, Acme Labs' console lets three paths through: GitHub's webhooks, as a POST with a valid signature, and GET and HEAD on /health and /.well-known/*. Every other path still needs sign-in.

The Edit path dialog for /webhooks/github: POST ticked, Check the webhook signature ticked, the sender github, and the signing secret shown as Saved secret — type to replace
Only GitHub's own deliveries get through on /webhooks/github: a POST the sender didn't sign gets a 401. The secret comes from GitHub's webhook settings and is never shown again.
The Overview: Only signed-in users can open app.example.com, except 3 open paths
The Overview says what's open, and 3 open paths links to the list.

What changed

  • Two ways to read the list. Open without sign-in: every path needs sign-in except the ones listed. Protect only these paths: only the listed paths need sign-in, and every other path is open to anyone, pages you add later included. Switching between them asks first.
  • Methods per path. Every method, or any of GET, HEAD, POST, PUT, PATCH, DELETE and OPTIONS. Other methods still need sign-in.
  • A signature check in the same dialog. A path can check a webhook's signature first, for a sender such as GitHub or Slack, or as a generic HMAC with your header, algorithm and prefix. Only requests the sender signed get through. It works the way the Verify webhook rule does, on a path of an endpoint with sign-in.
  • POST without a check opens every method. Rails, Laravel and Symfony can read the method from the request body, so a POST can act as PUT, PATCH or DELETE. The dialog offers to open every method or to add a signature check.
  • One-click starts. Start from /webhooks/*, /health or /.well-known/*. /webhooks/* covers /webhooks and everything under it.
  • Your app still knows who's signed in. On a path that skips sign-in, a signed-in visitor still reaches your app as that user. Everyone else arrives without a user.
  • Up to 50 paths per endpoint, written as callers send them.

Get started

  1. Open the endpoint's Sign-in & access tab, then Sign-in.
  2. Under Paths that skip sign-in, click Add path. Start from /webhooks/*, /health or /.well-known/*, or type your own.
  3. Pick the methods. For a webhook, tick Check the webhook signature, choose the sender and paste its signing secret.
  4. Click Open path.
  5. Read the docs: Paths that skip sign-in.

Read the docs

Ask an AI to summarise this page
Deploy
App hosting Edge functions Domains & certificates
Connect
Secure tunnels API gateway Multi-region edge
Protect
Bot protection & challenge WAF & firewall Edge login
Observe & AI
Monitoring Inspector & replay Iris AI MCP server AI Gateway
Developers
Developer tools Docs ngrok policy converter Blog Changelog
Compare
Ngris vs ngrok Ngris vs Cloudflare Tunnel Ngris vs Vercel Ngris vs Netlify Expose localhost guide
More
Solutions Pricing Enterprise Sign in Get Started Free