<p>There is no maker fee using API, but when place new order, the default parameter for "post_only" is false, which means it is possible set a price to become a taker, hence GDAX will make sure you have enough funds to cover the fees.</p>

<p>Set post_only to true then GDAX will allow you to spend your entire account without reserves for fees.</p>

CC BY-SA 3.0
2017-12-21T16:22:08.493Z
2017-12-21T16:22:08.493Z
Jake
<p>I'm not sure exactly why this would happen, but according to the <a href="https://www.sec.gov/spotlight/emsac/memo-maker-taker-fees-on-equities-exchanges.pdf" rel="nofollow noreferrer">SEC</a>:</p>

<p>"If an execution occurs, the liquidity providing “maker” receives a rebate, and the “taker” that executes against that resting order pays a fee to the market."</p>

<p>This means the <strong>maker</strong> is the one who already had their trade order in the books, and the <strong>taker</strong> is the one who places the order and who's order is executed immediately against the makers.</p>

<p>Using the API, you could've accidentally placed a buy order below or at the current price or ETH. If this happened you would be charged a "taker" fee instead of the 0% maker fee. That is my only explanation, because it says <a href="https://docs.gdax.com/#fees" rel="nofollow noreferrer">here</a> in there API docs there is zero maker fee. </p>

<p>If you were the maker but charged the taker fee, I'd ask GDAX why this is occurring <a href="https://support.gdax.com/customer/portal/emails/new" rel="nofollow noreferrer">here</a></p>

CC BY-SA 3.0
2017-12-11T05:00:24.670Z
2017-12-11T05:00:24.670Z
chriscrutt
<p>If you go to the fills tab you can see which order(s) your order was matched with. You can also see if your order was executed as a maker or a taker. It likely executed as a taker, which is why you had to pay the fee.</p>

CC BY-SA 4.0
2018-12-30T03:15:14.863Z
2018-12-30T03:15:14.863Z
mdornfe1
<p>Why are we getting charged maker's fee when creating buy orders on the GDAX API.</p>

<p>For example I deposited 100 EUR to GDAX account and wanted to place a limit buying order for size 0.5 ETH at the price of 200 EUR and received HTTP 400: "Insufficient funds" as a response.</p>

<p>I lowered the size to 0.4 and the order went through, but I was left with 19.80 EUR on my account - meaning that 0.25% was taken as well, but my order was at 200 EUR and 0.4 ETH, totaling 80 EUR not 80.2 EUR.</p>

<p>Looking at the API there shouldn't be a maker's fee.</p>

<p>Has anyone else noticed this?</p>

<p>Doing it manually in the GUI I am left with 20 EUR.</p>

<coinbase.com><gdax>
Why is GDAX charging maker's fee when using API?
user2352084
# Why is GDAX charging maker's fee when using API?

(Asked by: username_0 on 2017-12-11)

Why are we getting charged maker's fee when creating buy orders on the GDAX API.

For example I deposited 100 EUR to GDAX account and wanted to place a limit buying order for size 0.5 ETH at the price of 200 EUR and received HTTP 400: "Insufficient funds" as a response.

I lowered the size to 0.4 and the order went through, but I was left with 19.80 EUR on my account - meaning that 0.25% was taken as well, but my order was at 200 EUR and 0.4 ETH, totaling 80 EUR not 80.2 EUR.

Looking at the API there shouldn't be a maker's fee.

Has anyone else noticed this?

Doing it manually in the GUI I am left with 20 EUR.

**Tags:** coinbase.com, gdax


---

## 3 answers

### Answer by username_1 on 2017-12-21. Score: 2

There is no maker fee using API, but when place new order, the default parameter for "post\_only" is false, which means it is possible set a price to become a taker, hence GDAX will make sure you have enough funds to cover the fees.

Set post\_only to true then GDAX will allow you to spend your entire account without reserves for fees.


---

### Answer by username_2 on 2017-12-11. Score: 1

I'm not sure exactly why this would happen, but according to the [SEC](https://www.sec.gov/spotlight/emsac/memo-maker-taker-fees-on-equities-exchanges.pdf):

"If an execution occurs, the liquidity providing “maker” receives a rebate, and the “taker” that executes against that resting order pays a fee to the market."

This means the **maker** is the one who already had their trade order in the books, and the **taker** is the one who places the order and who's order is executed immediately against the makers.

Using the API, you could've accidentally placed a buy order below or at the current price or ETH. If this happened you would be charged a "taker" fee instead of the 0% maker fee. That is my only explanation, because it says [here](https://docs.gdax.com/#fees) in there API docs there is zero maker fee.

If you were the maker but charged the taker fee, I'd ask GDAX why this is occurring [here](https://support.gdax.com/customer/portal/emails/new)


---

### Answer by username_3 on 2018-12-30. Score: 0

If you go to the fills tab you can see which order(s) your order was matched with. You can also see if your order was executed as a maker or a taker. It likely executed as a taker, which is why you had to pay the fee.


---

