Wallet Link

Backfill the signed-in account's wallet from a signed challenge.

The Privy backfill above needs an identity token, which a Privy app can simply never issue (a dashboard setting) — but the embedded wallet can still sign, and a signature over this server's own challenge is the proof a wallet sign-in already accepts. Fill-empty only: an account that has a wallet keeps it.

A session mutation, so it takes CSRF like every other one.

post/v1/auth/wallet/link

Request

  • Base URL: https://api.app.membase.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.app.membase.ai/v1/auth/wallet/link
  • Auth: none declared

Request body

messagestring required
signaturestring required
invite_codestring

Response

Successful Response

account_idstring required
methodstring required
expires_atstring required
csrf_tokenstring required
rolestring nullable
emailstring nullable
display_namestring nullable
walletstring nullable

Changes

No recorded changes to this operation across all 1 revision of this API.