# rivr send and rivr verify --sequence: what your journal does with one order's events

- Date: 2026-11-02
- Type: New
- Surface: Developer portal and CLI
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-11-02-cli-send-sequences

`rivr verify` asks how your receiver answers; CLI 0.8.0 adds the next question, what your journal does with one order. `rivr send <status> --url <receiver url>` sends one signed test delivery of an order event (`created`, `pending`, `completed`, `cancelled` or `refunded`) with the body Rivr writes for that status, and prints the order's id; `--order <id>` makes the next `send` about the same order, with the same `merchantId` and `CreatedDate`. `rivr verify --sequence <name>` sends one order's events in a row and checks that each gets `2xx` within five seconds: `invoice-paid`, `refund`, `cancel`, `out-of-order`, `late-duplicate` (the first `Completed` again with the same `Rivr-Webhook-Id` after `Refunded`, a retry that came late, which verify's own duplicate does not cover) and `same-status` (`Completed` twice with different ids). The last line says which status the order should have in your journal, for a receiver that takes the status from the webhook. Nothing goes to Rivr: the deliveries are signed with your own `RIVR_WEBHOOK_SECRET`, marked `Rivr-Webhook-Test: true`, and the order is invented. The guide Test in the sandbox (/guides/testing) describes both. Run the install command again to update.