Look up the accounts this LA already holds for an investor on an asset

The asset node asks the LA which network accounts it already associates with
finId on (organizationId, assetId) — e.g. wallets whitelisted directly on the
adapter or its external system. The LA answers with the full array. Nothing is
created and no challenge is ever issued. An empty array is a successful, empty
result.

Return production wallets only. The array must contain the investor's real
accounts on this asset — the ones the adapter actually holds or has whitelisted for
that investor. Never return test, placeholder or freshly generated wallets. Every
returned wallet is bound on the router as an onboarded network account for the
investor on (organizationId, assetId), replacing whatever the router previously
held for that pair, and will be accepted on the investor's execution legs. Return an
empty array if the adapter holds none.

Two response shapes, both 202:

  • isCompleted: true — the result is inline in accounts.
  • isCompleted: falsecid is returned and the result arrives on
    GET /operations/status/{cid} (or the callback, per operationResponseStrategy)
    as networkAccountOperation.accounts.

A ledger adapter that does not support lookup answers 501; the asset node fails the
operation with a terminal business error (7352).

Body Params

Body for POST /accounts/lookup. Same identification triple as CreateAccountRequest;
no wallet is supplied — the LA reports the accounts it already holds for the investor.

string
required
.*\S.*
string
required
.*\S.*
string
required
length between 64 and 66
^[0-9a-f]*$

The investor whose adapter-held accounts are looked up (see CreateAccountRequest.finId).

Headers
string
required

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

Response

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