Function cryptoapis::apis::create_subscriptions_for_api::new_unconfirmed_coins_transactions

pub async fn new_unconfirmed_coins_transactions(
    configuration: &Configuration, 
    blockchain: &str, 
    network: &str, 
    context: Option<&str>, 
    new_unconfirmed_coins_transactions_request_body: Option<NewUnconfirmedCoinsTransactionsRequestBody>
) -> Result<NewUnconfirmedCoinsTransactionsResponse, Error<NewUnconfirmedCoinsTransactionsError>>

Through this endpoint customers can create callback subscriptions for a specific event. In this case the event is when there are new unconfirmed coins transactions for the user. By creating this subscription the user will be notified by Crypto APIs 2.0 when that event occurs. The information is returned per specified address. Unconfirmed coins transactions remain in the mempool (memory pool) until they are confirmed by miners and added to the next block. Sometimes spikes in transaction activity can cause delays in confirmations. {note}To have an operational callback subscription, you need to first verify a domain for the Callback URL. Please see more information on Callbacks here.{/note} {note}It is also important to note that just because pending unconfirmed transactions are in the mempool, doesn’t necessarily mean they will get confirmed.{/note} {warning}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.{/warning}