Come on, there were plenty of answers from experts saying that I don't know anything, the only thing I want are api recommendations where I can make automatic btc shipments from a single wallet, I'm testing the coinbase one, but the library they had in js is obsolete, the Blockchain is a good option I'll see what to do with it, from there on out I'm not interested in going into many details, that's why I'm looking for an api, so that they manage security and complex code for me, I'll just do the interface, I thought to ask a little bit about the reception address gap limit since I am presenting some inconveniences too, but I am afraid I am in the wrong place...
I don't think you're in the wrong place at all - this is clearly
development.
I am wondering though, if you're sure about what you are doing if relying on a 3rd party for
'manage security and complex code for me'. In essence, if you have your coins on an online wallet like blockchain.com, you actually don't hold the keys and the coins are not yours.
Please give this a read:
https://notyourkeys.org/For a PoC, such an online wallet with easy REST API might be fine, but for anything more serious, you really need to hold your coins locally on your own machine, preferably with a HSM.
I'm not trying to discourage you from the project; however you're coming in with the attitude that you're sure you want to use a centralized custodial service, while it seems you're not fully aware of the risks, so I'm just trying to explain why it's not a good idea. All the reasons for holding your own private keys are explained nicely in the above mentioned
Not Your Keys, Not Your Bitcoin website.