Prismic Webhook uses GET instead of POST?

[adamthoti (Adam Toth)]

Hello,

I have been utilizing Prismic webhooks in my Next.js application for tag revalidation. This setup has been functioning correctly for over two weeks. Recently, however, I started encountering 405 status codes when the webhooks are triggered. Upon investigating, I noticed that the method received from Prismic is GET instead of the expected POST. Manually calling my revalidation endpoint works seamlessly.

Could you please inform me if there have been any recent changes to the webhook configurations or any related aspects on your end? I have not found any updates or changes documented that might explain this issue.

Thank you

[Phil (Phil Snow)]

Hi Adam,

There have been no changes to how we handle webhooks. All our methods on our APIs are get methods.

Maybe this thread will help:

Caching issue with Next.js App Router - Vercel Deployment

Dear Prismic team I set up a new Next.js App Router project using your setup command npx @slicemachine/init@latest and walking trough your step by step setup guide. In previous versions, I never had issues deploying the site to Vercel and setting up Prismic Webhooks to trigger redeploys. With this new project it seems like there are some caching issues with Vercel: If I push a new commit to Github or if I edit content on Prismic, it triggers a new deploy correctly. Unfortunately those deplo…

Thanks.