Start with the developer tools available today
Draft generic payment JSON in your browser or send a preset, unauthenticated webhook to an endpoint you control. These tools help frame an integration conversation; they are not a Gruv API reference or production sandbox.
Public developer tools
Available without an account
Generic payload builder
Draft and copy JSON in your browser
- Generic fields
- No live request
- No authentication
Webhook simulator
Send a preset event to your endpoint
- Preset JSON
- Unauthenticated
- Status and latency
Production schemas, authentication, and sandbox access are not published on this page.
Public tools
Use the tools for the job they actually do
Both tools are available without a Gruv account. Each page states its limits before you use the output in a real integration.
Generic payload builder
Choose a payment-shaped example, fill its required fields, preview the JSON, and copy it from your browser.
Generic fields · no live API call · no authentication
Open resourceWebhook simulator
Choose a preset event, send its JSON to your endpoint, and inspect the status, latency, and response body.
Preset events · unauthenticated · HTTP or HTTPS endpoint
Open resourceProduction integration
Bring a clear question before you ask for access
This page does not publish OpenAPI downloads, SDK packages, authentication steps, production endpoint references, or public sandbox credentials. Use the public tools to define what you need, then ask Gruv what is available for that workflow.
Integration patterns
See illustrative file, API, webhook, batch-event, and export patterns with visible maturity labels.
Public product context
Open resourceAsk an integration question
Tell Gruv which workflow and system you are evaluating, then ask what schema or access can be shared.
Contact request · not instant sandbox access
Open resourceWhat the tools leave open
proof
The webhook simulator sends one preset JSON event through a server-side proxy to an address you enter, and reports the status, the latency and the body that came back. That is worth doing. It tells you the endpoint is reachable from outside your own network, that it parses a body it was not expecting, and how a request fares through your load balancer, read against your own logs.
It is worth being equally clear about what it cannot tell you. Nothing is signed, so signature checking goes untested. The request arrives from the proxy, so an address allowlist proves nothing here. One event sent once says nothing about what your handler does with the same event twice.
the reference
"There is no API reference here, so there is nothing to evaluate." The first half is accurate. This page publishes no endpoints, no authentication steps and no schema.
The second half is worth arguing with, because a field list is rarely what costs the engineering time. What costs it is the state machine: which states a record can hold, which transitions are legal, which are terminal, and what happens to a record that is accepted and then fails afterwards.
A schema names fields and answers none of that. Ask instead for the list of states and reason codes, and for one worked example of a record that failed after acceptance.
the amount
The payload builder gives you a generic amount and a currency code. The shape is right. The thing that breaks an integration sits one level below it.
ISO 4217 assigns every currency a minor-unit exponent: two for most, zero for the Japanese yen, three for the Kuwaiti dinar. Code that multiplies every amount by a hundred sends a tenth of the intended amount to Kuwait and a hundred times too much to Japan. Nothing in either request is malformed. A number in the right field is all either side agreed to check, so nothing on the way in raises an error.
The standard is not the last word either: at least one large processor documents its own table, differing from ISO for a handful of currencies, and tells integrators to follow that instead.
Frequently Asked Questions
Is this a Gruv API reference?+
Does the payload builder match the Gruv API?+
What does the webhook simulator send?+
Are sandbox credentials available on this page?+
Where can I review integration options?+
Have a concrete integration question?
Tell Gruv which workflow, system, and data exchange you are evaluating. The team can confirm what public information or additional access is available.
