The Gravv API, from your terminal
Install the CLI, sign in with a sandbox key, and work a whole payment flow by hand before you write any code against it.
One command to install it
The installer puts the gravv binary on your path. It is also where the CLI's own documentation lives.
Install the Gravv CLI
curl -sSL https://get.gravv.xyz | shmacOS or Linux, in any shell that has curl.
Installed, signed in, and working the flow
Three steps, and the second one is the one that decides what the third can touch.
- Install itOne command. The installer script puts the gravv binary on your path.
- AuthenticateSign in with a sandbox key. The CLI uses the same keys as the API, so a sandbox key reaches sandbox and nothing else.
- Work the flowCreate a customer, open an account, move money, read it back, against the same endpoints your code will call.
Why use it at all
It is not a different product with a different surface. That is the whole point of it.
- The same surface as your code
The CLI calls the Gravv API. There is no second surface to learn and nothing it can do that an API key cannot.
- The same keys and the same limits
A key carries its environment and its permissions. The CLI inherits both, so sandbox stays sandbox.
- Before you write anything
Walk the sequence once in a terminal and you know the shape of the integration before the first line of code.
Three ways to reach the same API
Your code, your terminal, or an assistant. One key model, one set of limits, one surface underneath all three, and the terminal is this page.
What it can do is what your key can do
Nothing about the CLI widens a key. Sandbox keys reach sandbox; live keys reach live, after review.