Your First API Call

First follow the wallet_request setup in Quickstart to prepare the tools, Base URL/API Key/HMAC key environment variables, and shell function. Run the requests below in that same shell.

Start with the public server-time endpoint.

curl -sS "$WALLET_BASE_URL/time" | jq

Confirm success: true and compare the returned server time with the caller clock. Then use the prepared wallet_request helper or your HMAC client to call a protected endpoint.

wallet_request GET '/networks?is_active=true&page=1&page_size=20' | jq

A successful response uses the common envelope:

{
  "success": true,
  "data": { "items": [], "page": 1, "page_size": 20, "total": 0 },
  "error": null
}

Always verify both HTTP status and the body-level success. On failure, record error.request_id, error.code, and error.action without logging credentials.

Next, query an asset type and its supported networks before creating customer resources.

Validate the returned contract

Check that data.items is an array, numeric IDs can be stored without precision loss, boolean activation fields are preserved, and UTC timestamps are parsed without applying an unintended local timezone.

Run one negative test with a deliberately stale timestamp in a disposable environment. The response should use HTTP 401 with INVALID_TIMESTAMP and an action that directs the caller to synchronize time. Do not perform negative authentication tests against production without coordination.

Your first-call integration is complete when the service records the safe request metadata, exposes the upstream request_id for diagnostics, and converts neither IDs nor money strings to imprecise JavaScript numbers.