For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/features/products/webhook-delivery.md.
  • English

      • Why did my delivery webhook test fail?

      When you click Send test, Clickmax posts the payload to the Webhook URL you configured and shows the response your server returned. The badge next to the button carries the real HTTP status — for example 401 - Unauthorized — not a generic confirmation.

      A status outside the 2xx range means the delivery reached your server and your server rejected it. The problem is on the receiving side, not in the sending.

      Workspace role: Owner, Administrator, Editor or Collaborator.

      Where to see the test result

      1. Open the product, go to the offer and add (or edit) a webhook delivery.
      2. Fill in the Webhook URL and the HTTP Method.
      3. Under Select the events to trigger, pick at least one event.
      4. Click Send test.
      5. Click Show payload to open the details.

      The panel shows two parts:

      SectionWhat it contains
      Sent payloadThe JSON Clickmax built and sent
      Your server responseStatus, headers and body your server returned

      Very long responses appear cut off, with a note that only the beginning is shown.

      What each status means

      StatusMeaningWhat to do
      200, 201, 204Delivery acceptedNothing. It works.
      401, 403Your server rejected the authenticationCheck the token in the URL and the headers under Add custom authentication?
      404The address does not exist on your serverReview the URL path
      405Your server does not accept that methodChange the HTTP Method to what your endpoint expects
      500 and other 5xxYour server received it but broke while processingCheck your application logs against the sent payload

      Always read the body under Your server response: most APIs explain the reason there, such as {"error":"unauthorized"}.

      If the URL redirects

      When the address you entered redirects to another one within the same site — most commonly the domain without www pointing to the www version — Clickmax follows the redirect automatically and delivers to the final destination. You do not need to do anything.

      A redirect to another site is refused, with this message:

      This address redirects to another site. Use your webhook final address.

      That is intentional: the authentication headers you saved are not resent to a domain other than the one you configured. Find out where your address points and enter that final address directly.

      If the address is refused before sending

      The message below appears when the address cannot be used as a webhook:

      The webhook URL must be a public, valid https address.

      Possible causes:

      • The address does not start with https://
      • It is an internal or local network address (for example localhost or private ranges)
      • The domain does not resolve
      • The address carries an embedded username and password, in the https://user:password@domain format

      In these cases nothing is sent. Fix the address and test again.