Your webhook answers with a 307 or 308 redirect

A redirect says go to another address. Many webhook senders do not follow it and count it as a failed delivery. Use the final address in your provider settings.

What you might see

The provider shows 307, 308, 301 or 302 for your webhook.
Your app never gets the event.
A browser opens your webhook address and lands somewhere else.

Why it happens

Common reasons: your host adds or removes a trailing slash, forces https, or sends the bare domain to www.

Some frameworks and middleware also redirect unknown or logged-out requests to a login page.

How to fix it

Find the final address. Run the Tillping scan or use curl to follow the redirect chain. The last address that answers is the one to use.
```
curl -s -o /dev/null -D - -X POST https://yourapp.com/api/webhook
```
Put that address in the provider dashboard. Copy it exactly. Match https, the www part and the trailing slash.
Fix the cause. If you use Next.js, check the trailingSlash option. Check your domain redirects on your host. Check middleware that sends logged-out users to a login page, and let the webhook route through.
Re-send a test event. Most providers let you re-send an event. Do it once and check for a 2xx reply.

Check your fix

Scan again with Tillping. The redirect finding should be gone, and the chain should end at your endpoint.

Run the free check

Paste your webhook address and see what your endpoint answers. No account. No keys.

Check my webhook