New confirmed internal transactions

Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new confirmed internal transactions. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs.

Being confirmed means that the transactions are verified by miners and added to the next block.

To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks here.

Crypto APIs will notify the user only when the event occurs. There are cases when the specific event doesn't happen at all, or takes a long time to do so. A callback notification will not be sent if the event does not or cannot occur, or will take long time to occur.

Supports Callback Functionality Single Result - This endpoint returns only one single result. POST /blockchain-events/{blockchain}/{network}/subscriptions/address-internal-transactions-confirmed

Path Parameters

  • Required
    blockchain string

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

    Example : ethereum-classic
    Possible Values : ethereum ethereum-classic binance-smart-chain tron
  • 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" are test networks.

    Example : mordor
    Possible Values : mainnet testnet mordor nile goerli

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.

    Example : yourExampleString

Request body schema application/json

  • 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 : yourExampleString
  • Required
    data object
    • Required
      item object
      • Required
        address string

        Defines the specific address of the internal transaction.

        Example : 0xbcc817f057950b0df41206c5d7125e6225cae18e
      • Required
        allowDuplicates boolean

        Flag that permits or denies creation of duplicates

        Default : False
        Example : True
      • Required
        callbackSecretKey string

        Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs. For more information please see our Documentation.

        Example : yourSecretKey
      • Required
        callbackUrl string

        Represents the URL that is set by the customer where the callback will be received at. The callback notification will be received only if and when the event occurs. We support ONLY httpS type of protocol.

        Example : https://example.com
      • Optional
        receiveCallbackOn integer

        Represents the exact confirmation, on which the user wants to receive callback.

        Example : 3

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 : 2021-03-20
  • 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 : yourExampleString
  • Required
    data object
    • Required
      item object
      • Required
        address string

        Defines the specific address of the internal transaction.

        Example : 0xbcc817f057950b0df41206c5d7125e6225cae18e
      • Required
        callbackSecretKey string

        Represents the Secret Key value provided by the customer. This field is used for security purposes during the callback notification, in order to prove the sender of the callback as Crypto APIs 2.0. For more information please see our Documentation.

        Example : yourSecretKey
      • Required
        callbackUrl string

        Represents the URL that is set by the customer where the callback will be received at. The callback notification will be received only if and when the event occurs. We support ONLY httpS type of protocol.

        Example : https://example.com
      • Required
        createdTimestamp integer

        Defines the specific time/date when the subscription was created in Unix Timestamp.

        Example : 1236238648
      • Required
        eventType string

        Defines the type of the specific event available for the customer to subscribe to for callback notification.

        Example : ADDRESS_INTERNAL_TRANSACTION_CONFIRMED
      • Required
        isActive boolean

        Defines whether the subscription is active or not. Set as boolean.

        Example : True
      • Required
        receiveCallbackOn integer

        Represents the exact confirmation, on which the user wants to receive callback.

        Example : 3
      • Required
        referenceId string

        Represents a unique ID used to reference the specific callback subscription.

        Example : bc243c86-0902-4386-b30d-e6b30fa1f2aa

Callback parameters Method : POST

You can use the optional parameter callbackSecretKey in your request for additional security. It is then used to create a unique hash string in the x-signature response header in the callback request itself. For more information, please see our Documentation.
ADDRESS_INTERNAL_TRANSACTION_CONFIRMED

