Bot intelligence record
Recurly Webhooks
Usually allowUse the Recurly Webhook identifier to separate Recurly webhook or service callback traffic from normal visitor requests in server logs.
- Operator
- Recurly
- Family
- Recurly
- Type
- Webhook
- Source type
- Verified Directory
- Last checked
- 2026-05-20
User-Agent Pattern
RecurlyRecurly Webhook
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: Recurly Webhook Disallow: /
Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Webhook notifications, callbacks, payment events, or service-to-service integration requests.
Record Details
Structured data- Operator
- Recurly
- Family
- Recurly
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-05-20
- Source type
- Verified Directory
- Verification
- Follow the operator's own documentation when additional verification details are available.
- Spoofing risk
- User-agent strings for Recurly Webhook can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.
Notes
Recurly Webhooks is listed in the Botcrawl directory as a webhook callback service from Recurly. The primary identifier for log review is Recurly Webhook.
Identification
- User-agent pattern:
Recurly Webhook - Family: Recurly
- Type: Webhook
- Kind: Webhook
Common use
Webhook notifications, callbacks, payment events, or service-to-service integration requests.
Verification and handling
Follow the operator's own documentation when additional verification details are available.
Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: Yes.
Evidence and Source
- Follow the operator's own documentation when additional verification details are available.
- Match `Recurly Webhook` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Webhook notifications, callbacks, payment events, or service-to-service integration requests.
- User-agent strings for Recurly Webhook can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.
