> ## Documentation Index
> Fetch the complete documentation index at: https://developers.avacloud.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a teleporter message

> **[Deprecated]** Gets a teleporter message by message ID.

⚠️ **This operation will be removed in a future release.  Please use /v1/icm/messages/:messageId endpoint instead** .



## OpenAPI

````yaml get /v1/teleporter/messages/{messageId}
openapi: 3.1.0
info:
  title: Data API
  description: >-
    The Data API provides web3 application developers with multi-chain data
    related to Avalanche's primary network, Avalanche subnets, and Ethereum.
    With Data API, you can easily build products that leverage real-time and
    historical transaction and transfer history, native and token balances, and
    various types of token metadata. The API is in Beta and may be subject to
    change.</br></br>If you have feedback or feature requests for the API,
    please submit them <a
    href="https://portal.productboard.com/dndv9ahlkdfye4opdm8ksafi/tabs/4-glacier-api">here</a>.
    Bug reports can be submitted <a
    href="https://docs.google.com/forms/d/e/1FAIpQLSeJQrcp7QoNiqozMDKrVJGX5wpU827d3cVTgF8qa7t_J1Pb-g/viewform">here</a>,
    and any potential security issues can be reported <a
    href="https://immunefi.com/bounty/avalabs">here</a>.
  version: 1.0.0
  contact: {}
servers:
  - url: https://glacier-api.avax.network
security:
  - apiKey: []
  - {}
tags:
  - name: EVM Chains
    description: >-
      Find information about indexed EVM-compatible chains, such as the
      Avalanche C-Chain.
  - name: EVM Blocks
    description: >-
      Find information about blocks on EVM-compatible chains, such as the
      Avalanche C-Chain.
  - name: EVM Transactions
    description: >-
      Find information about transactions on EVM-compatible chains, such as the
      Avalanche C-Chain.
  - name: EVM Balances
    description: >-
      Find information about balances on EVM-compatible chains, such as the
      Avalanche C-Chain.
  - name: EVM Contracts
    description: >-
      Find information about contracts on EVM-compatible chains, such as the
      Avalanche C-Chain.
  - name: Primary Network
  - name: Primary Network Blocks
    description: >-
      Find information about blocks on Avalanche's Primary Network Chains - the
      P-Chain, the X-Chain, and the C-Chain.
  - name: Primary Network Vertices
    description: Find information about vertices on Avalanche's X-Chain.
  - name: Primary Network Transactions
    description: >-
      Find information about transactions on Avalanche's Primary Network Chains
      - the P-Chain, the X-Chain, and the C-Chain.
  - name: Primary Network Balances
    description: >-
      Find information about balances on Avalanche's Primary Network Chains -
      the P-Chain, the X-Chain, and the C-Chain.
  - name: Primary Network UTXOs
    description: >-
      Find information about utxos on Avalanche's Primary Network Chains - the
      P-Chain, the X-Chain, and the C-Chain.
  - name: Primary Network Rewards
    description: Find information about rewards on Avalanche's Primary Network.
  - name: NFTs
  - name: Operations
  - name: Health Check
  - name: Teleporter
    description: Find information about Teleporter transactions.
  - name: Interchain Messaging
    description: Find information about Interchain Messaging transactions.
  - name: Webhooks
    description: Manage webhooks and get notified for various onchain activities.
  - name: RPC
    description: Interact with chain nodes using JSON-RPC.
  - name: Data API Usage Metrics
    description: Usage metrics and logs for the Data API.
  - name: Signature Aggregator
    description: Request signatures for a Warp message from Subnet validators
  - name: Notifications
    description: Get notifications for validator status and activity issues.
  - name: AVAX Supply
    description: Find information about AVAX supply.
