Privy Link

Backfill the signed-in account's wallet from a fresh Privy token.

Privy mints the embedded wallet during the first login, so the token that login exchanged names no wallet and the account was created without one — and since the exchange happens once per sign-in, it stayed missing for the whole session. The web calls this as soon as the SDK reports a wallet, and gets the updated session back so the address chip fills in without a reload.

A session mutation, so it takes CSRF like every other one, and the service refuses a token whose subject is not this session's account.

post/v1/auth/privy/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/privy/link
  • Auth: none declared

Request body

access_tokenstring 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.