Getting started
Sign wallet actions and recover an agent order
Keep one private workspace across restarts, authorize agent or customer funds, and recover a submitted trade when an HTTP response goes missing.
Workflow
Keep the identifiers before you trade
The SDK creates a workspace with new BitpontClient(). Save client.workspace in the host’s secret store, then restore it with new BitpontClient({workspace}) after restart. A REST client can POST an empty JSON object to /api/v1/agent/workspace and retain data.workspace for the X-Bitpont-Workspace header. Assign one persistent requestId UUID to each intended action.
Review the exact authority
Select a supported action from executionRoutes, call executionPrepare and inspect the returned network, asset, amount, fee, destination and expiry. On the wallet host call bitpont_walletReview then bitpont_walletExecute with the executionId, or sign locally and call executionSubmit. For customer custody, sessionPrepare names the exact unsubmitted ticket IDs. The customer reviews the payloads and signs the session approval before activation.
Resume the same ticket
If preparation timed out, call executionLookup with the original requestId in the same workspace. After submission, use executionStatus with its executionId and save the returned chain or venue reference. Use executionReceipts to locate earlier submissions after restart. Check the venue fill or chain receipt before creating another order.
List the available signing routes
curl -fsS "https://www.bitpont.com/api/v1/agent/execution/routes"