paths:
  /v1/teleporter/messages/{messageId}:
    get:
      tags:
        - Teleporter
      description: >-
        **[Deprecated]** Gets a teleporter message by message ID.


        ⚠️ **This operation will be removed in a future release.  Please use
        /v1/icm/messages/:messageId endpoint instead** .
      operationId: getTeleporterMessage
      parameters:
        - name: messageId
          required: true
          in: path
          description: The message ID of the teleporter message.
          example: acf1c8b06f9aec48e9fcbefbbe576ae8a7ca3b327fcae111396e7cc99956674d
          schema:
            type: string
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                oneOf:
                  - $ref: '#/components/schemas/PendingTeleporterMessage'
                  - $ref: '#/components/schemas/DeliveredTeleporterMessage'
                  - $ref: >-
                      #/components/schemas/DeliveredSourceNotIndexedTeleporterMessage
                discriminator:
                  propertyName: status
                  mapping:
                    pending: '#/components/schemas/PendingTeleporterMessage'
                    delivered: '#/components/schemas/DeliveredTeleporterMessage'
                    delivered_source_not_indexed: >-
                      #/components/schemas/DeliveredSourceNotIndexedTeleporterMessage
        '400':
          description: |-
            Bad requests generally mean the client has passed invalid 
                or malformed parameters. Error messages in the response could help in 
                evaluating the error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BadRequest'
        '401':
          description: |-
            When a client attempts to access resources that require 
                authorization credentials but the client lacks proper authentication 
                in the request, the server responds with 401.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Unauthorized'
        '403':
          description: |-
            When a client attempts to access resources with valid
                credentials but doesn't have the privilege to perform that action, 
                the server responds with 403.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Forbidden'
        '404':
          description: |-
            The error is mostly returned when the client requests
                with either mistyped URL, or the passed resource is moved or deleted, 
                or the resource doesn't exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotFound'
        '429':
          description: |-
            This error is returned when the client has sent too many,
                and has hit the rate limit.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TooManyRequests'
        '500':
          description: |-
            The error is a generic server side error that is 
                returned for any uncaught and unexpected issues on the server side. 
                This should be very rare, and you may reach out to us if the problem 
                persists for a longer duration.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/InternalServerError'
        '502':
          description: |-
            This is an internal error indicating invalid response 
                  received by the client-facing proxy or gateway from the upstream server.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BadGateway'
        '503':
          description: |-
            The error is returned for certain routes on a particular
                Subnet. This indicates an internal problem with our Subnet node, and may 
                not necessarily mean the Subnet is down or affected.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ServiceUnavailable'
      deprecated: true
