Rodeo CLI
The official command-line tool for webhook.rodeo - the easiest way to receive, inspect, and forward webhooks to your local development environment.
Installation
npm install -g @webhook-rodeo/cli
Basic usage
The most common workflow is forwarding webhooks to your local server:
# 1. Authenticate with your webhook.rodeo account
rodeo login
# 2. View your webhooks
rodeo webhooks
# 3. Forward a webhook to your local server
rodeo forward 3000 my-webhook
That's it! Webhooks sent to webhook.rodeo will now forward to http://localhost:3000.
Commands
rodeo login
Authenticate with your webhook.rodeo account. Opens your browser for secure authentication (supports SSO).
rodeo login
You rarely need to run this yourself: rodeo forward and rodeo webhooks sign you in when there is no session, or when it has expired. Use rodeo login --force to switch accounts.
On a machine without a browser, rodeo login --no-browser prints the sign-in URL instead of opening it. Open it in a browser on the same machine: the sign-in finishes by sending that browser to http://127.0.0.1:1337.
rodeo webhooks
List all your active webhooks with their URLs and current forwarding status.
rodeo webhooks
rodeo forward [PORT] [WEBHOOK-NAME]
Forward webhook events to your local development server. If you don't provide a port or webhook name, the CLI will prompt you interactively.
# Forward to a specific port
rodeo forward 3000 my-webhook
# Forward to a full URL
rodeo forward http://localhost:8080/webhooks my-webhook
# Interactive mode (prompts for port and webhook)
rodeo forward
Options:
PORT- Port number (e.g.,3000) or full URL (e.g.,http://localhost:8080/webhook)WEBHOOK-NAME- Name of your webhook from webhook.rodeo--timeout- Seconds to wait for your local server to respond (default30)
How it works: the CLI keeps a connection open to webhook.rodeo and replays each incoming webhook against your local server from your own machine, with the original headers and body. Nothing needs to be reachable from the internet. If the connection drops, the CLI reconnects and picks up where it left off, so webhooks that arrived in the meantime are still delivered.
rodeo status
Check your current authentication status and when your session expires.
rodeo status
rodeo logout
Sign out from your webhook.rodeo account.
rodeo logout
Use cases
Local development
Test webhooks from services like Stripe, GitHub, Twilio, etc. on your local machine without deploying:
# Start your local server
npm run dev # Running on port 3000
# In another terminal, forward webhooks
rodeo forward 3000 stripe-webhooks
Now Stripe webhooks go directly to your local server!
Testing different environments
Forward the same webhook to different local services:
# Forward to your API server
rodeo forward 8080 my-webhook
# Or to a specific endpoint
rodeo forward http://localhost:8080/api/webhooks my-webhook
Debugging
See the complete request and response data in real-time:
- Full request headers and body
- Response headers and body
- Response time and status codes
- Syntax-highlighted JSON
Troubleshooting
"Your session has expired"
CLI sessions last for a limited time. In a terminal, the CLI opens your browser and signs you in again automatically, including in the middle of rodeo forward. In scripts and CI it exits with this message instead; run rodeo login and try again.
"Connection refused"
The webhook reached the CLI, but nothing answered at the address you are forwarding to. Check that your local server is running and that the port and path are right.
Session storage
CLI sessions are stored in ~/.config/rodeo/config.json. To reset:
rodeo logout
# Or manually delete
rm ~/.config/rodeo/config.json