| `recipient` | The recipient Stacks address in c32check format | **No** |
> > > > > > > | `recipient` | The recipient Stacks address in c32check format | **No** |
| `amount` | The amount of Stacks tokens to send denominated in microstacks | **No** |
> > > > > > > | `amount` | The amount of Stacks tokens to send denominated in microstacks | **No** |
| `fee` | The fee that the sender is willing to pay for miners to process the transaction. Denominated in microstacks | Yes |
> > > > > > > | `fee` | The fee that the sender is willing to pay for miners to process the transaction. Denominated in microstacks | Yes |
| `nonce` | A nonce is an integer that needs to be incremented by 1 for each sequential transaction from the same account. Nonces start at 0 | Yes |
> > > > > > > | `nonce` | A nonce is an integer that needs to be incremented by 1 for each sequential transaction from the same account. Nonces start at 0 | Yes |
> Note: By setting a fee in the transaction builder function, the automatic fee estimation step will be skipped.
> Note: By setting a fee in the transaction builder function, the automatic fee estimation step will be skipped.
<<<<<<<HEAD
> <<<<<<<HEAD
>
>
> > > > > > > 50bb8c8a... feat: draft of first 2 tutorials
> > > > > > > # 50bb8c8a... feat: draft of first 2 tutorials
=======
> > > > > > >
>>>>>>> 50bb8c8a... feat: draft of first 2 tutorials
>>>>>>> # 50bb8c8a... feat: draft of first 2 tutorials
=======
> > > > > > >
-> Note: By setting a fee in the transaction builder function, the automatic fee estimation step will be skipped.
> > > > > > > -> Note: By setting a fee in the transaction builder function, the automatic fee estimation step will be skipped.
>>>>>>> 69c8cfcb... feat: restructure information architecture
>>>>>>> 69c8cfcb... feat: restructure information architecture
>>>>>>> ab15b4f3... feat: restructure information architecture
>>>>>>> ab15b4f3... feat: restructure information architecture
### Handling nonces
### Handling nonces
@ -206,15 +207,15 @@ With the transaction ID, we can check the status of the transaction. Every trans
=======
=======
> Note: A transactions is completed once it is confirmed and the status changes to `success`. Most transactions will be pending for several minutes before confirmed. You should implement polling in your app to refresh the status display.
> Note: A transactions is completed once it is confirmed and the status changes to `success`. Most transactions will be pending for several minutes before confirmed. You should implement polling in your app to refresh the status display.
<<<<<<<HEAD
> <<<<<<<HEAD
>
>
> > > > > > > 50bb8c8a... feat: draft of first 2 tutorials
> > > > > > > # 50bb8c8a... feat: draft of first 2 tutorials
=======
> > > > > > >
>>>>>>> 50bb8c8a... feat: draft of first 2 tutorials
>>>>>>> # 50bb8c8a... feat: draft of first 2 tutorials
=======
> > > > > > >
-> Note: A transactions is completed once it is confirmed and the status changes to `success`. Most transactions will be pending for several minutes before confirmed. You should implement polling in your app to refresh the status display.
> > > > > > > -> Note: A transactions is completed once it is confirmed and the status changes to `success`. Most transactions will be pending for several minutes before confirmed. You should implement polling in your app to refresh the status display.
>>>>>>> 69c8cfcb... feat: restructure information architecture
>>>>>>> 69c8cfcb... feat: restructure information architecture
>>>>>>> ab15b4f3... feat: restructure information architecture
>>>>>>> ab15b4f3... feat: restructure information architecture
```js
```js
const transactions = new TransactionsApi(apiConfig);
const transactions = new TransactionsApi(apiConfig);