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

# Post /v2/tx/track

> Requests tracking of a transaction that has already landed on-chain but was not broadcast through the Skip Go API. The status of a tracked transaction and subsequent IBC or Axelar transfers if routing assets cross chain can be queried through the /status endpoint.



## OpenAPI

````yaml swagger post /v2/tx/track
openapi: 3.0.0
info:
  title: Skip Go API
  description: >-
    Simple APIs to build seamless cross-chain products that do more with fewer
    transactions. For devs with all levels of cross-chain experience.
  version: 0.1.0
servers:
  - url: https://api.skip.build
    description: Production
  - url: https://api.dev.skip.build
    description: Development
  - url: http://localhost:8080
    description: Local
security: []
tags:
  - name: Info
    description: APIs that return general information useful for a variety of operations
  - name: Fungible
    description: >-
      APIs swaps, transfers, and contract calls within the IBC/Cosmos Ecosystem,
      EVM ecosystem, and between them, including automatic DEX aggregation,
      bridge routing, and denom recommendation. Typical usage is /route to
      generate routing info and quotes, followed by /msgs to generate msgs for
      signing
  - name: Transaction
    description: >-
      APIs for broadcasting transactions within the IBC/Cosmos ecosystem, EVM
      ecosystem, and between them, and tracking their status and any subsequent
      transfers if routing assets cross chain. Typical usage is /submit to
      broadcast a transaction, followed by /status to query its status
paths:
  /v2/tx/track:
    post:
      tags:
        - Transaction
      description: >-
        Requests tracking of a transaction that has already landed on-chain but
        was not broadcast through the Skip Go API. The status of a tracked
        transaction and subsequent IBC or Axelar transfers if routing assets
        cross chain can be queried through the /status endpoint.
      operationId: track
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TrackTxRequest'
      responses:
        '200':
          description: The hash of the transaction and a link to its explorer page.
          content:
            application/json:
              example:
                tx_hash: >-
                  F30790E79987F18F3A4DA8C7A9BA9FD837043EF59D8236CA85180E1078BC607F
                explorer_link: >-
                  https://www.mintscan.io/osmosis/tx/F30790E79987F18F3A4DA8C7A9BA9FD837043EF59D8236CA85180E1078BC607F
              schema:
                $ref: '#/components/schemas/TrackTxResponse'
        '400':
          description: >-
            The request was invalid, i.e. the transaction hash was malformed or
            the specified transaction did not execute successfully.
          content:
            application/json:
              example:
                code: 3
                message: tx is invalid on chain
                details: []
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: >-
            The specified chain is not supported or the specified transaction
            was not found.
          content:
            application/json:
              example:
                code: 5
                message: chain ID not supported
                details: []
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Internal server error
          content:
            application/json:
              example:
                code: 2
                message: internal server error
                details: []
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    TrackTxRequest:
      type: object
      required:
        - tx_hash
        - chain_id
      properties:
        tx_hash:
          type: string
          description: Hex encoded hash of the transaction to track
        chain_id:
          type: string
          description: Chain ID of the transaction
    TrackTxResponse:
      type: object
      required:
        - tx_hash
        - explorer_link
      properties:
        tx_hash:
          type: string
          description: Hash of the transaction
        explorer_link:
          type: string
          description: Link to the transaction on the relevant block explorer
    Error:
      properties:
        code:
          allOf:
            - $ref: '#/components/schemas/GRPCStatusCode'
          description: Error code
        details:
          description: Additional error details
          items:
            $ref: '#/components/schemas/ErrorDetail'
          type: array
        message:
          description: Error message
          type: string
      type: object
    GRPCStatusCode:
      description: >-
        grpc status codes as defined
        [here](https://grpc.github.io/grpc/core/md_doc_statuscodes.html)
      type: number
    ErrorDetail:
      type: object
      properties:
        reason:
          description: >
            Error detail:

            * `LOW_INFO_ERROR` - Not enough asset pricing information to
            determine the price safety of the route.

            * `BAD_PRICE_ERROR` - The execution price of the route deviates
            significantly from the current market price.

            * `HIGH_LOSS_ERROR` - The route would result in a USD loss exceeding
            the configured threshold and has been blocked.
          enum:
            - LOW_INFO_ERROR
            - BAD_PRICE_ERROR
            - HIGH_LOSS_ERROR
          type: string

````