> ## Documentation Index > Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt > Use this file to discover all available pages before exploring further. # Broadcast a user operation > Attaches a signature to a user operation and submits it to the bundler. The user operation can be the one `build-user-operation` returned, or one you built yourself for the client's smart account (EntryPoint v0.6, ZeroDev Kernel v2). Pass the signature exactly as the raw signing endpoint returned it; Portal formats it for the smart account. Returns the user operation hash; look it up with the get transaction endpoint for the on-chain transaction hash once a bundler includes it. ## OpenAPI ````yaml /openapi/client-api.yaml post /clients/me/chains/{chain}/assets/send/broadcast-user-operation openapi: 3.1.0 info: title: Portal Client API version: '3.0' description: > The Portal Client API provides endpoints for managing wallets, building transactions, and interacting with blockchain networks. All endpoints require authentication via a Client API Key or Client Session Token (CST) passed as a Bearer token. ## Base URL `https://api.portalhq.io/api/v3` ## Authentication Include your Client API Key or Client Session Token as a Bearer token in the `Authorization` header of every request. ## Chain ID Format Chain parameters use either friendly names (e.g. `ethereum`, `solana`) or CAIP-2 format (e.g. `eip155:1`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`). When using CAIP-2 format in URLs, ensure the colon is URI-encoded (`%3A`). servers: - url: https://api.portalhq.io/api/v3 description: Production security: - bearerAuth: [] tags: - name: Clients description: Core client management endpoints - name: Wallet description: >- Read wallet state — balances, NFTs, transaction history, capabilities, and transaction details - name: Transactions description: Build, broadcast, and evaluate blockchain transactions - name: Funding description: Fund wallets with testnet tokens - name: Wallet Shares description: Manage signing and backup share pairs - name: Delegations description: Manage token approvals, revocations, and delegated transfers - name: Session Keys description: Manage EIP-7702 session keys for smart accounts - name: 0x description: Token swap endpoints powered by the 0x protocol - name: Yield.xyz description: Yield opportunities and staking actions powered by Yield.xyz - name: Yield.xyz Borrow description: >- Supply collateral, borrow, repay and withdraw from lending markets (Aave V3, Morpho Blue, SparkLend, Lista) powered by Yield.xyz Borrow - name: Yield.xyz Perps description: >- Trade perpetual futures — open/close leveraged positions, manage stop-loss/take-profit, and fund/withdraw a trading account — powered by Yield.xyz Perps - name: Li.Fi description: Cross-chain swaps and bridging powered by Li.Fi - name: Blockaid description: Transaction and address security scanning powered by Blockaid - name: Hypernative description: >- Transaction, address, token, and NFT security scanning powered by Hypernative - name: Noah description: KYC onboarding, payins, and payouts powered by Noah - name: Meld description: Buy and sell crypto with fiat through aggregated providers powered by Meld - name: Due description: Payins, payouts, virtual accounts, and FX powered by Due - name: EIP-7702 description: EIP-7702 account type detection and authorization management - name: Deprecated description: >- Legacy endpoints scheduled for removal. Use the newer equivalents listed in each endpoint's description. paths: /clients/me/chains/{chain}/assets/send/broadcast-user-operation: post: tags: - Transactions summary: Broadcast a user operation description: > Attaches a signature to a user operation and submits it to the bundler. The user operation can be the one `build-user-operation` returned, or one you built yourself for the client's smart account (EntryPoint v0.6, ZeroDev Kernel v2). Pass the signature exactly as the raw signing endpoint returned it; Portal formats it for the smart account. Returns the user operation hash; look it up with the get transaction endpoint for the on-chain transaction hash once a bundler includes it. operationId: broadcastUserOperation parameters: - $ref: '#/components/parameters/chain' requestBody: required: true content: application/json: schema: type: object required: - userOperation - signature properties: userOperation: oneOf: - type: string - type: object description: >- The user operation to submit, as a JSON string or an object. Either the `userOperation` from `build-user-operation`, unchanged, or one you built yourself for the client's smart account. Any `signature` it carries is replaced. signature: type: string description: >- The raw SECP256K1 signature of `userOpHash`, hex encoded, with or without `0x`. example: userOperation: >- {"sender":"0xF86e3fAe8443e4494a689fcDd4C8e6C76c1b2C96","nonce":"0x5",...} signature: >- 3e42da7cb2a70a00a3e1d565cbb75e2f1aca3f62183c3fc61da1d9f3f8dff6d5... responses: '200': description: User operation submitted to the bundler content: application/json: schema: type: object properties: data: type: object properties: userOpHash: type: string metadata: type: object properties: chainId: type: string example: data: userOpHash: >- 0xf82a8a15e20eec1c8c3057fc56df67d7da3dc668e2b0dd3c7380ddc9175867d1 metadata: chainId: eip155:11155111 '400': description: > Bad request. Common causes: - The client does not have Account Abstraction enabled - Missing `userOperation` or `signature`, or `userOperation` is not valid JSON - The bundler rejected the user operation content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized - invalid or missing authentication token content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: parameters: chain: name: chain in: path required: true description: > The blockchain chain identifier. Use either a friendly name or CAIP-2 format. When using CAIP-2 format in URLs, ensure the colon (`:`) is URI-encoded as `%3A`. **Supported chains:** - `ethereum` (`eip155:1`) - `sepolia` (`eip155:11155111`) - `base` (`eip155:8453`) - `base-sepolia` (`eip155:84532`) - `polygon` (`eip155:137`) - `polygon-mumbai` (`eip155:80001`) - `celo` (`eip155:42220`) - `celo-alfajores` (`eip155:44787`) - `monad` (`eip155:143`) - `monad-testnet` (`eip155:10143`) - `solana` (`solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`) - `solana-devnet` (`solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1`) - `tron` (`tron:mainnet`) - `tron-nile` (`tron:nile`) - `tron-shasta` (`tron:shasta`) - `stellar` (`stellar:pubnet`) - `stellar-testnet` (`stellar:testnet`) - `bitcoin-segwit` (`bip122:000000000019d6689c085ae165831e93-p2wpkh`) - `bitcoin-segwit-testnet` (`bip122:000000000933ea01ad0ee984209779ba-p2wpkh`) - `bitcoin-p2wpkh` (`bip122:000000000019d6689c085ae165831e93-p2wpkh`) - `bitcoin-p2wpkh-testnet` (`bip122:000000000933ea01ad0ee984209779ba-p2wpkh`) schema: type: string examples: ethereum: value: ethereum summary: Ethereum mainnet (friendly name) eip155: value: eip155:1 summary: Ethereum mainnet (CAIP-2) solana: value: solana summary: Solana mainnet (friendly name) bitcoin: value: bitcoin-segwit summary: Bitcoin segwit (friendly name) schemas: ErrorResponse: type: object properties: error: type: string description: Error message describing what went wrong securitySchemes: bearerAuth: type: http scheme: bearer description: > Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header. ````