Create an outgoing request bundle (using addresses)

post

https://your-protect-instance.example.com/api/rest/v1/requests/bundle/outgoing/transfers/address_to_address

This endpoint creates an outgoing request bundle. It will create a set of requests prepared to send funds to multiple addresses (multi-output) from one address in a single transaction. The requests are specified using addresses instead of IDs.
Currently only supported on: BTC.
Required role: RequestCreator.

Responses

200A successful response.

400Bad Request: indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing)

401Unauthorized: indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource

403Forbidden: indicates that the server understands the request but refuses to authorize it

404Not Found: indicates that the server cannot find the requested resource

500Internal Server Error: indicates that the server encountered an unexpected condition that prevented it from fulfilling the request

503Service Unavailable: indicates that the server is not ready to handle the request.

defaultAn unexpected error response.