What is your goal?
Create a custom webhook.
What is the problem & what have you tried?
When copying the URL of the webhook to my Safari browser I receive the message ‘unauthorised’ instead of ‘accepted’.
I just started using make.com and with my first attempts a few days earlier there were no problems.
Error messages or input/output bundles
Just the word ‘Unauthorized’.
Check the webhook settings in Make and see if API key authentication is enabled. If it is, opening the URL directly in Safari won’t work because the request needs to include the API key in the x-make-apikey header.
You can test it using Postman by adding that header with your API key and sending a request. Also, check whether any IP restrictions have been added to the webhook. That might help narrow down what’s causing the Unauthorized response.
When you paste a make.com webhook URL directly into Safari, your browser makes a GET request, but Make webhooks expect a specific payload structure; typically via a POST request which triggers the ‘Unauthorized’ or method error if triggered natively like that. To properly test it, use a tool like Postman or cURL to send a POST request with JSON data, and make sure your scenario is toggled to ‘Run once’ in Make before sending. Let me know what platform or tool is supposed to send data to this webhook and I can outline the correct request format right here.
That reply usually means the webhook is asking for authentication, not that it’s broken. Open the webhook in the Webhooks section (or click the webhook module and choose Edit), then check its advanced settings for an API key or IP restriction. If either is set, a plain browser request will always be refused, because the browser doesn’t send the key header. Remove the restriction while you test, or send the key from Postman or the calling app instead. If nothing is set there, create a fresh webhook, because a URL copied from an older or deleted hook won’t match the scenario that’s listening now.
Welcome to the Make community!
You have created a webhook with an API key. Therefore any request that you send to that address requires the API key, otherwise you’ll get the unauthorised response. If you want to test it in your web browser, you’ll have to delete the API key attached to your webhook. Alternatively, test it in Postman using the instructions the others have shared.
Follow these official instructions to edit your webhook: Webhooks - Apps Documentation
Hope this helps! If you are still having trouble, please provide more details.
— @samliew