Connect to the
RAXIO API.

Follow every step.

Choose a path and explore its requests, results and events. Change the outcome to see how the operation and balances respond.

One operation. One signed record.

Every completed operation has a signed receipt. Verify its origin and integrity, keep a copy, and track its individual registration on Base.

Example · sandbox

Withdrawal received

250.00USD

Operation completed

Receipt fingerprint · SHA-256

Loading signed receipt…

Receipt details

Operation reference

—

Receipt reference

—

Settlement time

—

Signing key · Ed25519

—

Base registration

—

Check the signature yourself.

This example is signed by RAXIO. Your browser checks the receipt against the public key from this API origin.

1. Operation completedThe settlement has its own transfer reference.
2. Receipt signedAmounts, reference and time are protected by the signature.
3. Individual registration on BaseChecking publication status…

Verify receipt ↗Download JSON ↓

Loading the signed example and trusted public key…

Try changing the amount

Receipt verification checks the signature and fingerprint. Blockchain registration has a separate status.

For your operations, use the authenticated proof endpoint. The integration kit includes an independent Node.js verifier.

GET /v1/casino/operations/{operationId}/proof
node verify-receipt.mjs receipt.json <known RAXIO HTTPS origin>

Your first API request

Use the Postman collection or download the Node.js example. Configure your client with the API key, secret and merchantId supplied for your integration.

Create a local .env.raxio file with your assigned values:

RAXIO_BASE_URL=<this site's HTTPS origin>
RAXIO_API_KEY=<your-api-key>
RAXIO_API_SECRET=<your-api-secret>
RAXIO_MERCHANT_ID=<your-merchant-id>

Download the client and run it with Node.js:

curl --fail --silent --show-error "<this site's HTTPS origin>/example.mjs" --output raxio-example.mjs
node --env-file=.env.raxio raxio-example.mjs

Postman: import the collection, set baseUrl to the URL above, and store raxioApiKey, raxioApiSecret and merchantId locally. Run the main wallet journey in order. Keep runId for retries; clear it for a new journey.

Authenticate every API request

All /v1/ routes require the four headers below. POST requests also require a stable Idempotency-Key. Health and downloadable reference files are public.

timestamp.METHOD.path-and-query.nonce.sha256(rawBody)

# Use the exact transmitted bytes
timestamp.POST./v1/casino/withdrawals.nonce.bodyHash

The signature includes the query string and exact request body. Do not parse and reserialize JSON after signing. The secret is text: do not hex-decode it. A business retry keeps its idempotency key and external transaction reference, but uses a new timestamp, nonce and signature.

Endpoints

Expand an endpoint for its request, fields and response schema.

Receive signed callbacks

Operation status and callback delivery are tracked independently. Replaying an event never repeats a debit or credit.

Callbacks use the HTTPS URL registered for your integration. Verify the signature over the original body with your webhook signing secret, then deduplicate by eventId. The event keeps the same identity across delivery attempts.

GET  /v1/sandbox/events
POST /v1/sandbox/events/{eventId}/deliver

X-Raxio-Event: {eventId}
X-Raxio-Key: {integration key}
X-Raxio-Timestamp: {unix milliseconds}
X-Raxio-Nonce: {fresh nonce}
X-Raxio-Signature: {webhook HMAC-SHA256}

An external deposit in the sandbox uses txHash: "test_tx_…". Internal movements use a transfer reference. Use a fresh idempotency key when requesting another delivery attempt.

Parameters & limits

Rate limits are 120 requests per minute per IP and 300 per minute per credential. Idempotent retries reuse the same operation; delivery retries reuse the same event identifier.