Skip to main content
POST
User fee schedule

Authorizations

Authorization
string
header
required

Optional. API key passed via Authorization: Bearer <key>. Required only when API_KEY is configured on the server.

Body

application/json
type
enum<string>
required
Available options:
userFees
user
string
required

42-character hex address

Example:

"0xabc..."

Response

Fee schedule and rates

dailyUserVlm
array

Daily volume breakdown

feeSchedule
object

Fee tier schedule

userCrossRate
string
Example:

"0.000315"

userAddRate
string
Example:

"0.0001"

activeReferralDiscount
string
Example:

"0.0"