HomeGuidesAPI Reference
API Reference

Create or bind an investor account on this LA (Phase 1)

post
https://example.com/accounts/create

Single LA-side endpoint covering both flows:

  • Create new — bindInfo is absent. The LA generates a fresh wallet on the
    asset's network.
  • Bind existing — bindInfo carries the caller-supplied networkAccount
    and ownershipSignature (proof-of-ownership hint).

The LA issues a challenge (signatureTemplate / walletConnect / deposit /
fireblocksApproval / …) which the user must fulfill. Two response shapes:

  • 207 Multi-Status — challenge ready immediately; body has challenge and
    operationResponseStrategy.
  • 202 Accepted — LA needs more time; body has cid and
    operationResponseStrategy. Asset node polls or awaits callback per strategy;
    the challenge arrives via GET /operations/status/{cid}.

The ledger.accounts.wallets jsonb column is updated only after challenge verification.

Body Params

Body for POST /accounts/create. Single LA-side endpoint covering both create-new
and bind-existing flows.

  • Create new — omit bindInfo. The LA generates a wallet on the asset's network.
  • Bind existing — populate bindInfo with the caller-supplied wallet and a
    proof-of-ownership signature hint. The LA still issues a challenge for final verification.

The response is either 207 (challenge ready) or 202 (challenge pending) — see the
endpoint definition.

string
required
.*\S.*
string
required
.*\S.*
bindInfo
object

Bind-info block. When present in CreateAccountRequest, signals the bind-existing flow.

Headers
string
required

hex encoding of a 32-byte payload consisting of 24 random bytes + 8-byte epoch timestamp (seconds)

Responses

Updated 7 days ago

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

Updated 7 days ago