No. That would require both an API to create the destination object in the repository and an API to setup the security (the part done by the XS Admin tool).
What is your underlying requirement here? Do you just want a dynamic destination address?
If so you can send a request using both the destination or by supplying the destination URL as a parameter instead of the destination object. The main problem is that your authorization options are very limited with this approach: