Wallets

Authenticate wallet session scoped to intents

Exchange a user JWT for a session key scoped to specific intents. The returned USK can only authorize the bound intents and cannot sign other RPC requests.

post/v1/wallets/authenticate/intents

Headers

privy-app-idstring required

ID of your Privy app.

Request body

OR

Response

Object with authorization key, wallet IDs, and the bindings the key is scoped to.

OR

Example response

{
  "wallets": [
    {
      "additional_signers": [],
      "address": "0xF1DBff66C993EE895C8cb176c30b07A559d76496",
      "archived_at": null,
      "chain_type": "ethereum",
      "created_at": 1741834854578,
      "display_name": "Treasury",
      "exported_at": null,
      "external_id": "my-order-123",
      "id": "id2tptkqrxd39qo9j423etij",
      "imported_at": null,
      "owner_id": "rkiz0ivz254drv1xw982v3jq",
      "policy_ids": []
    }
  ]
}

Changes

Changed in 3 of the 46 revisions of this API.4

    • added the optional property anyOf[subschema #1: EncryptedBoundAuthenticateResponse]/wallets/items/archived_at to the response with the 200 status

      response-optional-property-added

    • added the optional property anyOf[subschema #2: RawBoundAuthenticateResponse]/wallets/items/archived_at to the response with the 200 status

      response-optional-property-added

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • api operation id authenticateIntents removed and replaced with createIntentBoundSigningKey

      api-operation-id-removed

    • endpoint added

      endpoint-added