> ## 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. # Submit a CCTP transfer > Tells Portal which transaction to track. Send exactly one of: - `txHash`: the burn transaction hash (`0x`), for EOA clients on an EVM source. For a Solana source, the base58 signature of the burn transaction, for every client including Account Abstraction clients. - `userOpHash`: the user operation hash, for Account Abstraction clients on an EVM source. Submitting the approve or a fee transfer hash instead of the burn hash ends the transfer as `FAILED` with `failureReason` `TX_MISMATCH`. A Solana signature that doesn't appear on chain within 30 minutes ends it as `FAILED` with `SOURCE_TX_NOT_FOUND`. Safe to retry: the same hash again returns the transfer. A different hash, or a hash already submitted for another transfer, returns `409` with the id `ALREADY_SUBMITTED`. A transfer marked `ABANDONED` still accepts a late submit. Works even if the integration was disabled after the transfer was created. ## OpenAPI ````yaml /openapi/client-api.yaml post /clients/me/integrations/cctp/transfers/{id}/submit 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: CCTP description: >- Crosschain USDC transfers powered by Circle's Cross-Chain Transfer Protocol (CCTP) - 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/integrations/cctp/transfers/{id}/submit: post: tags: - CCTP summary: Submit a CCTP transfer description: > Tells Portal which transaction to track. Send exactly one of: - `txHash`: the burn transaction hash (`0x`), for EOA clients on an EVM source. For a Solana source, the base58 signature of the burn transaction, for every client including Account Abstraction clients. - `userOpHash`: the user operation hash, for Account Abstraction clients on an EVM source. Submitting the approve or a fee transfer hash instead of the burn hash ends the transfer as `FAILED` with `failureReason` `TX_MISMATCH`. A Solana signature that doesn't appear on chain within 30 minutes ends it as `FAILED` with `SOURCE_TX_NOT_FOUND`. Safe to retry: the same hash again returns the transfer. A different hash, or a hash already submitted for another transfer, returns `409` with the id `ALREADY_SUBMITTED`. A transfer marked `ABANDONED` still accepts a late submit. Works even if the integration was disabled after the transfer was created. operationId: submitCctpTransfer parameters: - name: id in: path required: true schema: type: string description: The `transferId` from the create response. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/CctpSubmitRequest' examples: evm: summary: EVM source (EOA client) value: txHash: >- 0xc7c227eee90af289fceb0d33c66b472457c65b74811f2ba02a8ab21727496dfb solana: summary: Solana source value: txHash: >- 3GxLobzBKtFmQUrYEvgCbrcXHbJ6SsgZwiwyXP8TWJeWBeZUCeAU7D1tzqdZqFYr7VvLA41WXsvQuFMqgGjXBMhr responses: '200': description: Transfer submitted content: application/json: schema: $ref: '#/components/schemas/CctpTransferResponse' example: data: id: cmuzgyc2105hw41rg2h19pomm status: SUBMITTED sourceChain: eip155:84532 destinationChain: eip155:43113 amount: '0.09' amountOut: '0.035807' sender: '0xa7f0c09f250b7f9cc73068c02ceb296a013c0c0c' recipient: '0xa7f0c09f250b7f9cc73068c02ceb296a013c0c0c' speed: fast fees: maxFee: '0.054193' custodian: '0' totalDebit: '0.09' sourceTxHash: >- 0xc7c227eee90af289fceb0d33c66b472457c65b74811f2ba02a8ab21727496dfb sourceExplorerUrl: >- https://sepolia.basescan.org/tx/0xc7c227eee90af289fceb0d33c66b472457c65b74811f2ba02a8ab21727496dfb estimatedCompletionAt: '2026-10-08T11:44:54.347Z' pollAfterMs: 2000 createdAt: '2026-10-08T11:44:32.137Z' updatedAt: '2026-10-08T11:44:46.349Z' '400': description: > Bad request. Common causes: - The body has both or neither of `txHash` and `userOpHash`, `txHash` isn't a `0x` 32-byte hash or a base58 Solana signature, or `userOpHash` isn't a `0x` 32-byte hash - On an EVM source, an EOA client sent `userOpHash`, an Account Abstraction client sent `txHash`, or `txHash` isn't a `0x` hash - On a Solana source, the body has `userOpHash` or a `0x` `txHash` instead of the Solana signature content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Submit the txHash of the broadcast burn transaction '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: The transfer doesn't exist or belongs to another client. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: CCTP transfer does not exist. '409': description: >- The transfer was already submitted with a different hash, or the hash belongs to another transfer (`ALREADY_SUBMITTED`). content: application/json: schema: $ref: '#/components/schemas/CctpErrorResponse' example: error: This transfer was already submitted with a different hash id: ALREADY_SUBMITTED components: schemas: CctpSubmitRequest: type: object description: >- Send exactly one of `txHash` (EOA clients on an EVM source, and every client on a Solana source) or `userOpHash` (Account Abstraction clients on an EVM source). oneOf: - required: - txHash - required: - userOpHash properties: txHash: type: string pattern: ^(0x[0-9a-fA-F]{64}|[1-9A-HJ-NP-Za-km-z]{64,88})$ description: >- The burn transaction hash (`0x`, EVM source) or the base58 signature of the burn transaction (Solana source). Not the approve or a fee transfer hash. userOpHash: type: string pattern: ^0x[0-9a-fA-F]{64}$ description: The hash of the broadcast user operation. additionalProperties: false CctpTransferResponse: type: object properties: data: $ref: '#/components/schemas/CctpTransfer' ErrorResponse: type: object properties: error: type: string description: Error message describing what went wrong CctpErrorResponse: type: object required: - error properties: error: type: string id: type: string enum: - CCTP_NOT_ENABLED - INVALID_AMOUNT - IDEMPOTENCY_KEY_REUSED - CCTP_REBUILD_UNAVAILABLE - CCTP_REBUILD_TOO_SOON - ALREADY_SUBMITTED description: Stable error id. Absent on malformed request errors. details: type: object additionalProperties: true CctpTransfer: type: object properties: id: type: string status: $ref: '#/components/schemas/CctpTransferStatus' failureReason: type: string enum: - SOURCE_REVERTED - TX_MISMATCH - USER_OP_NOT_FOUND - SOURCE_TX_NOT_FOUND description: >- Set when `status` is `FAILED`. `SOURCE_TX_NOT_FOUND` means the submitted Solana signature didn't appear on chain within 30 minutes. delayReason: type: string description: >- Circle's reason while the transfer is `DELAYED`, for example `insufficient_fee`, `amount_above_max` or `insufficient_allowance_available`. sourceChain: type: string destinationChain: type: string amount: type: string amountOut: type: string description: >- What the recipient receives, `amount - fees.feeExecuted` once known, otherwise `amount - fees.maxFee`. Never less than the quoted `amountOut`, since `feeExecuted` is at most `maxFee`. sender: type: string description: >- The address that burns the USDC (the smart account for Account Abstraction clients on an EVM source, the Solana wallet for a Solana source). recipient: type: string speed: type: string enum: - fast - standard fees: type: object properties: maxFee: type: string description: >- Circle's protocol and forwarding fees, which come out of `amount`. custodian: type: string description: Your fee in USDC, paid on top of `amount`. feeExecuted: type: string description: The fee Circle actually charged, once known. totalDebit: type: string description: The USDC that leaves the wallet, `amount + fees.custodian`. sourceTxHash: type: string description: >- The burn transaction hash, or its base58 signature on Solana. For Account Abstraction clients on an EVM source, present once the user operation is included on chain. userOpHash: type: string destinationTxHash: type: string description: >- The mint transaction on the destination chain, a base58 signature on Solana. Set when `COMPLETED`. sourceExplorerUrl: type: string description: Links to Solscan for a Solana source. destinationExplorerUrl: type: string description: Links to Solscan for a Solana destination. estimatedCompletionAt: type: string format: date-time description: Only present until the status is final. pollAfterMs: type: integer minimum: 2000 description: >- How long to wait before reading again. Only present until the status is final. createdAt: type: string format: date-time updatedAt: type: string format: date-time CctpTransferStatus: type: string enum: - BUILT - SUBMITTED - PENDING_SOURCE - ATTESTING - DELAYED - FORWARDING - COMPLETED - FAILED - ABANDONED - STALLED description: >- `COMPLETED`, `FAILED` and `STALLED` are final. `ABANDONED` means built but not submitted within 1 hour; a late submit is still accepted. securitySchemes: bearerAuth: type: http scheme: bearer description: > Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.