> Guveno API reference v1.10.0, last updated October 17, 2026. The whole reference is at https://www.guveno.com/llms-full.txt.

## Introduction

The Guveno API is a JSON-over-HTTPS interface for managing your crypto wallets. Create wallets, watch balances and transactions, and prepare and broadcast withdrawals straight from your own systems.

### The five things to know

If you skim everything else, keep these five:

- Every request carries an API key: `Authorization: Bearer gv_live_...`.
- Amounts are decimal strings in whole units (`"1.5"` ETH), never floats.
- Money in: register a webhook and credit a balance only on `deposit.confirmed` (see **Webhooks**).
- Money out: prepare → sign → broadcast, with an `Idempotency-Key` on each call. Signing always happens on your side (see **Withdrawals**).
- Guveno never holds spendable keys. Lose your recovery phrase and passphrase, and nobody can recover the funds (see **How wallets work**).

### Base URL

All requests go over HTTPS and exchange `application/json`.

```
https://api.guveno.com/v1
```

If you run a self-hosted Guveno server, use your own host with the same `/v1` path.

### Conventions

- Authentication is a bearer token on every request (see Authentication).
- Timestamps are ISO-8601 in UTC, e.g. `2026-06-14T12:00:00.000Z`.
- Resource IDs are integers; list endpoints paginate with an opaque `cursor`.
- Amounts are decimal strings in whole units (never floats), to preserve precision.

### Quick start

- **1.** [Log in to the dashboard](https://dashboard.guveno.com/login). New to Guveno? [Sign up](https://dashboard.guveno.com/signup). The Developer tier is free on testnets, and sign-ups are by referral right now, so [ask us for a code](https://www.guveno.com/contact/) if you don't have one.
- **2.** Create an API key under **Developer → API Keys** and scope it to the wallets and actions it needs.
- **3.** Check the key works:

```
curl https://api.guveno.com/v1/me \
  -H "Authorization: Bearer gv_live_your_key_here"
```

It answers with the account the key belongs to: `id`, `email`, the optional `firstName` and `lastName` its owner set in the dashboard, the company membership and your encryption key. The two name fields are cosmetic and stay `null` until someone fills them in.

- **4.** List the wallets it can see:

```
curl https://api.guveno.com/v1/wallets \
  -H "Authorization: Bearer gv_live_your_key_here"
```

From here, go where your integration goes: receiving money is **Webhooks**, sending money is **Withdrawals**, and if you'd rather not hand-roll HTTP, the **Node.js** and **Python** SDKs wrap all of it.

Source: https://www.guveno.com/docs/