Skip to content
21 changes: 21 additions & 0 deletions api-reference/problems/below-min-withdraw-limit.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 400 - Below Min Withdraw Limit
---

A Below Min Withdraw Limit error is returned when a withdrawal request is below the minimum allowed withdrawal amount.

For example, attempting to withdraw an amount less than the configured minimum withdrawal limit for the profile or asset will result in this error.

To resolve this error, increase the withdrawal amount to meet or exceed the minimum required limit.

<CodeGroup>
```json Example
{
"detail": "withdrawal amount is below minimum limit",
"meta": {},
"status": 400,
"title": "Below Min Withdraw Limit",
"type": "https://developer.paxos.com/docs/v2/problems/below-min-withdraw-limit"
}
```
</CodeGroup>
21 changes: 21 additions & 0 deletions api-reference/problems/exceed-max-withdraw-limit.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 400 - Exceed Max Withdraw Limit
---

An Exceed Max Withdraw Limit error is returned when a withdrawal request exceeds the maximum allowed withdrawal amount.

For example, attempting to withdraw an amount greater than the configured maximum withdrawal limit for the profile or asset will result in this error.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have limits per Profile at the moment. Limits can be set on customer's account level.


To resolve this error, reduce the withdrawal amount to be within the allowed maximum limit, or contact support to adjust the withdrawal limits if needed.

<CodeGroup>
```json Example
{
"detail": "withdrawal amount exceeds maximum limit",
"meta": {},
"status": 400,
"title": "Exceed Max Withdraw Limit",
"type": "https://developer.paxos.com/docs/v2/problems/exceed-max-withdraw-limit"
}
```
</CodeGroup>
21 changes: 21 additions & 0 deletions api-reference/problems/exceed-precision.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 400 - Exceed Precision
---

An Exceed Precision error is returned when a request contains a numeric value with more decimal places than allowed for the specified asset or field.

For example, attempting to create an order with an amount that has more decimal places than the asset's precision limit will result in this error.

To resolve this error, round the value to the appropriate number of decimal places as defined by the asset's precision requirements.

<CodeGroup>
```json Example
{
"detail": "value exceeds allowed precision",
"meta": {},
"status": 400,
"title": "Exceed Precision",
"type": "https://developer.paxos.com/docs/v2/problems/exceed-precision"
}
```
</CodeGroup>
21 changes: 21 additions & 0 deletions api-reference/problems/market-conditions-prevented-execution.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 403 - Market Conditions Prevented Execution
---

A Market Conditions Prevented Execution error is returned when current market conditions prevent the execution of a trade or order.

For example, this error may occur during periods of extreme volatility, insufficient liquidity, or other market conditions that make it impossible to execute the requested operation at the specified parameters.

To resolve this error, you may need to adjust your order parameters, wait for market conditions to stabilize, or request a new quote.

<CodeGroup>
```json Example
{
"detail": "current market conditions prevented execution",
"meta": {},
"status": 403,
"title": "Market Conditions Prevented Execution",
"type": "https://developer.paxos.com/docs/v2/problems/market-conditions-prevented-execution"
}
```
</CodeGroup>
21 changes: 21 additions & 0 deletions api-reference/problems/minimum-commission-exceeds-notional.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 400 - Minimum Commission Exceeds Notional
---

A Minimum Commission Exceeds Notional error is returned when the minimum commission required for a trade exceeds the notional value of the trade itself.

For example, attempting to execute a very small trade where the minimum commission fee would be greater than the trade amount will result in this error.

To resolve this error, increase the trade size so that the notional value exceeds the minimum commission requirement.

<CodeGroup>
```json Example
{
"detail": "minimum commission exceeds notional value",
"meta": {},
"status": 400,
"title": "Minimum Commission Exceeds Notional",
"type": "https://developer.paxos.com/docs/v2/problems/minimum-commission-exceeds-notional"
}
```
</CodeGroup>
21 changes: 21 additions & 0 deletions api-reference/problems/notional-value-too-large.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 403 - Notional Value Too Large
---

A Notional Value Too Large error is returned when the total notional value of a trade or order exceeds the maximum allowed limit.

For example, attempting to create an order with a notional value that exceeds the configured maximum for the profile, market, or trading limits will result in this error.

To resolve this error, reduce the order size to bring the notional value within the allowed limits, or contact support to adjust trading limits if needed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add a link to the Docs describing the limits. We have something here - https://docs.paxos.com/guides/crypto-brokerage/orders-precision-rounding#order-limitations

I don't know if this is still valid - https://help.paxos.com/hc/en-us/articles/4410538467220-Maximum-Order-Size-per-Trade If yes, we should incorporate this into Docs.


<CodeGroup>
```json Example
{
"detail": "notional value exceeds maximum allowed",
"meta": {},
"status": 403,
"title": "Notional Value Too Large",
"type": "https://developer.paxos.com/docs/v2/problems/notional-value-too-large"
}
```
</CodeGroup>
21 changes: 21 additions & 0 deletions api-reference/problems/unavailable-market.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 403 - Unavailable Market
---

An Unavailable Market error is returned when attempting to trade on a market that is currently unavailable or disabled.

For example, this error may occur when a market is temporarily closed for maintenance, suspended due to regulatory requirements, or permanently disabled.

To resolve this error, check the market status and wait for the market to become available, or select a different available market for your trade.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we provide a way for customers to figure out the proper market names available to them?
We have this endpoint with supported markets - https://api.paxos.com/v2/markets, but I think it doesn't show everything that some customers can actually use.


<CodeGroup>
```json Example
{
"detail": "market is currently unavailable",
"meta": {},
"status": 403,
"title": "Unavailable Market",
"type": "https://developer.paxos.com/docs/v2/problems/unavailable-market"
}
```
</CodeGroup>
9 changes: 8 additions & 1 deletion docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -956,10 +956,17 @@
{
"group": "Problems",
"pages": [
"api-reference/problems/already-exists",
"api-reference/problems/below-min-withdraw-limit",
"api-reference/problems/exceed-max-withdraw-limit",
"api-reference/problems/exceed-precision",
"api-reference/problems/expired",
"api-reference/problems/insufficient-funds",
"api-reference/problems/market-conditions-prevented-execution",
"api-reference/problems/minimum-commission-exceeds-notional",
"api-reference/problems/notional-value-too-large",
"api-reference/problems/rejected",
"api-reference/problems/already-exists"
"api-reference/problems/unavailable-market"
]
}
]
Expand Down
Loading