POST a Turbo Transaction

prerequisites before submitting an api request, ensure you have completed the following create an account create a project installed the eternl wallet https //eternl io/ you need a maestro composer level subscription or higher to access the turbo transactions feature otherwise, you can use the submit transaction # endpoint steps to submit an api request turbo transactions supercharge your transaction submission processes this guide will walk you through generating a transaction on eternl and sending it to maestro's turbo transaction endpoint 1\ prepare your wallet switch the network to pre production testnet by selecting it from the bottom right selector of the eternl wallet interface create or restore two separate wallets in eternl # to test the transaction after creating the wallets, disable the transaction auto submit option find your w allet address in the eternl dashboard under the receive tab send test ada (tada) to one (or both) wallets using the cardano faucet https //docs cardano org/cardano testnet/tools/faucet here https //docs cardano org/cardano testnet/tools/faucet 2\ configure eternl to use maestro's turbo submit endpoint open eternl app settings expand the custom submit api endpoint section and click add enter the below turbo transaction submit api url, replacing \<api key> with your project key found in your project dashboard https //dashboard gomaestro org/login https //preprod gomaestro api org/v1/txmanager/turbosubmit?api key=\<api key> click save if your subscription does not support turbo transactions , you can try the standard submit api upgrade to the pay as you go conductor subscription https //www gomaestro org/pricing for easy access and support for turbo transactions 3\ generating a transaction go to the send tab enter the receiving wallet address to create and sign a transaction between the two test wallets then, specify the amount of test ada to send enter your spending password and click sign 4\ submit the transaction option 1 click submit to hit the turbo transaction endpoint via eternl option 2 click download(signed) copy the cborhex from the downloaded transaction file in this example, that will be \> 84a500818258206c4200b0697da7bb625007431df049c70fcc6f548a35f706f9f3356e2c91ee51000186825839008f0bb4f9da382fc5c4926d55130ffbc6f9b4df9461ca922dd310aade6e923c8acd41268395174a364a586ea99a26ba526aa16a3aead7a3ef1a004c4b4082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71b0000000129b6e78b82583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a94dcd36082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a4a6e69b082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a4a6e69b082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a004c4b40021a0002bf35031a042bb5290800a10081825820a92c0a0ddb77ae18ea28e7bcd7f6966af99f32a9a73fc84c5c2c0737f6e8903b5840307e1b7cfedbf33bc167a1779aa72a5379c2461caba02becb2786c4688af48f9c72029f89839d664848145c3d4e719a2122820bc188d279ded4f9c9e59c6e706f5f6 run the following command to create a binary stream \> transaction=84a500818258206c4200b0697da7bb625007431df049c70fcc6f548a35f706f9f3356e2c91ee51000186825839008f0bb4f9da382fc5c4926d55130ffbc6f9b4df9461ca922dd310aade6e923c8acd41268395174a364a586ea99a26ba526aa16a3aead7a3ef1a004c4b4082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71b0000000129b6e78b82583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a94dcd36082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a4a6e69b082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a4a6e69b082583900e55b137c7911b75f8f8b5c83f82107e9c5a40d03e6eeb58bad2b4227a720eb63cb5bd34ac4923e8b114c672f543a0e98a1e18492bc3f2da71a004c4b40021a0002bf35031a042bb5290800a10081825820a92c0a0ddb77ae18ea28e7bcd7f6966af99f32a9a73fc84c5c2c0737f6e8903b5840307e1b7cfedbf33bc167a1779aa72a5379c2461caba02becb2786c4688af48f9c72029f89839d664848145c3d4e719a2122820bc188d279ded4f9c9e59c6e706f5f6 \> xxd r p <<< ${transaction} > tx signed cbor preprod use your project api key to submit the transaction to the maestro endpoint /txmanager/turbosubmit \> curl x post h "content type application/cbor" h "api key \<project api key>" data binary @tx signed cbor preprod https //preprod gomaestro api org/v1/txmanager/turbosubmit the response is the transaction hash of the submitted transaction