components:
  schemas:
    PendingTeleporterMessage:
      type: object
      properties:
        messageId:
          type: string
        teleporterContractAddress:
          type: string
        sourceBlockchainId:
          type: string
        destinationBlockchainId:
          type: string
        sourceEvmChainId:
          type: string
        destinationEvmChainId:
          type: string
        messageNonce:
          type: string
        from:
          type: string
        to:
          type: string
        data:
          type: string
        messageExecuted:
          type: boolean
        receipts:
          type: array
          items:
            $ref: '#/components/schemas/TeleporterReceipt'
        receiptDelivered:
          type: boolean
        rewardDetails:
          $ref: '#/components/schemas/TeleporterRewardDetails'
        sourceTransaction:
          $ref: '#/components/schemas/TeleporterSourceTransaction'
        status:
          type: string
          enum:
            - pending
      required:
        - messageId
        - teleporterContractAddress
        - sourceBlockchainId
        - destinationBlockchainId
        - sourceEvmChainId
        - destinationEvmChainId
        - messageNonce
        - from
        - to
        - messageExecuted
        - receipts
        - receiptDelivered
        - rewardDetails
        - sourceTransaction
        - status
    DeliveredTeleporterMessage:
      type: object
      properties:
        messageId:
          type: string
        teleporterContractAddress:
          type: string
        sourceBlockchainId:
          type: string
        destinationBlockchainId:
          type: string
        sourceEvmChainId:
          type: string
        destinationEvmChainId:
          type: string
        messageNonce:
          type: string
        from:
          type: string
        to:
          type: string
        data:
          type: string
        messageExecuted:
          type: boolean
        receipts:
          type: array
          items:
            $ref: '#/components/schemas/TeleporterReceipt'
        receiptDelivered:
          type: boolean
        rewardDetails:
          $ref: '#/components/schemas/TeleporterRewardDetails'
        sourceTransaction:
          $ref: '#/components/schemas/TeleporterSourceTransaction'
        destinationTransaction:
          $ref: '#/components/schemas/TeleporterDestinationTransaction'
        status:
          type: string
          enum:
            - delivered
      required:
        - messageId
        - teleporterContractAddress
        - sourceBlockchainId
        - destinationBlockchainId
        - sourceEvmChainId
        - destinationEvmChainId
        - messageNonce
        - from
        - to
        - messageExecuted
        - receipts
        - receiptDelivered
        - rewardDetails
        - sourceTransaction
        - destinationTransaction
        - status
    DeliveredSourceNotIndexedTeleporterMessage:
      type: object
      properties:
        messageId:
          type: string
        teleporterContractAddress:
          type: string
        sourceBlockchainId:
          type: string
        destinationBlockchainId:
          type: string
        sourceEvmChainId:
          type: string
        destinationEvmChainId:
          type: string
        messageNonce:
          type: string
        from:
          type: string
        to:
          type: string
        data:
          type: string
        messageExecuted:
          type: boolean
        receipts:
          type: array
          items:
            $ref: '#/components/schemas/TeleporterReceipt'
        receiptDelivered:
          type: boolean
        rewardDetails:
          $ref: '#/components/schemas/TeleporterRewardDetails'
        destinationTransaction:
          $ref: '#/components/schemas/TeleporterDestinationTransaction'
        status:
          type: string
          enum:
            - delivered_source_not_indexed
      required:
        - messageId
        - teleporterContractAddress
        - sourceBlockchainId
        - destinationBlockchainId
        - sourceEvmChainId
        - destinationEvmChainId
        - messageNonce
        - from
        - to
        - messageExecuted
        - receipts
        - receiptDelivered
        - rewardDetails
        - destinationTransaction
        - status
    BadRequest:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 400
        error:
          type: string
          description: The type of error
          examples:
            - Bad Request
      required:
        - message
        - statusCode
        - error
    Unauthorized:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 401
        error:
          type: string
          description: The type of error
          examples:
            - Unauthorized
      required:
        - message
        - statusCode
        - error
    Forbidden:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 403
        error:
          type: string
          description: The type of error
          examples:
            - Forbidden
      required:
        - message
        - statusCode
        - error
    NotFound:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 404
        error:
          type: string
          description: The type of error
          examples:
            - Not Found
      required:
        - message
        - statusCode
        - error
    TooManyRequests:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 429
        error:
          type: string
          description: The type of error
          examples:
            - Too Many Requests
      required:
        - message
        - statusCode
        - error
    InternalServerError:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 500
        error:
          type: string
          description: The type of error
          examples:
            - Internal Server Error
      required:
        - message
        - statusCode
        - error
    BadGateway:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 502
        error:
          type: string
          description: The type of error
          examples:
            - Bad Gateway
      required:
        - message
        - statusCode
        - error
    ServiceUnavailable:
      type: object
      properties:
        message:
          description: The error message describing the reason for the exception
          oneOf:
            - type: string
            - type: array
              items:
                type: string
        statusCode:
          type: number
          description: The HTTP status code of the response
          examples:
            - 503
        error:
          type: string
          description: The type of error
          examples:
            - Service Unavailable
      required:
        - message
        - statusCode
        - error
    TeleporterReceipt:
      type: object
      properties:
        receivedMessageNonce:
          type: string
        relayerRewardAddress:
          type: string
      required:
        - receivedMessageNonce
        - relayerRewardAddress
    TeleporterRewardDetails:
      type: object
      properties:
        address:
          type: string
          description: A wallet or contract address in mixed-case checksum encoding.
          examples:
            - '0x71C7656EC7ab88b098defB751B7401B5f6d8976F'
        name:
          type: string
          description: The contract name.
          examples:
            - Wrapped AVAX
        symbol:
          type: string
          description: The contract symbol.
          examples:
            - WAVAX
        decimals:
          type: number
          description: >-
            The number of decimals the token uses. For example `6`, means to
            divide the token amount by `1000000` to get its user representation.
          examples:
            - 18
        logoUri:
          type: string
          description: The logo uri for the address.
          examples:
            - >-
              https://images.ctfassets.net/gcj8jwzm6086/5VHupNKwnDYJvqMENeV7iJ/fdd6326b7a82c8388e4ee9d4be7062d4/avalanche-avax-logo.svg
        ercType:
          type: string
          enum:
            - ERC-20
        price:
          description: The token price, if available.
          allOf:
            - $ref: '#/components/schemas/Money'
        value:
          type: string
      required:
        - address
        - name
        - symbol
        - decimals
        - ercType
        - value
    TeleporterSourceTransaction:
      type: object
      properties:
        txHash:
          type: string
        timestamp:
          type: number
        gasSpent:
          type: string
      required:
        - txHash
        - timestamp
        - gasSpent
    TeleporterDestinationTransaction:
      type: object
      properties:
        txHash:
          type: string
        timestamp:
          type: number
        gasSpent:
          type: string
        rewardRedeemer:
          type: string
        delivererAddress:
          type: string
      required:
        - txHash
        - timestamp
        - gasSpent
        - rewardRedeemer
        - delivererAddress
    Money:
      type: object
      properties:
        currencyCode:
          $ref: '#/components/schemas/CurrencyCode'
          examples:
            - usd
        value:
          type: number
          description: Monetary value in base 10 decimals.
          examples:
            - '42.42'
      required:
        - currencyCode
        - value
    CurrencyCode:
      type: string
      description: ISO 4217 currency code.
      enum:
        - usd
        - eur
        - aud
        - cad
        - chf
        - clp
        - cny
        - czk
        - dkk
        - gbp
        - hkd
        - huf
        - jpy
        - nzd
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-glacier-api-key
      description: >-
        Api keys provide higher access to rate limits. To obtain an api key,
        sign up for an account at https://avacloud.io/.

````