Skip to main content
Use this page when you need to show a countdown for an active order window. RampHub keeps one active order intent per customer, token, and network at a time, whether the order is a buy or a sell. The intent usually lasts 30 minutes and closes automatically when the underlying order completes, cancels, or expires. Merchant apps can use this endpoint to check whether a customer already has an active window before they create a new order. If the order create request comes back with PAYCHAIN_ACTIVE_INTENT_CONFLICT, inspect the returned conflict.activeIntent data and decide whether to ask the customer to wait or resend the order with overrideActiveIntent: true.

​
Get the active window

GET /api/developer/orders/intent
​
string
required
The customer or user identifier used when the order was created.
​
string
required
The token symbol, such as USDT or USDC.
​
string
required
The network for the order, such as base, bsc, or solana.
If there is no active window for that customer and rail, RampHub returns 404.

​
How API clients should use this

  • Call this endpoint before order creation if you want to show the active window first.
  • Handle PAYCHAIN_ACTIVE_INTENT_CONFLICT from POST /api/developer/orders as a normal product flow, not as a fatal error.
  • If the customer chooses to continue and replace the active order, resend the order request with overrideActiveIntent: true.

​
Conflict response from order creation

When an active window already exists, the order create endpoint can return a structured response like this:
Your app can use the conflict object to show the current window to the customer, then either wait or resend the order with overrideActiveIntent: true.