Make Your First Request

Use this guide after creating an API application, storing the one-time API key, and preparing a request-signing helper from Request Signing. You need the CRYPTO_READ permission for the signed REST request below.

Check the public health endpoint

The health endpoint is not part of the signed Partner REST surface. Use it only as a connectivity check.

curl https://rest-api.nuvera.global/health

A healthy API returns a small JSON response with status set to ok.

Generate a signed request JWT

For GET /api/v1/crypto/networks, generate a JWT immediately before the request with:

JWT input	Value
`method`	`GET`
`uri`	`/api/v1/crypto/networks`
`bodyHash`	SHA-256 of an empty body

Nuvera does not ship a CLI. Use your own helper built from Request Signing.

Call a low-risk signed endpoint

TOKEN="<signed-request-jwt>"

curl https://rest-api.nuvera.global/api/v1/crypto/networks \
  -H "x-api-key: $NUVERA_API_KEY" \
  -H "Authorization: Bearer $TOKEN"

This confirms that the API key, permission, public key, private key, JWT claims, and request URI all line up.

Common first-request failures

Symptom	Check
`401 Unauthorized`	Confirm `x-api-key` is present and is the raw one-time key value.
`401 Unauthorized`	Confirm the JWT `sub` matches the exact API key sent in `x-api-key`.
`401 Unauthorized`	Confirm `exp` is no more than 60 seconds after `iat` and has not expired.
`401 Unauthorized`	Confirm `uri` is exactly `/api/v1/crypto/networks`, including any query string if present.
`403 Forbidden`	Confirm the API application has `CRYPTO_READ`.

For full endpoint schemas, open the API Reference. For deeper auth troubleshooting, see Troubleshooting.

Getting Started

Partner API

Core Workflows

Operations

Make Your First Request

Common first-request failures

​Common first-request failures

Common first-request failures