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

# Get transaction status

> Get transaction status for bridge activity associated with an address.



## OpenAPI

````yaml openapi/polymarket-bridge.json GET /apis/v1/polymarket/status/{address}
openapi: 3.1.0
info:
  description: ''
  title: Polymarket Bridge
  version: '1'
  x-aisa-capabilities:
    idempotency: Idempotency-Key
    max_price: X-AISA-Max-Price-USD
    quote:
      header: X-AISA-Cost-Mode
      value: quote
  x-aisa-configured-paths:
    - /apis/v1/polymarket/deposit
    - /apis/v1/polymarket/quote
    - /apis/v1/polymarket/status/{address}
    - /apis/v1/polymarket/supported-assets
    - /apis/v1/polymarket/withdraw
  x-aisa-document:
    facts_hash: 2086e30aaacbdf046a1028dc02ae4ed4958ee132ea224144dc1e956945c61119
    generator_version: '2'
    protocol_version: '1'
    schema_version: '1'
    composer_version: '13'
    response_pending: []
    document_hash: sha256:a22669af750e793690ca9b6ba1c73d040b9af5d18c6207e9282cf0f95572ce64
  x-aisa-plans:
    builder: 1
    display_plan: payg
    payg: 1
    similarweb_payg: 1
    team: 1
    version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb
  x-aisa-provider: polymarket-bridge
  x-aisa-catalogs:
    polymarket-bridge:
      title: Polymarket Bridge
      description: ''
      x-aisa-document:
        facts_hash: 2086e30aaacbdf046a1028dc02ae4ed4958ee132ea224144dc1e956945c61119
        generator_version: '2'
        protocol_version: '1'
        schema_version: '1'
      x-aisa-plans:
        builder: 1
        display_plan: payg
        payg: 1
        similarweb_payg: 1
        team: 1
        version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb
      x-aisa-capabilities:
        idempotency: Idempotency-Key
        max_price: X-AISA-Max-Price-USD
        quote:
          header: X-AISA-Cost-Mode
          value: quote
servers:
  - url: https://api.aisa.one
security:
  - bearerAuth: []
paths:
  /apis/v1/polymarket/status/{address}:
    get:
      tags:
        - default
      summary: Get transaction status
      description: Get transaction status for bridge activity associated with an address.
      operationId: any_polymarket_bridge_apis_v1_polymarket_status_address
      parameters:
        - name: address
          in: path
          required: true
          description: >
            The bridge address to query for transaction status, taken from the
            `/deposit` or `/withdraw` response. EVM, Solana, Tron, and Bitcoin
            address formats are supported. EVM addresses are normalized before
            the request is forwarded upstream.
          schema:
            type: string
          example: EXoZue2avJae1d45B3fVw2unhkrtToSYQqHtHgfZ2cbE
        - name: cursor
          in: query
          required: false
          description: >
            Opaque continuation token returned as `nextCursor` by the previous
            response. Omit it to request the first page. URL-encode it, since
            cursors can contain characters such as `+`, `/`, and `=`. Invalid,
            tampered, or cross-address tokens return 400; restart the walk
            without a cursor when that happens.
          schema:
            type: string
          example: eyJsYXN0SWQiOiI0MiJ9
        - name: limit
          in: query
          required: false
          description: >
            Maximum number of transactions per page. A page may contain fewer
            transactions than requested and still have a following page.
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
          example: 100
        - name: paginate
          in: query
          required: false
          description: >
            Compatibility parameter forwarded upstream for existing
            integrations. Pagination applies whether or not it is sent, so new
            integrations should omit it and use `cursor` and `limit` alone. When
            sent, the only supported value is `true`.
          schema:
            type: string
            enum:
              - 'true'
      responses:
        '200':
          description: Successfully retrieved transaction status
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/Response7A88Af0Ff8Eb_TransactionStatusResponse
              example:
                transactions:
                  - fromChainId: '1151111081099710'
                    fromTokenAddress: '11111111111111111111111111111111'
                    fromAmountBaseUnit: '13566635'
                    toChainId: '137'
                    toTokenAddress: '0xC011a7E12a19f7B1f670d46F03B03f3342E82DFB'
                    status: DEPOSIT_DETECTED
                  - fromChainId: '1151111081099710'
                    fromTokenAddress: '11111111111111111111111111111111'
                    fromAmountBaseUnit: '13400000'
                    toChainId: '137'
                    toTokenAddress: '0xC011a7E12a19f7B1f670d46F03B03f3342E82DFB'
                    createdTimeMs: 1757646914535
                    status: PROCESSING
                  - fromChainId: '1151111081099710'
                    fromTokenAddress: '11111111111111111111111111111111'
                    fromAmountBaseUnit: '13500152'
                    toChainId: '137'
                    toTokenAddress: '0xC011a7E12a19f7B1f670d46F03B03f3342E82DFB'
                    txHash: >-
                      3atr19NAiNCYt24RHM1WnzZp47RXskpTDzspJoCBBaMFwUB8fk37hFkxz35P5UEnnmWz21rb2t5wJ8pq3EE2XnxU
                    createdTimeMs: 1757531217339
                    status: COMPLETED
                nextCursor: eyJsYXN0SWQiOiI0MiJ9
        default:
          content:
            application/json:
              schema: {}
          description: >-
            Error response; upstream passthrough responses may use provider
            formats
components:
  schemas:
    Response7A88Af0Ff8Eb_TransactionStatusResponse:
      type: object
      required:
        - transactions
        - nextCursor
      properties:
        transactions:
          type: array
          items:
            $ref: '#/components/schemas/Response7A88Af0Ff8Eb_Transaction'
          description: >
            One page of transactions for the given address, newest first. This
            is a page, not the full history for the address.
        nextCursor:
          type:
            - string
            - 'null'
          description: >
            Opaque continuation token for the next page, or null when the
            pagination walk is complete. Pass it back verbatim as `cursor` on
            the next request; never parse, modify, construct, or reuse it with a
            different address. Stop on null rather than on an empty page or a
            page shorter than `limit`.
          example: eyJsYXN0SWQiOiI0MiJ9
    Response7A88Af0Ff8Eb_Transaction:
      type: object
      properties:
        fromChainId:
          type: string
          description: Source chain ID
          example: '1151111081099710'
        fromTokenAddress:
          type: string
          description: Source token contract address
          example: '11111111111111111111111111111111'
        fromAmountBaseUnit:
          type: string
          description: Amount in base units (without decimals)
          example: '13566635'
        toChainId:
          type: string
          description: Destination chain ID
          example: '137'
        toTokenAddress:
          type: string
          description: Destination token contract address
          example: '0xC011a7E12a19f7B1f670d46F03B03f3342E82DFB'
        status:
          type: string
          description: >
            Current status of the transaction. If a transaction fails, remains
            stuck, or funds are held due to a compliance check, direct users to
            our Bridge API provider's support
            (https://intercom.help/funxyz/en/articles/10732578-contact-us).
          enum:
            - DEPOSIT_DETECTED
            - PROCESSING
            - ORIGIN_TX_CONFIRMED
            - SUBMITTED
            - COMPLETED
            - FAILED
          example: COMPLETED
        txHash:
          type: string
          description: Transaction hash (only available when status is COMPLETED)
          example: >-
            3atr19NAiNCYt24RHM1WnzZp47RXskpTDzspJoCBBaMFwUB8fk37hFkxz35P5UEnnmWz21rb2t5wJ8pq3EE2XnxU
        createdTimeMs:
          type: number
          description: >-
            Unix timestamp in milliseconds when transaction was created (missing
            when status is DEPOSIT_DETECTED)
          example: 1757531217339
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.