Overview
Zendesk Webhook is a webhook callback from Zendesk used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Its primary user-agent pattern is Zendesk Webhook.
Zendesk Webhook is Unverified at the identity-evidence level. The listed identity remains useful for detection, but this record does not currently contain authoritative evidence sufficient to authenticate the identity claim.
Robots.txt behavior is not currently confirmed.
Zendesk Webhook can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
Zendesk Webhook - HTTP Agent Examples
-
Zendesk Webhook - Robots Token
- Zendesk Webhook
- Identity Type
- Observed
- Evidence Method
- Treat `Zendesk Webhook` as an identity signal only. Confirm it with current operator documentation, cryptographic verification, forward-confirmed reverse DNS, source-network ownership, or other authoritative evidence before trusting the claimed identity.
Classification
- Type
- Webhook
- Kind
- Webhook
- Family
- Zendesk
- Purpose
- Webhook
Behavior and handling
- Common Use
- Zendesk Webhook is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Detection Notes
- Zendesk Webhook traffic is primarily detected by the `Zendesk Webhook` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence with Zendesk infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Zendesk Webhook has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- Do not block
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Zendesk Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.