Wallets

Authenticate wallet session scoped to intents

Changed on

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

Request

  • Base URL
    https://api.privy.io
  • URL
    https://api.privy.io/v1/wallets/authenticate/intents
  • Auth
    HTTP basic

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": [
    {
      "id": "id2tptkqrxd39qo9j423etij",
      "address": "0xF1DBff66C993EE895C8cb176c30b07A559d76496",
      "display_name": "Treasury",
      "external_id": "my-order-123",
      "chain_type": "ethereum",
      "policy_ids": [],
      "additional_signers": [],
      "owner_id": "rkiz0ivz254drv1xw982v3jq",
      "parent_wallet_id": null,
      "entity": {
        "id": "jorpjo4rfxj62nx1itt8y1zt",
        "type": "user"
      },
      "created_at": 1741834854578,
      "exported_at": null,
      "imported_at": null,
      "archived_at": null
    }
  ]
}

Changes

    • warning

      added the new xrpl enum value to the /// response property for the response status

    • warning

      added the new xrpl enum value to the /// response property for the response status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status

    • info

      the /// response's property pattern ^[a-zA-Z0-9_-]+$ was added for the status

    • info

      the /// response's property pattern ^[a-zA-Z0-9_-]+$ was added for the status

    • info

      added the optional property /// to the response with the status

    • info

      added the optional property /// to the response with the status