> ## Documentation Index > Fetch the complete documentation index at: https://docs.blockradar.co/llms.txt > Use this file to discover all available pages before exploring further. # Child Address Broadcast Transaction > Sign and broadcast a raw unsigned transaction from a child address. The transaction is signed and submitted on chain via a queue with automatic retries. Returns PENDING status with webhook notification on completion. ## OpenAPI ````yaml post /v1/wallets/{id}/addresses/{addressId}/signing/broadcast openapi: 3.0.3 info: title: Blockradar Documentation description: >- The OpenAPI specification of the Blockradar API that enables fintechs and developers to seamlessly integrate stablecoin deposits and payments into their products. version: 1.0.0 contact: {} servers: - url: https://api.blockradar.co security: - apiKey: [] tags: - name: Rewards description: >- Non-custodial yield (Earn) on stablecoins via regulated (Fija) and DeFi (Aave) strategies. Deposit, withdraw, preview fees, and read positions and earnings at the business, wallet, and sub-address level. Amounts are returned net of the platform fee, which applies only to interest earned. - name: Wallet description: >- Wallet Management System Comprehensive wallet management API for multi-blockchain operations. This system handles wallet creation, configuration, balance monitoring, and integration with various blockchain networks. Core Functionality: - Multi-blockchain wallet creation and management - Balance monitoring and asset tracking - Auto-settlement rule configuration - Gateway wallet integration - Address generation and management - Transaction monitoring and processing - name: Addresses description: >- Address Management System Comprehensive blockchain address management API for operations. This system handles address creation, validation, monitoring, and management across multiple blockchain networks. Core Functionality: - Multi-blockchain address generation - Address validation and verification - Balance monitoring and tracking - Transaction history management - Address labeling and organization - Integration with wallet systems - Real-time address monitoring - name: Asset - name: Transactions - name: Withdraw description: >- The Withdraw feature allows you to programmatically withdraw stablecoins from your master wallet with ease - name: Withdraw Fiat - name: Signing description: >- Typed data signing service for secure transaction authorization. Supports all EIP-712 standards including EIP-3009 (TransferWithAuthorization) and EIP-2612 (Permit). - name: Swap description: >- The Swap feature enables users to exchange one stabelcoin asset for another across different blockchains. This feature provides a seamless way to convert between different stablecoins while maintaining security and compliance standards. - name: Liquidity Pool - name: Virtual Accounts description: >- Virtual Accounts API provides endpoints for managing virtual bank accounts linked to master wallets or child addresses. This API enables businesses to: - Create virtual accounts for customers to receive payments - Retrieve virtual account details - Activate/deactivate virtual accounts **Virtual Account Types:** Virtual accounts support different types with varying behaviors: 1. **AUTO_FUNDING** (Default): - Automatically mints stablecoin when fiat payments are received - Transfers the stablecoin to the linked wallet/address immediately - Best for real-time payment processing **How It Works - Auto-Funding Flow (AUTO_FUNDING type only):** When a customer sends fiat currency to a virtual account with type AUTO_FUNDING: 1. **Payment Receipt**: The payment is received in the virtual account 2. **Automatic Minting**: The system automatically mints the stablecoin equivalent 3. **Blockchain Transfer**: The minted stablecoin is transferred to the virtual account's linked wallet or address **Note**: The auto-funding flow only applies to virtual accounts with type `AUTO_FUNDING`. Other types have different processing behaviors. ## Prerequisites Before creating virtual accounts, ensure: - **Compliance requirements must be completed** (see [Compliance Requirements](http://localhost:3000/essentials/virtual-accounts#compliance-requirements) section below) - **Virtual accounts feature must be enabled** for your business (reach out to [support@blockradar.co](https://mailto:support@blockradar.co) or use live chat on the dashboard to enable the feature after compliance approval) - **Only available on MAINNET environment** (not available on testnet) - **Master Wallet must support stablecoin asset** - Your account plan must include stablecoin access (upgrade from Dashboard → Settings → Subscription if needed) **Supported Currency:** - Fiat: NGN (Nigerian Naira) - Stablecoin: cNGN - minted automatically on blockchain (for AUTO_FUNDING type) - name: Auto Settlements description: >- Creates a new auto settlement rule for a wallet. Auto settlement automatically transfers/swap assets based on configured rules when certain conditions are met. Rules can be configured for: - Source blockchain and assets - Destination blockchain and asset - Amount ranges (min/max) - Slippage tolerance - Gateway vs non-gateway wallets Gateway rules are required for testnet wallets and must have matching source/destination assets. - name: Smart Contract description: >- This API provides endpoints for interacting with smart contracts on the blockchain. It allows for reading contract data, executing contract functions, and estimating network fees. - name: Gateway description: >- The Gateway feature enables you to programmatically deposit USDC into a unified, chain-abstracted balance and instantly mint USDC on any supported blockchain, streamlining crosschain transfers and eliminating manual bridging steps and rebalancing complexities. - name: Payment Links description: >- The Payment Pages API provides a quick and secure way to collect payment for servcies. - name: Beneficiaries description: >- This API allows you to create beneficiaries with automatic settlements to your external wallets on a periodic basis. Example frequencies: INSTANT, DAILY, WEEKLY, MONTHLY, YEARLY - name: AML description: >- The AML (Anti Money Laundering) API provides a quick way for you to check if an address is blacklisted or sanctioned - name: Asset Recovery description: >- Enables the recovery (salvage) of both native blockchain assets and tokens from a specified sender address to a recipient address. This feature supports emergency fund recovery and asset consolidation operations. - name: Miscellaneous description: >- The Miscellaneous API are supporting APIs that can be used to provide more details to other APIs. - name: Asset1 - name: Blockchain - name: Webhooks description: >- Webhooks allow you to set up a notification system that can be used to receive updates on certain requests made to the Blockradar API. To see full list and instructions [https://docs.blockradar.co/essentials/webhooks](https://docs.blockradar.co/essentials/webhooks) ## - name: Deposit - name: Withdraw1 - name: Swap1 - name: Gateway1 paths: /v1/wallets/{id}/addresses/{addressId}/signing/broadcast: post: tags: - Signing summary: Child Address Broadcast Transaction description: >- Sign and broadcast a raw unsigned transaction from a child address. The transaction is signed and submitted on chain via a queue with automatic retries. Returns PENDING status with webhook notification on completion. operationId: childAddressBroadcastTransaction parameters: - name: id in: path required: true schema: type: string example: YOUR_WALLET_ID - name: addressId in: path required: true schema: type: string example: ADDRESS_OR_ID requestBody: content: application/json: schema: type: object required: - transaction properties: transaction: type: string description: >- The serialized unsigned transaction. Base64 for Solana, JSON string for EVM and Tron. example: >- AQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA... reference: type: string description: Your internal tracking ID. example: sol-child-broadcast-001 metadata: type: object description: Custom key-value pairs stored with the transaction record. example: source: jupiter responses: '201': description: Transaction signed and broadcast initiated content: application/json: schema: type: object properties: statusCode: type: number example: 200 message: type: string example: Transaction signed and broadcast initiated data: type: object properties: id: type: string example: f3efdbaa-a1f8-4365-b3b4-768413c9a92b reference: type: string example: sol-child-broadcast-001 senderAddress: type: string example: 6NkEUDPS6TBkP1VSc2SZVRdtuARUFhQvMRz28RonytUG recipientAddress: type: string example: 6NkEUDPS6TBkP1VSc2SZVRdtuARUFhQvMRz28RonytUG hash: type: string example: >- 5bKNw9RX8aXkrK1VEHg5aPa1xtckpShPyenSRET4mUBXh5uCkWLFV5MhGRi4cMACDJvFn6VfkoKb75Pk4KYw6xtw confirmed: type: boolean example: false status: type: string example: PENDING type: type: string example: SIGNED createdChannel: type: string example: api reason: type: string example: Transaction signed and broadcast network: type: string example: testnet chainId: type: number example: 103 metadata: nullable: true example: null signedTransaction: type: string description: >- The signed transaction. Base64 for Solana, hex for EVM, JSON string for Tron. example: >- AeWpW65y80rSu+TU0CSrcvFNovyDiybKRjSskCpfffAFLM0GIYzx... amount: nullable: true example: null amountUSD: type: string example: '0.00' fee: nullable: true example: null feeUSD: nullable: true example: null currency: type: string example: USD createdAt: type: string example: '2026-03-19T13:35:09.921Z' updatedAt: type: string example: '2026-03-19T13:35:09.921Z' wallet: type: object properties: id: type: string example: c72a6f21-6ab5-48ad-9f99-fd90a2d6d311 name: type: string example: Solana Testnet Wallet address: type: string example: HKqZUT3wuyJrsPYmrYPcGduDdjXZTggbLrNsF9WHMvbw isActive: type: boolean example: true status: type: string example: ACTIVE network: type: string example: testnet asset: nullable: true example: null blockchain: type: object properties: id: type: string example: 196badf5-380f-4480-ab4a-d0e4304e91f0 name: type: string example: solana symbol: type: string example: sol slug: type: string example: solana isEvmCompatible: type: boolean example: false tokenStandard: nullable: true example: null beneficiary: nullable: true example: null '400': description: Invalid transaction format content: application/json: schema: type: object properties: statusCode: type: number example: 400 message: type: string example: >- Invalid transaction format: expected a base64-encoded Solana VersionedTransaction components: securitySchemes: apiKey: type: apiKey name: x-api-key in: header ````