List Unconfirmed Omni Transactions By Address

This endpoint will list unconfirmed Omni transactions by an attribute address. The transactions listed will detail additional information such as hash, height, time of creation in Unix timestamp, etc.

Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.

GET /blockchain-data/{blockchain}/{network}/omni/address-transactions-unconfirmed/{address}

Path Parameters

  • Required
    network string

    Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "ropsten", "rinkeby" are test networks.

    Example : testnet
    Possible Values : mainnet testnet
  • Required
    blockchain string

    Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.

    Example : bitcoin
    Possible Values : bitcoin
  • Required
    address string

    Represents the public address, which is a compressed and shortened form of a public key.

    Example : mi7iSsKcvyFYNsiYdDZqJmH75RmoHomwmo

Query parameters

  • Optional
    context string

    In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

  • Optional
    limit integer

    Defines how many items should be returned in the response per page basis.

    Default : 50
    Example : 50
  • Optional
    offset integer

    The starting index of the response items, i.e. where the response should start listing the returned items.

    Default : 0
    Example : 10

Response schema

200 400 401 402 403 409 415 422 429 500
HTTP Status Code: 200
Content-Type: application/json

The request has been successful.

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2.0
  • Required
    requestId string

    Defines the ID of the request. The requestId is generated by Crypto APIs and it's unique for every request.

    Example : 601c1710034ed6d407996b30
  • Optional
    context string

    In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context is specified by the user.

    Example : You can add any text here
  • Required
    data object
    • Required
      offset integer

      The starting index of the response items, i.e. where the response should start listing the returned items.

      Example : 0
    • Required
      limit integer

      Defines how many items should be returned in the response per page basis.

      Example : 50
    • Required
      total integer

      Defines the total number of items returned in the response.

      Example : 100
    • Required
      items array
      Example : Array ( )
      • Required
        amount string

        Defines the amount of the sent tokens.

        Example : 14.915785
      • Required
        divisible boolean

        Defines whether the attribute can be divisible or not, as boolean. E.g., if it is "true", the attribute is divisible.

        Example : True
      • Required
        mined boolean

        Defines whether the transaction has been mined or not, as boolean. E.g. if set to "true", it means the transaction is mined.

        Example : True
      • Required
        propertyId integer

        Represents the identifier of the tokens to send.

        Example : 2
      • Required
        recipients array

        Represents an object of addresses that receive the transactions.

        • Required
          address string

          Represents the hash of the address that receives the funds.

          Example : ms4KNsbNpoU8g424pzmEjbkFbfAHae1msB
        • Required
          amount string

          Defines the amount of the received funds as a string.

          Example : 0.1
      • Required
        senders array

        Represents an object of addresses that provide the funds.

        • Required
          address string

          Represents the hash of the address that provides the funds.

          Example : mwDuExdjRewYKYoR454sZGvd15LnJVsmoR
        • Required
          amount string

          Represents the total amount sent by this address including the fee.

          Example : 0.1
      • Required
        sent boolean

        Defines whether the transaction has been sent or not, as boolean. E.g. if set to "true", it means the transaction is sent.

        Example : False
      • Required
        timestamp integer

        Defines the exact date/time in Unix Timestamp when this transaction was mined, confirmed or first seen in Mempool, if it is unconfirmed.

        Example : 1616429665
      • Required
        transactionId string

        Represents the unique identifier of a transaction, i.e. it could be transactionId in UTXO-based protocols like Bitcoin, and transaction hash in Ethereum blockchain.

        Example : b3e76370a1ccdf5549a3654f1d14be27bebb4a834a81b489fcc99d057ada3dd1
      • Required
        type string

        Defines the type of the transaction as a string.

        Example : Simple Send
      • Required
        typeInt integer

        Defines the type of the transaction as a number.

        Example : 0
      • Required
        version integer

        Defines the specific version.

        Example : 0
      • Required
        fee object
        • Required
          amount string

          Defines the amount of the fee.

          Example : 0.0001
        • Required
          unit string

          Defines the unit of the fee.

          Example : BTC
Try it out

Request Example

GET
https://rest.cryptoapis.io/v2/blockchain-data/bitcoin/testnet/omni/address-transactions-unconfirmed/mi7iSsKcvyFYNsiYdDZqJmH75RmoHomwmo?limit=50&offset=10
Headers
Host: https://rest.cryptoapis.io/v2
Content-Type: application/json
X-API-Key: my-api-key

Response Example

{
    "apiVersion": "2.0",
    "requestId": "601c1710034ed6d407996b30",
    "context": "You can add any text here",
    "data": {
        "offset": 0,
        "limit": 50,
        "total": 100,
        "items": [
            {
                "amount": "14.915785",
                "divisible": true,
                "mined": true,
                "propertyId": 2,
                "recipients": [
                    {
                        "address": "ms4KNsbNpoU8g424pzmEjbkFbfAHae1msB",
                        "amount": "0.1"
                    }
                ],
                "senders": [
                    {
                        "address": "mwDuExdjRewYKYoR454sZGvd15LnJVsmoR",
                        "amount": "0.1"
                    }
                ],
                "sent": false,
                "timestamp": 1616429665,
                "transactionId": "b3e76370a1ccdf5549a3654f1d14be27bebb4a834a81b489fcc99d057ada3dd1",
                "type": "Simple Send",
                "typeInt": 0,
                "version": 0,
                "fee": {
                    "amount": "0.0001",
                    "unit": "BTC"
                }
            }
        ]
    }
}