The official command-line interface for Volley - Webhook forwarding for local development.
Similar to Stripe CLI, Volley CLI allows you to forward webhooks from your Volley sources to your local development environment. Perfect for testing webhooks locally without exposing your development server or dealing with changing URLs.
Volley is a webhook-as-a-service platform that provides reliable webhook infrastructure for both development and production. Volley accepts webhooks from any source and dispatches them to your endpoints with guaranteed delivery, rate limiting, and comprehensive monitoring.
Perfect for:
- 🧪 Local Development - Test webhooks locally without exposing your server
- 🏗️ Production Infrastructure - Reliable webhook delivery at scale
- 🔍 Webhook Debugging - Comprehensive monitoring and event replay
- 🏢 Multi-Tenant SaaS - Manage webhooks for multiple customers
- 🔄 Webhook Fan-out - Send one webhook to multiple destinations
Key Features:
- ✅ Persistent Webhook URLs - URLs that never change
- ✅ Guaranteed Delivery - Automatic retries with exponential backoff
- ✅ Built-in Monitoring - Track every webhook event with detailed metrics
- ✅ Rate Limiting - Configurable events per second (EPS) at source and destination levels
- ✅ Production Ready - Enterprise-grade reliability with 99.999% uptime
- ✅ Multi-Tenant Architecture - Organizations, projects, and role-based access control
- ✅ Local Development - CLI tool for forwarding webhooks to localhost (no tunneling needed)
brew tap volleyhq/volley
brew install volleyOr install directly:
brew install volleyhq/volley/volleyDownload the latest release from GitHub Releases and extract:
# For amd64
wget https://github.com/volleyhq/volley-cli/releases/latest/download/volley-linux-amd64.tar.gz
tar -xzf volley-linux-amd64.tar.gz
sudo mv volley /usr/local/bin/
# For arm64
wget https://github.com/volleyhq/volley-cli/releases/latest/download/volley-linux-arm64.tar.gz
tar -xzf volley-linux-arm64.tar.gz
sudo mv volley /usr/local/bin/Download the latest release from GitHub Releases and extract:
# Download and extract
Invoke-WebRequest -Uri "https://github.com/volleyhq/volley-cli/releases/latest/download/volley-windows-amd64.zip" -OutFile "volley.zip"
Expand-Archive -Path volley.zip -DestinationPath .
# Add to PATH or move to a directory in your PATH-
Sign up for Volley (if you haven't already):
- Visit volleyhooks.com to create a free account
- Create a webhook source in the dashboard to get your ingestion ID
-
Login to your Volley account:
volley login
-
Forward webhooks to your local server:
volley listen --source abc123xyz --forward-to http://localhost:3000/webhook
That's it! No connection or destination setup required. The CLI will automatically forward events from your source to localhost.
The CLI will poll for new webhook events and forward them to your local endpoint in real-time.
Volley is a comprehensive webhook-as-a-service platform that competes with both local development tools and production webhook infrastructure solutions.
Volley is a better alternative to ngrok for webhook testing and development:
| Feature | Volley | ngrok |
|---|---|---|
| Webhook URLs | Permanent, never change | Change on every restart |
| Tunneling Required | ❌ No tunneling needed | ✅ Requires persistent tunnel |
| Local Server Privacy | ✅ Completely private | |
| Built-in Retry | ✅ Automatic retries | ❌ No retry mechanism |
| Monitoring & Logging | ✅ Comprehensive dashboard | ❌ Limited (paid plans) |
| Rate Limiting | ✅ Configurable EPS | ❌ Not available |
| Production Ready | ✅ Same URL for dev/prod | ❌ Dev tool only |
| Offline Support | ✅ Webhooks queued | ❌ Must be online |
| Cost | Free tier: 10K events/month | Free tier: Limited features |
-
No Tunneling Required
- Volley doesn't require a persistent tunnel connection
- Your local server stays completely private
- No need to keep a process running
-
Persistent URLs
- Your webhook URL never changes:
https://api.volleyhooks.com/hook/abc123xyz - No need to update webhook URLs in external services
- Same URL works in development and production
- Your webhook URL never changes:
-
Production Features
- Automatic retry with exponential backoff
- Comprehensive monitoring and logging
- Rate limiting and throttling
- Event replay and debugging tools
-
Better Developer Experience
- Webhooks are queued if your local server is offline
- Built-in monitoring dashboard
- CLI tool similar to Stripe CLI
- No port forwarding configuration needed
Learn more: Why Volley Instead of ngrok?
Volley competes with full webhook infrastructure platforms like Hookdeck, Svix, and others:
| Feature | Volley | Hookdeck | Svix | webhook.site |
|---|---|---|---|---|
| Webhook-as-a-Service | ✅ Yes | ✅ Yes | ✅ Yes | ❌ Testing only |
| Permanent URLs | ✅ Yes | ✅ Yes | ✅ Yes | ❌ Temporary |
| Guaranteed Delivery | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Automatic Retries | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Rate Limiting | ✅ Configurable | ✅ Yes | ✅ Yes | ❌ No |
| Monitoring Dashboard | ✅ Comprehensive | ✅ Yes | ✅ Yes | |
| Local Development CLI | ✅ Yes | ❌ No | ❌ No | |
| Multi-Tenant Support | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Event Replay | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Free Tier | ✅ 10K events/month | ✅ Yes | ||
| Pricing | Transparent | Usage-based | Usage-based | Free only |
| Feature | Volley | RequestBin | webhook.site | ngrok |
|---|---|---|---|---|
| Permanent URLs | ✅ Yes | ❌ Temporary | ❌ Temporary | ❌ Changes on restart |
| Webhook Delivery | ✅ Active delivery | ❌ Passive viewing | ❌ Passive viewing | ✅ Tunnel |
| Production Ready | ✅ Yes | ❌ Testing only | ❌ Testing only | ❌ Dev tool only |
| Retry Logic | ✅ Automatic | ❌ No | ❌ No | ❌ No |
| Monitoring | ✅ Comprehensive | |||
| Local Development | ✅ CLI forwarding | ❌ No | ❌ No | ✅ Tunnel |
| Tunneling Required | ❌ No | ❌ No | ❌ No | ✅ Yes |
| Rate Limiting | ✅ Configurable | ❌ No | ❌ No | ❌ No |
For Local Development:
- ✅ Better than ngrok: No tunneling, persistent URLs, built-in monitoring
- ✅ Better than webhook.site: Active delivery, production-ready, CLI tool
- ✅ Better than RequestBin: Permanent URLs, automatic retries, comprehensive logging
For Production:
- ✅ Simpler Pricing - Transparent pricing vs complex usage-based models
- ✅ Local Dev + Production - Same platform for both, seamless transition
- ✅ Developer-Friendly - CLI tool, comprehensive docs, easy setup
- ✅ Enterprise Features - Multi-tenant, RBAC, rate limiting, monitoring
Use Cases:
- 🧪 Testing Stripe webhooks locally - Guide
- 🔍 Debugging Twilio webhooks - Guide
- 🔄 Webhook fan-out - Send one webhook to multiple destinations
- 🏢 Multi-tenant webhooks - Manage webhooks for SaaS platforms
- 📦 Production webhook infrastructure - Reliable delivery at scale
- 🔁 Event replay - Replay historical webhooks for testing
- 🚀 Replacing ngrok - Better alternative for webhook testing - Guide
See all use cases: docs.volleyhooks.com
volley login- Authenticate with your Volley accountvolley logout- Log out and clear credentialsvolley status- Check authentication status
volley listen --source <ingestion_id> --forward-to <url>- Forward webhooks to a local endpoint
volley listen --source abc123xyz --forward-to http://localhost:3000/webhookThis will:
- Connect to your Volley account
- Monitor the source with ingestion ID
abc123xyz - Poll for new webhook events
- Forward them to
http://localhost:3000/webhookin real-time
- Create a Stripe webhook source in Volley dashboard
- No connection or destination needed for localhost testing!
- Get your permanent webhook URL:
https://api.volleyhooks.com/hook/abc123xyz - Add this URL to Stripe Dashboard → Webhooks → Add endpoint
- Start forwarding to your local server:
volley listen --source abc123xyz --forward-to http://localhost:3000/webhook
- Trigger test events in Stripe - They'll be forwarded to your local server instantly!
Note: The CLI automatically handles events even if you haven't created a connection yet. Just create a source and start forwarding!
Full guide: Testing Stripe Webhooks Locally
You can forward the same webhook source to multiple local endpoints by running multiple CLI instances:
# Terminal 1: Forward to main API
volley listen --source abc123xyz --forward-to http://localhost:3000/webhook
# Terminal 2: Forward to webhook processor
volley listen --source abc123xyz --forward-to http://localhost:3001/process
# Terminal 3: Forward to logging service
volley listen --source abc123xyz --forward-to http://localhost:3002/logThe CLI uses a smart hybrid approach:
- Authenticates with your Volley account
- Finds the source by ingestion ID
- If connections exist: Uses connection-based polling (backward compatible)
- If no connections exist: Polls events directly from the source (simplified flow)
- Retrieves the full event payload with original headers
- Forwards it to your local endpoint, preserving exact headers and body for signature validation
Key Benefits:
- ✅ No connection required - Just create a source and start forwarding
- ✅ Simplified setup - Perfect for localhost testing
- ✅ Backward compatible - Works with existing connections too
- ✅ Preserves signatures - Headers and payload are forwarded exactly as received
The CLI stores configuration in:
- macOS/Linux:
~/.config/volley/config.json - Windows:
%APPDATA%\volley\config.json
You can override the API endpoint:
volley --api-url https://api.volleyhooks.com listen --source abc123xyz --forward-to http://localhost:3000/webhook# Build
make build
# Run tests
make test
# Install locally
make install
# Cross-platform builds
make release- Website: volleyhooks.com
- Documentation: docs.volleyhooks.com
- Dashboard: app.volleyhooks.com
- Support: app.volleyhooks.com/console/help
Ready-to-use examples showing how to integrate Volley:
- volley-stripe-example - Complete Stripe webhook integration with Express.js
- volley-local-dev-example - Local development examples in Node.js, Python, and Go
- Volley Platform - The webhook middleware platform
- Volley Documentation - Complete guides and API reference
Contributions are welcome! Please feel free to submit a Pull Request.
MIT License - See LICENSE file for details
Built with ❤️ by the Volley team
