invalid-webhook-url

422 Unprocessable Content · Invalid webhook URL · type: https://docs.dlogify.com/errors/invalid-webhook-url

When it happensCopy Anchor Link

• The URL does not use https, contains credentials or a fragment, or uses a port other than 443 or 1024–65535.
• The host name is local, or resolves to at least one private, loopback or otherwise non-public address.
• For a Slack or Discord channel, the URL is not an incoming webhook URL of that platform (see Slack and Discord); the detail says which form is expected.

How to fix itCopy Anchor Link

Use a public https endpoint. For local development, expose your receiver through a tunnel with a public https address. For a webhook, the message is the same whatever rule failed, so check each of them. See Webhooks. For Slack or Discord, paste the URL exactly as the platform gives it.

ExampleCopy Anchor Link

HTTP/1.1 422 Unprocessable Content
Content-Type: application/problem+json

{
  "type": "https://docs.dlogify.com/errors/invalid-webhook-url",
  "title": "Invalid webhook URL",
  "status": 422,
  "detail": "The webhook URL must use https and resolve to a public address.",
  "instance": "req_01j…"
}