Quickstart
This takes a provider’s webhook from a Ricochet URL to a server on your machine. You
need an account (sign-up is by invite during the alpha) and a local server that
accepts POST requests, here on http://localhost:3000/webhooks.
-
Sign in to the dashboard. Open app.getricochet.dev and sign in with the link we email you. Your first project starts with a
devenvironment, and the first-run screen walks through the next three steps. -
Create a source. A source is the URL a provider sends to. Pick the sender (Stripe, GitHub, generic HMAC or “not listed”) and copy the URL, which looks like
https://in.getricochet.dev/src_…. -
Point the provider at it and set its secret. Paste the URL where the provider asks for a webhook endpoint, then copy the provider’s signing secret into the source, so Ricochet can check every request. The provider guides say where each provider keeps it.
-
Install the CLI. A single binary for Linux, macOS and Windows (from Git Bash); the script checks its checksum and puts it in
~/.local/bin:Terminal window curl -fsSL https://getricochet.dev/install.sh | shThe builds are also at /download/latest/.
-
Sign in from the CLI. This opens the browser; confirm the code shown in the terminal.
Terminal window ricochet login -
Forward events to your app.
Terminal window ricochet listen --forward localhost:3000/webhooksThe CLI connects your own CLI destination to the environment’s sources and shows each event as it arrives, with your server’s status and latency. It saves the target in
.ricochet.json, so next timericochet listenis enough. -
Send an event. Trigger one from the provider, or send a signed sample:
Terminal window ricochet trigger stripe invoice.paid
If your handler fails, fix it and send the same event again. In the full-screen view,
select the event and press r, or:
ricochet replay evt_…Next steps
Section titled “Next steps”- Deliver to a deployed app: create an HTTP destination and connect the source to it.
- Verify Ricochet’s signature in your handler.
- Read the concepts behind sources, destinations and replays.