Skip to Content
Pyxis Docs

Wallet events

The event allowlist, limits and response of POST /v1/wallet-events.

POST /v1/wallet-events accepts a JSON body { "events": [ ... ] }. The validator is a strict allowlist: any unknown property (an address, a signature, XDR) rejects that event.

Events

EventMeaning
wallet_connect_startedThe user began connecting a wallet
wallet_connectedThe wallet connected
wallet_disconnectThe wallet disconnected
transaction_sign_startedA signing request was shown
transaction_sign_completedThe user signed
transaction_sign_failedSigning failed or was rejected
transaction_submit_startedSubmission began
transaction_submit_completedSubmission reported success
transaction_submit_failedSubmission reported failure

Properties

PropertyAllowed values
eventOne of the events above (required)
wallet_providerfreighter, xbull, albedo, lobstr, rabet, hana, ledger, hot_wallet, other. Anything else becomes other
networktestnet, public, other. Anything else becomes other
failure_categoryLowercase letters and underscore, 1 to 32 characters
flow, sdk_version, tsAccepted but not stored. The server always uses its own time

Limits and response

FactDetail
BatchAt most 50 events; body at most 20,000 characters
Status200 even when events are rejected; the body is { "accepted": n, "rejected": [{ "index": i, "reason": "..." }] }
Reject reasonsnot_an_object, prohibited_property, unknown_event, bad_failure_category
Batch errors400 events_array_required, 400 batch_too_large, 413
StoredCounts per project, minute, event, provider category and network only

Reported, not verified

Events come from the browser. They are never proof that a transaction reached the ledger.

On this page