Anchorage Digital Transaction Creation API

Operations for creating transactions with managed fees and replay protection

Operations 3

POST /wallet-operations/create/transaction Create Transaction #
POST /wallet-operations/create/propose-transaction Propose Create Transaction #
POST /wallet-operations/create/propose-raw-transaction Propose Raw Transaction #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/anchorage-transaction-creation-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

anchorage-transaction-creation-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  version: 2.0.0
  title: Anchorage Digital API Reference Transaction Creation API
  contact:
    email: api@anchorage.com
  description: '# Introduction

    *CONFIDENTIAL: Please do not distribute this documentation externally without prior Anchorage Digital approval.*


    The Anchorage Digital REST API v2.0 provides a set of operations and resources that allow Anchorage Digital clients and partners to:

    - Programmatically transfer funds from an Anchorage Digital vault or wallet without human intervention

    - Create and list deposit addresses in a vault

    - Read and monitor vault balances

    - Query transaction history including deposits

    …'
servers:
- url: https://api.anchorage-staging.com/v3
security:
- Api-Access-Key: []
tags:
- description: Operations for creating transactions with managed fees and replay protection
  name: Transaction Creation
paths:
  /wallet-operations/create/transaction:
    post:
      operationId: createTransaction
      summary: Create Transaction
      description: 'Permissions required: **Create transaction**


        Create and sign a specialized transaction immediately with Anchorage-managed replay protection and fee selection.


        This endpoint signs the transaction right away. Use Propose Create Transaction instead if you need

        an approval workflow before signing.


        Use Create Transfer Transaction for simple asset transfers instead.


        This endpoint returns immediately with a `walletOperationId`. Poll `GET /wallet-operations/{walletOperationId}` to check

        the status and retrieve the signed transaction data once construction is complete. Use the signedTransaction

        field from the response to broadcast to the blockchain.


        For operations that create staking positions (create validator, create stake account, split and deactivate stake),

        query `GET /wallets/{walletId}/staking-positions?creatingWalletOperationId={walletOperationId}` after the operation

        completes to find the resulting staking position.'
      parameters: []
      requestBody:
        description: Transaction creation request
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateTransactionRequest'
      responses:
        '202':
          description: Transaction request accepted for processing
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateWalletOperationResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
      tags:
      - Transaction Creation
  /wallet-operations/create/propose-transaction:
    post:
      operationId: proposeCreateTransaction
      summary: Propose Create Transaction
      description: 'Permissions required: **Propose create transaction**


        Create a specialized transaction for approval workflow with Anchorage-managed replay protection and fee selection.

        The transaction will not be signed until it receives the required endorsements.


        This endpoint creates the transaction but defers signing. The operation will enter PENDING_ENDORSEMENT status

        and require approval through your organization''s workflow before signing occurs.


        Use Create Transaction instead if you want to sign immediately without an approval workflow.


        Use Propose Create Transfer Transaction for simple asset transfers with deferred signing instead.


        This endpoint returns immediately with a `walletOperationId` in `PENDING_ENDORSEMENT` status. The transaction

        will not be signed until it receives the required endorsements through your approval workflow. Poll

        `GET /wallet-operations/{walletOperationId}` to check the status. Once endorsed and signed, use the

        signedTransaction field from the response to broadcast to the blockchain.


        For operations that create staking positions (create validator, create stake account, split and deactivate stake),

        query `GET /wallets/{walletId}/staking-positions?creatingWalletOperationId={walletOperationId}` after the operation

        completes to find the resulting staking position.'
      parameters: []
      requestBody:
        description: Transaction creation request for approval workflow
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateTransactionRequest'
      responses:
        '202':
          description: Transaction request accepted for approval workflow
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateWalletOperationResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
      tags:
      - Transaction Creation
  /wallet-operations/create/propose-raw-transaction:
    post:
      operationId: proposeRawTransaction
      summary: Propose Raw Transaction
      description: 'Permissions required: **Propose create transaction**


        Propose an off-chain signature or on-chain execution raw transaction for approval workflow.


        This endpoint creates a raw transaction but defers signing. The operation will enter PENDING_ENDORSEMENT status

        and require approval through your organization''s workflow before signing occurs.


        Supported raw transaction types include Ethereum structured data signing (EIP-712), Ethereum personal message

        signing, Ethereum transaction execution, and Solana raw transaction execution.


        This endpoint returns immediately with a `walletOperationId` in `PENDING_ENDORSEMENT` status. The transaction

        will not be signed until it receives the required endorsements through your approval workflow. Poll

        `GET /wallet-operations/{walletOperationId}` to check the status.'
      parameters: []
      requestBody:
        description: Raw transaction creation request for approval workflow
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ProposeRawTransactionRequest'
      responses:
        '202':
          description: Raw transaction request accepted for approval workflow
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CreateWalletOperationResponse'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '401':
          description: Unauthenticated
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorDetails'
      tags:
      - Transaction Creation
