Bot intelligence record
SendGrid
Usually allowSendGrid is a webhook callback used for webhook delivery, payment notifications, service callbacks; it appears in server logs as `SendGrid Event API`.
User-Agent Pattern
SendGridSendGrid Event API
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: SendGrid Event API
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
NoThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
SendGrid is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Record Details
Verified fields- Operator
- SendGrid
- Family
- SendGrid
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify SendGrid by matching `SendGrid Event API` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Spoofing risk
- SendGrid has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- SendGrid is a webhook callback used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Its primary user-agent pattern is
SendGrid Event API. - SendGrid is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is documented crawler-pattern evidence.
- SendGrid does not have confirmed robots.txt behavior in the available public evidence.
- SendGrid can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify SendGrid by matching `SendGrid Event API` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- SendGrid traffic is primarily detected by the `SendGrid Event API` user-agent pattern. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- SendGrid is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- SendGrid has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Use This Signal In Edge
Botcrawl EdgeUse Edge to match live requests, detect related datacenter traffic, and apply allow, block, rate-limit, or log rules.