For the complete documentation index, see llms.txt. This page is also available as Markdown.

Recipient Info

Get the caller's shielded recipient handle

get

Returns a recipientInfo handle that other users pass to /transfer or /deposit-for-other (EVM/Tron) or /deposit-solana-for-other (Solana) to send funds to this wallet's shielded balance. Read-only — requires an active session. Pass sessionId and nonce as query parameters and include x-hinkal-request-signature: secp256k1_sign(SHA256("GET /recipient-info\n" + queryString)).

Query parameters
sessionIdstring · uuidRequired

Session identifier UUID from POST /create-session

Example: ffd74231-0672-48c7-bd82-9f72a803578b
noncestring · uuidRequired

Per-request UUID. Echoed back in the response.

Example: 0d147d06-b91d-48ce-a01e-f4bd9875c852
chainIdstringRequired

Chain ID (e.g. 10 for Optimism, 501 for Solana mainnet)

Example: 10
Header parameters
x-hinkal-request-signaturestringRequired

Hex-encoded compact secp256k1 signature: secp256k1_sign(SHA256(binding + "\n" + payload)), where binding is "<METHOD> <routePath>" (this route's own method and path, e.g. "POST /refresh-cache" or "GET /balance") and payload is JSON.stringify(body) for POST requests or the raw query string for GET requests. Binding the route into the signed digest stops a signature captured for one endpoint from being replayed against another. See Authentication for the full signing scheme.

Responses
200

Recipient handle

application/json
get/recipient-info
GET /recipient-info?sessionId=ffd74231-0672-48c7-bd82-9f72a803578b&nonce=0d147d06-b91d-48ce-a01e-f4bd9875c852&chainId=10 HTTP/1.1
Host: api.hinkal.io
x-hinkal-request-signature: text
Accept: */*
{
  "success": true,
  "recipientInfo": "0x8e4a7f9c2b3d5a1e6f8c4b2d9a7e5f3c1b4d6a8e2f4c6b8a2d4f6c8e1b3d5a7",
  "nonce": "0d147d06-b91d-48ce-a01e-f4bd9875c852"
}

Last updated