components:
  schemas:
    HyperevmBridgeRequest:
      description: Request to bridge HYPE from the client's HyperEVM wallet into HyperCore spot balance, the funding step that precedes staking. This operation is initiated on the HyperEVM (HYPE_HYPEREVM) wallet. An explicit amount is required ('all' is not supported). This operation can't be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)
      type: object
      properties:
        amount:
          description: Amount of HYPE to bridge from HyperEVM into HyperCore spot (decimal string). An explicit amount greater than zero is required.
          type: string
          example: '100.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is a HyperEVM bridge (inbound, HyperEVM -> HyperCore) request
          type: string
          default: HYPEREVM_BRIDGE
          enum:
          - HYPEREVM_BRIDGE
      required:
      - type
      - amount
      title: HyperEVM Bridge to HyperCore Request
    SolanaCreateAndActivateStakeAccountRequest:
      description: Request to create and delegate a new Solana stake account in a single operation. Minimum stake amount is 0.01 SOL.
      type: object
      properties:
        amount:
          description: Amount of SOL to deposit into the new stake account (decimal string). Minimum 0.01 SOL.
          type: string
          example: '2.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is a  Create Stake Account And Stake Request
          type: string
          default: SOLANA_CREATE_AND_ACTIVATE_STAKE_ACCOUNT
          enum:
          - SOLANA_CREATE_AND_ACTIVATE_STAKE_ACCOUNT
        voteAccountAddress:
          description: Vote account address corresponding with the validator to whom we want to stake
          type: string
          example: ANCVpxEySGWWLqqkVKw2xWYDE9UP4fmZWMCBr5t96jch
      required:
      - type
      - amount
      - voteAccountAddress
      title: Solana Create And Activate Stake Account Request
    SolanaRawTransactionRequest:
      description: Solana raw transaction execution request. The transaction field contains a Base64-encoded Solana transaction.
      type: object
      properties:
        transaction:
          description: Base64-encoded Solana transaction that could be passed to the sendTransaction RPC method
          type: string
          example: AX9ymHgILTd01GtdBsbQZ9by5D4z4UWh+1Tsh6LDuPHuZk/Z8LrIwoKZRp3le2RTb5lywL1xcJGQ8u3M3U0tyAgBAAEDXCL+JarHftfP5QgsRxpEsr+/YiRWQeCz7PI3jfzeppEvUc61u+TNHri9ChQdLN2evWGx+1O3MwbPFKV5rIqlxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAvOdVbvGn3R+uBkugNCq8C/Texc7ILBoYjbn4aVQV0OgBAgIAAQwCAAAAQEIPAAAAAAA=
        type:
          description: Discriminator field indicating this is a Solana raw transaction request
          type: string
          default: SOLANA_RAW_TRANSACTION
          enum:
          - SOLANA_RAW_TRANSACTION
      required:
      - type
      - transaction
      title: Solana Raw Transaction Request
    SolanaDeactivateStakeRequest:
      description: Request to deactivate a Solana stake account, beginning the process to unstake. This deactivates the entire balance of the stake account. For partial unstaking, use SOLANA_SPLIT_AND_DEACTIVATE_STAKE instead.
      type: object
      properties:
        stakeAccountAddress:
          description: Address of the stake account to deactivate. The entire balance will be deactivated.
          type: string
          example: 7NMw8RfMFLc6WZvyuJQbAF5yVhxFMkH9mKzPP2JVYKjL
        type:
          description: Discriminator field indicating this is a Solana deactivate stake request
          type: string
          default: SOLANA_DEACTIVATE_STAKE
          enum:
          - SOLANA_DEACTIVATE_STAKE
      required:
      - type
      - stakeAccountAddress
      title: Solana Deactivate Stake Request
    AvalancheCChainExportRequest:
      description: 'Step 1 of a C→P transfer: export AVAX from a C-Chain (EVM) wallet toward the P-Chain (on-chain c_to_p_export), initiated against the C-Chain wallet. This is the funding step that precedes P-Chain staking; settle the funds on the P-Chain with a follow-up AVALANCHE_PCHAIN_IMPORT. The destination must be a P-Chain wallet you control. Explicit amount only — ''all'' is not supported. This operation can''t be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)'
      type: object
      properties:
        amount:
          description: Amount of AVAX to export from the C-Chain (decimal string). Explicit amount required.
          type: string
          example: '10.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        destination:
          description: 'P-Chain address to receive the exported AVAX (format: P-avax1...). Must be an address of a wallet your organization controls.'
          type: string
          example: P-avax1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
        type:
          description: Discriminator field indicating this is an Avalanche C-Chain export request (initiated on the C-Chain wallet)
          type: string
          default: AVALANCHE_CCHAIN_EXPORT
          enum:
          - AVALANCHE_CCHAIN_EXPORT
      required:
      - type
      - destination
      - amount
      title: Avalanche C-Chain Export Request
    HypercoreDelegateStakeRequest:
      description: Request to delegate inactive stake balance to a validator on HyperCore. Currently only supports a single validator per wallet.
      type: object
      properties:
        amount:
          description: Amount of HYPE to delegate (decimal string)
          type: string
          example: '100.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is a HyperCore delegate stake request
          type: string
          default: HYPERCORE_DELEGATE_STAKE
          enum:
          - HYPERCORE_DELEGATE_STAKE
        validatorAddress:
          description: Address of the validator to delegate to (EVM 0x + 40 hex)
          type: string
          example: '0x393d4f2209abcacf57b75a51dafae777f9dd38bc'
          pattern: ^0x[0-9a-fA-F]{40}$
      required:
      - type
      - validatorAddress
      - amount
      title: HyperCore Delegate Stake Request
    EIP712SignTypedDataV4Request:
      description: Ethereum structured data signing request following the EIP-712 specification, using the JSON-RPC method eth_signTypedData_v4. The chainId in the domain must match the chain ID of the source wallet's network.
      type: object
      properties:
        domain:
          description: EIP-712 domain separator containing fields like name, version, chainId, and verifyingContract
          type: object
        message:
          description: The structured data to sign, conforming to the primaryType definition
          type: object
        primaryType:
          description: The primary type name that the message conforms to, must be defined in the types field
          type: string
          example: Permit
        type:
          description: Discriminator field indicating this is an EIP-712 sign typed data v4 request
          type: string
          default: EIP712_ETH_SIGNTYPEDDATA_V4
          enum:
          - EIP712_ETH_SIGNTYPEDDATA_V4
        types:
          description: EIP-712 type definitions. Must include the EIP712Domain type and any custom types referenced by primaryType.
          type: object
      required:
      - type
      - types
      - primaryType
      - domain
      - message
      title: EIP-712 Sign Typed Data V4 Request
    EthPersonalSignRequest:
      description: Ethereum personal message signing request using the eth_personalSign JSON-RPC method
      type: object
      properties:
        message:
          description: Human-readable message to sign
          type: string
          example: Please sign to verify wallet ownership
        type:
          description: Discriminator field indicating this is an Ethereum personal sign request
          type: string
          default: ETH_PERSONAL_SIGN
          enum:
          - ETH_PERSONAL_SIGN
      required:
      - type
      - message
      title: Ethereum Personal Sign Request
    CreateTransactionRequest:
      description: Request to create a specialized transaction with server-managed replay protection and fees
      type: object
      properties:
        idempotencyKey:
          description: Client-provided idempotency key to ensure request is processed only once
          type: string
          example: e763a50d-aa82-4ec7-b5a3-89ad0462d248
          maxLength: 128
        parameters:
          description: The details of the transaction to perform. Use the 'type' field to discriminate between different transaction types.
          discriminator:
            propertyName: type
            mapping:
              ETHEREUM_CREATE_VALIDATOR: '#/components/schemas/EthereumCreateValidatorRequest'
              ETHEREUM_ADD_STAKE: '#/components/schemas/EthereumAddStakeRequest'
              ETHEREUM_WITHDRAW_STAKE: '#/components/schemas/EthereumWithdrawStakeRequest'
              SOLANA_CREATE_AND_ACTIVATE_STAKE_ACCOUNT: '#/components/schemas/SolanaCreateAndActivateStakeAccountRequest'
              SOLANA_DEACTIVATE_STAKE: '#/components/schemas/SolanaDeactivateStakeRequest'
              SOLANA_WITHDRAW_STAKE: '#/components/schemas/SolanaWithdrawStakeRequest'
              SOLANA_SPLIT_AND_DEACTIVATE_STAKE: '#/components/schemas/SolanaSplitAndDeactivateStakeRequest'
              HYPERCORE_DELEGATE_STAKE: '#/components/schemas/HypercoreDelegateStakeRequest'
              HYPERCORE_SPOT_TO_STAKE: '#/components/schemas/HypercoreSpotToStakeRequest'
              HYPERCORE_UNDELEGATE_STAKE: '#/components/schemas/HypercoreUndelegateStakeRequest'
              HYPERCORE_STAKE_TO_SPOT: '#/components/schemas/HypercoreStakeToSpotRequest'
              HYPERCORE_BRIDGE: '#/components/schemas/HypercoreBridgeRequest'
              HYPEREVM_BRIDGE: '#/components/schemas/HyperevmBridgeRequest'
              HYPERCORE_LINK_ACCOUNTS: '#/components/schemas/HypercoreLinkAccountsRequest'
              AVALANCHE_PCHAIN_DELEGATE_STAKE: '#/components/schemas/AvalanchePChainDelegateStakeRequest'
              AVALANCHE_PCHAIN_STAKE: '#/components/schemas/AvalanchePChainStakeRequest'
              AVALANCHE_PCHAIN_EXPORT: '#/components/schemas/AvalanchePChainExportRequest'
              AVALANCHE_CCHAIN_EXPORT: '#/components/schemas/AvalancheCChainExportRequest'
              AVALANCHE_PCHAIN_IMPORT: '#/components/schemas/AvalanchePChainImportRequest'
              AVALANCHE_CCHAIN_IMPORT: '#/components/schemas/AvalancheCChainImportRequest'
          oneOf:
          - $ref: '#/components/schemas/EthereumCreateValidatorRequest'
          - $ref: '#/components/schemas/EthereumAddStakeRequest'
          - $ref: '#/components/schemas/EthereumWithdrawStakeRequest'
          - $ref: '#/components/schemas/SolanaCreateAndActivateStakeAccountRequest'
          - $ref: '#/components/schemas/SolanaDeactivateStakeRequest'
          - $ref: '#/components/schemas/SolanaWithdrawStakeRequest'
          - $ref: '#/components/schemas/SolanaSplitAndDeactivateStakeRequest'
          - $ref: '#/components/schemas/HypercoreDelegateStakeRequest'
          - $ref: '#/components/schemas/HypercoreSpotToStakeRequest'
          - $ref: '#/components/schemas/HypercoreUndelegateStakeRequest'
          - $ref: '#/components/schemas/HypercoreStakeToSpotRequest'
          - $ref: '#/components/schemas/HypercoreBridgeRequest'
          - $ref: '#/components/schemas/HyperevmBridgeRequest'
          - $ref: '#/components/schemas/HypercoreLinkAccountsRequest'
          - $ref: '#/components/schemas/AvalanchePChainDelegateStakeRequest'
          - $ref: '#/components/schemas/AvalanchePChainStakeRequest'
          - $ref: '#/components/schemas/AvalanchePChainExportRequest'
          - $ref: '#/components/schemas/AvalancheCChainExportRequest'
          - $ref: '#/components/schemas/AvalanchePChainImportRequest'
          - $ref: '#/components/schemas/AvalancheCChainImportRequest'
        sourceWalletId:
          description: Globally unique wallet identifier for the wallet that will pay transaction fees and sign the transaction
          type: string
      additionalProperties: false
      required:
      - parameters
      - sourceWalletId
    EthereumAddStakeRequest:
      description: Request to add stake to an existing 0x02 Ethereum validator by depositing additional ETH. Any validator balance above 2048 ETH will not earn rewards. Beyond that point it is recommended to create a new validator via ETHEREUM CREATE VALIDATOR REQUEST.
      type: object
      properties:
        amount:
          description: Amount of ETH to add as stake (decimal string)
          type: string
          example: '32.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is an Ethereum add stake request
          type: string
          default: ETHEREUM_ADD_STAKE
          enum:
          - ETHEREUM_ADD_STAKE
        validatorPublicKey:
          description: BLS12-381 public key of the validator to add stake to (48 bytes, hex encoded)
          type: string
          example: 93247f2209abcacf57b75a51dafae777f9dd38bc7053d1af526f220a7489a6d3a2753e5f3e8b1cfe39b56f43611df74a
      required:
      - type
      - validatorPublicKey
      - amount
      title: Ethereum Add Stake Request
    AvalanchePChainDelegateStakeRequest:
      description: 'Request to delegate AVAX to a validator on the Avalanche P-Chain for a fixed duration. P-Chain staking is time-locked: there is no early exit, and funds are returned automatically at the end of the staking period. Duration must be between 14 and 365 days on mainnet (1–365 days on testnet).'
      type: object
      properties:
        amount:
          description: Amount of AVAX to delegate (decimal string)
          type: string
          example: '25.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        duration:
          description: Staking duration in whole days (e.g. '14' for 14 days). Must be between 14 and 365 days on mainnet, or 1 and 365 days on testnet/regnet.
          type: string
          example: '14'
          pattern: ^[1-9][0-9]*$
        type:
          description: Discriminator field indicating this is an Avalanche P-Chain delegate stake request
          type: string
          default: AVALANCHE_PCHAIN_DELEGATE_STAKE
          enum:
          - AVALANCHE_PCHAIN_DELEGATE_STAKE
        validatorAddress:
          description: 'Avalanche NodeID of the validator to delegate to (format: NodeID-<base58check>)'
          type: string
          example: NodeID-7Xhw2mDxuDS44j42TCB6U5579esbSt3Lg
          pattern: ^NodeID-[1-9A-HJ-NP-Za-km-z]{33}$
      required:
      - type
      - validatorAddress
      - amount
      - duration
      title: Avalanche P-Chain Delegate Stake Request
    HypercoreUndelegateStakeRequest:
      description: Request to undelegate funds from a validator on HyperCore, beginning the 1-day delegation lockup before the funds return to the idle stake account. Currently only supports a single validator per wallet.
      type: object
      properties:
        amount:
          description: Amount of HYPE to undelegate (decimal string), or 'ALL' to undelegate the full delegated balance at the validator
          type: string
          example: '100.0'
          pattern: ^(ALL|[0-9]\d*(\.\d+)?)$
        type:
          description: Discriminator field indicating this is a HyperCore undelegate stake request
          type: string
          default: HYPERCORE_UNDELEGATE_STAKE
          enum:
          - HYPERCORE_UNDELEGATE_STAKE
        validatorAddress:
          description: Address of the validator to undelegate from (EVM 0x + 40 hex)
          type: string
          example: '0x393d4f2209abcacf57b75a51dafae777f9dd38bc'
          pattern: ^0x[0-9a-fA-F]{40}$
      required:
      - type
      - validatorAddress
      - amount
      title: HyperCore Undelegate Stake Request
    AvalanchePChainExportRequest:
      description: 'Step 1 of a P→C transfer: export AVAX from a P-Chain wallet toward the C-Chain (on-chain p_to_c_export), initiated against the P-Chain wallet. Bridging is two steps with no auto-import — settle the funds on the C-Chain with a follow-up AVALANCHE_CCHAIN_IMPORT. The destination must be a C-Chain wallet you control. Explicit amount only — ''all'' is not supported. This operation can''t be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)'
      type: object
      properties:
        amount:
          description: Amount of AVAX to export (decimal string). Explicit amount required.
          type: string
          example: '10.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        destination:
          description: C-Chain (EVM 0x) address to receive the exported AVAX. Must be an address of a wallet your organization controls.
          type: string
          example: '0x5aAeb6053F3E94C9b9A09f33669435E7Ef1BeAed'
        type:
          description: Discriminator field indicating this is an Avalanche P-Chain export request
          type: string
          default: AVALANCHE_PCHAIN_EXPORT
          enum:
          - AVALANCHE_PCHAIN_EXPORT
      required:
      - type
      - destination
      - amount
      title: Avalanche P-Chain Export Request
    HypercoreSpotToStakeRequest:
      description: Request to move spot balance into the stake account as inactive stake, the prerequisite for delegating. This operation can't be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)
      type: object
      properties:
        amount:
          description: Amount of HYPE to move from spot into the stake account (decimal string). An explicit amount greater than zero is required.
          type: string
          example: '100.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is a HyperCore spot-to-stake request
          type: string
          default: HYPERCORE_SPOT_TO_STAKE
          enum:
          - HYPERCORE_SPOT_TO_STAKE
      required:
      - type
      - amount
      title: HyperCore Spot To Stake Request
    AvalancheCChainImportRequest:
      description: 'Step 2 of a P→C transfer: claim on the C-Chain the AVAX that was exported from the P-Chain (on-chain c_from_p_import), initiated against the C-Chain (EVM) wallet. The funds always credit the initiating wallet''s own C-Chain address, so no destination is supplied. Explicit amount only — ''all'' is not supported. This operation can''t be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)'
      type: object
      properties:
        amount:
          description: Amount of AVAX to claim on the C-Chain (decimal string). Explicit amount required.
          type: string
          example: '10.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is an Avalanche C-Chain import request (initiated on the C-Chain wallet)
          type: string
          default: AVALANCHE_CCHAIN_IMPORT
          enum:
          - AVALANCHE_CCHAIN_IMPORT
      required:
      - type
      - amount
      title: Avalanche C-Chain Import Request
    HypercoreBridgeRequest:
      description: Request to bridge HyperCore spot balance out to the client's HyperEVM wallet. An explicit amount is required ('all' is not supported). This operation can't be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)
      type: object
      properties:
        amount:
          description: Amount of HYPE to bridge from HyperCore spot to HyperEVM (decimal string). An explicit amount greater than zero is required.
          type: string
          example: '100.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is a HyperCore bridge (outbound) request
          type: string
          default: HYPERCORE_BRIDGE
          enum:
          - HYPERCORE_BRIDGE
      required:
      - type
      - amount
      title: HyperCore Bridge to HyperEVM Request
    HypercoreStakeToSpotRequest:
      description: Request to move inactive stake balance back to spot balance. This is the withdraw-to-spot action; completion is subject to HyperCore's 7-day unstaking queue. This operation can't be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)
      type: object
      properties:
        amount:
          description: Amount of HYPE to move from the stake account back to spot (decimal string). An explicit amount greater than zero is required.
          type: string
          example: '100.0'
          pattern: ^[0-9]\d*(\.\d+)?$
        type:
          description: Discriminator field indicating this is a HyperCore stake-to-spot request
          type: string
          default: HYPERCORE_STAKE_TO_SPOT
          enum:
          - HYPERCORE_STAKE_TO_SPOT
      required:
      - type
      - amount
      title: HyperCore Stake To Spot Request
    CreateWalletOperationResponse:
      description: Async response with wallet operation ID. Use the walletOperationId with the GET /wallet-operations/{walletOperationId} endpoint to poll for the operation status and retrieve the created transaction details.
      type: object
      properties:
        walletOperationId:
          description: Wallet operation identifier. Poll the GET /wallet-operations/{walletOperationId} endpoint to check the status and retrieve the transaction data once creation is complete.
          type: string
          example: op_550e8400-e29b-41d4-a716-446655440000
      required:
      - walletOperationId
    AvalanchePChainStakeRequest:
      description: Request to create a new Avalanche P-Chain validator (self-stake). Requires BLS proof-of-possession (nodePublicKey + nodeSignature) to register the validator's BLS key. The commission controls what percentage of delegation rewards are kept by the validator. This operation can't be submitted to the create-transaction endpoint yet — it always requires quorum approval, so use the propose-transaction endpoint instead. (API-key endorsement / skip-quorum auto-execution for this and other generic operations is planned.)
      type: object
      properties:
        amount:
  

# --- truncated at 32 KB (44 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/anchorage/refs/heads/main/openapi/anchorage-transaction-creation-api-openapi.yml