Content-Type : application/json

  • Object :

  • Required
    apiVersion string

    Specifies the version of the API that incorporates this endpoint.

    Example : 2021-03-20
  • Required
    referenceId string

    Represents a unique identifier that serves as reference to the specific request which prompts a callback, e.g. Blockchain Events Subscription, Blockchain Automation, etc.

    Example : 6038d09050653d1f0e40584c
  • Required
    idempotencyKey string

    Specifies a unique ID generated by the system and attached to each callback. It is used by the server to recognize consecutive requests with the same data with the purpose not to perform the same operation twice.

    Example : e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c
  • Required
    data object

    Specifies all data, as attributes, included into the callback notification, which depends on the event.

    • Required
      product string

      Represents the Crypto APIs 2.0 product which sends the callback.

      Example : BLOCKCHAIN_DATA
    • Required
      event string

      Defines the specific event, for which a callback subscription is set.

      Example : ADDRESS_INTERNAL_TRANSACTION_CONFIRMED
    • Required
      item object

      Defines an item as one result.

      • Required
        blockchain string

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

        Example : ethereum
      • 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 : mainnet
      • Required
        address string

        Defines the specific address of the internal transaction.

        Example : 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2
      • Required
        minedInBlock object

        Refers to the specific block the transaction was mined in.

        • Required
          height integer

          Defines the number of blocks in the blockchain preceding this specific block.

          Example : 12567093
        • Required
          hash string

          Represents the hash of the block's header, i.e. an output that has a fixed length.

          Example : 0xa787415dc7c7025a43b87542a57872d1127f30f95daa87097cf5f26ef79d6950
        • Required
          timestamp integer

          Defines the exact date/time when this transaction was mined in seconds since Unix Epoch time.

          Example : 1622797821
      • Required
        parentTransactionId string

        Defines the Parent Transaction's unique ID.

        Example : 0xc3be8371b32fa2238c44271643446b14c87ff11b77d58f9a1bceb1d1253e79b2
      • Required
        operationId string

        Defines the specific operation's unique ID.

        Example : call_5_0
      • Required
        amount string

        Defines the amount of coins sent with the confirmed transaction.

        Example : 0.94891479938916527
      • Required
        unit string

        Defines the unit of the transaction, e.g. Gwei.

        Example : ETH
      • Required
        direction string

        Defines whether the transaction is "incoming" or "outgoing".

        Example : outgoing
        Possible Values : incoming outgoing

Credits Cost : 1000 Credits For 1 Result(s)

Try it out

Request Example

POST
https://rest.cryptoapis.io/blockchain-events/ethereum-classic/mordor/subscriptions/address-internal-transactions-confirmed?context=yourExampleString
Headers
Content-Type: application/json
X-API-Key: my-api-key

Request Body
{
    "context": "yourExampleString",
    "data": {
        "item": {
            "address": "0xbcc817f057950b0df41206c5d7125e6225cae18e",
            "allowDuplicates": true,
            "callbackSecretKey": "yourSecretKey",
            "callbackUrl": "https://example.com",
            "receiveCallbackOn": 3
        }
    }
}

Response Example

{
    "apiVersion": "2021-03-20",
    "requestId": "601c1710034ed6d407996b30",
    "context": "yourExampleString",
    "data": {
        "item": {
            "address": "0xbcc817f057950b0df41206c5d7125e6225cae18e",
            "callbackSecretKey": "yourSecretKey",
            "callbackUrl": "https://example.com",
            "createdTimestamp": 1236238648,
            "eventType": "ADDRESS_INTERNAL_TRANSACTION_CONFIRMED",
            "isActive": true,
            "receiveCallbackOn": 3,
            "referenceId": "bc243c86-0902-4386-b30d-e6b30fa1f2aa"
        }
    }
}

Callback Example

{
    "apiVersion": "2021-03-20",
    "referenceId": "6038d09050653d1f0e40584c",
    "idempotencyKey": "e55bf7a4a7188855f1c27541a6c387d04cc3b22ee34d1304b0e6ecad61c9906c",
    "data": {
        "product": "BLOCKCHAIN_DATA",
        "event": "ADDRESS_INTERNAL_TRANSACTION_CONFIRMED",
        "item": {
            "blockchain": "ethereum",
            "network": "mainnet",
            "address": "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2",
            "minedInBlock": {
                "height": 12567093,
                "hash": "0xa787415dc7c7025a43b87542a57872d1127f30f95daa87097cf5f26ef79d6950",
                "timestamp": 1622797821
            },
            "parentTransactionId": "0xc3be8371b32fa2238c44271643446b14c87ff11b77d58f9a1bceb1d1253e79b2",
            "operationId": "call_5_0",
            "amount": "0.94891479938916527",
            "unit": "ETH",
            "direction": "outgoing"
        }
    }
}