VIP Tiers
VIP tiers govern your fee schedule and rate limits.
The live routes are GET /api/v1/tiers/status and GET /api/v1/tiers/config.
Where to read tier data
| Data | Source |
|---|---|
| Your current tier, fees, rolling 30d volume, next-tier progress | GET /api/v1/tiers/status |
| All live tier configurations | GET /api/v1/tiers/config |
| Account margin / equity | Encrypted POST /api/v1/account |
| Published schedule (Core → Apex) | The table on Fee Structure |
| Instrument-default fees | GET /instruments (tier-0 defaults only) |
GET tier status
Authoritative source for your fee schedule. Use this at login and refresh daily.
GET /api/v1/tiers/status
Auth: Authorization: Bearer <access_token> (REST JWT).
curl the REST origin/api/v1/tiers/status \
-H "Authorization: Bearer $TOKEN"
Response
{
"user_id": "5b7d...",
"current_tier": 3,
"tier_name": "Advanced",
"current_volume": "12450000",
"progress_to_next": "5.44",
"volume_to_next_tier": "37550000",
"current_config": {
"tier_level": 3,
"tier_name": "Advanced",
"min_volume": "10000000",
"maker_fee_bps": "0.5",
"taker_fee_bps": "4.0",
"maker_fee_pct": "0.005",
"taker_fee_pct": "0.040",
"benefits": {
"minimum size": 75,
"tier_protection_days": 7,
"vip_support": null,
"features": ["community_access", "standard_support"]
}
},
"next_config": {
"tier_level": 4,
"tier_name": "Prime",
"min_volume": "50000000",
"maker_fee_bps": "0.0",
"taker_fee_bps": "3.0",
"maker_fee_pct": "0.000",
"taker_fee_pct": "0.030",
"benefits": {}
}
}
Field Reference
| Field | Description |
|---|---|
current_tier / tier_name | Current tier level and label |
current_volume | Qualifying trailing-volume decimal string |
progress_to_next | Progress percentage as a decimal string |
volume_to_next_tier | Additional volume required |
current_config / next_config | Fee and benefit configuration objects |
GET tier config
GET /api/v1/tiers/config is public and returns a JSON array of the same configuration objects, ordered by tier_level. Use it for schedule display; use /tiers/status for the authenticated user's assignment.
Fee Authority
The tier routes expose decimal strings. Do not derive fees from retired bonus fields. See Fee Structure for the current migration-backed schedule.
See Fee Structure for how fees are collected and settled.