Ask

Send a message to Zaira and immediately receive an execution ID. The answer can be polled manually using the execution UUID, or if configured, it will be delivered via webhooks.

This endpoint requires x-bakkt-api-key in addition to x-api-key, for every user. Self-custody users (those without a Bakkt custodial wallet) must additionally send x-bakkt-session-id on every request, because Zaira acts through the user's own Bakkt session rather than signing with a wallet it holds. When x-bakkt-session-id is supplied, Zaira resolves the user from that session and x-user-uuid may be omitted.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required

Session ID. Zaira supports multiple sessions per user without sharing context, so the user can manage their sessions.

string
required

User request for Zaira.

string

Base64-encoded image so Zaira can OCR to extract details (e.g. transfer recipient account data).

Headers
uuid

User UUID returned from /initiate. Required unless x-bakkt-session-id is supplied, in which case Zaira identifies the user from that Bakkt session instead.

string
required

Bakkt API key. Required on every request to this endpoint.

string

Active Bakkt session ID of the user. Required on every request for self-custody users (users with no Bakkt custodial wallet). Not needed for custodial users, for whom Zaira signs in with the stored wallet.

string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json