Skip to main content
Developer evaluation resources

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

Evaluation only

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.

Production 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.

What 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?+
No. This page links to public evaluation tools and product context. It does not publish production endpoints, authentication instructions, or a complete Gruv API schema.
Does the payload builder match the Gruv API?+
No. The builder uses generic payment fields so you can draft and copy JSON in your browser. Map the output to a verified production specification before using it in an integration.
What does the webhook simulator send?+
It sends one of several preset, unauthenticated JSON events through a server-side proxy to the HTTP or HTTPS endpoint you enter. It returns the response status, latency, and body.
Are sandbox credentials available on this page?+
No public sandbox credentials are provided here. Contact Gruv to ask what environment, schema, and access may be available for the workflow you are evaluating.
Where can I review integration options?+
Start with the integrations page. Its named connection patterns are illustrative and carry visible maturity labels. Confirm the method, direction, fields, authentication, and availability for your setup.

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.