Dexly (Hyperliquid) API integration & on-chain perp data services

1. Wallet session & authorization

Protocol analysis of Dexly's WalletConnect v2 handshake and of the third-party Privy email-wallet flow. We map session topics, agent-wallet signatures and device biometric gating to a stable server-side session model, so a back-office tool can call APIs on behalf of a trader without ever touching seed phrases.

Use: unify multi-wallet login across desktop dashboards and mobile devices for a trading desk or family office.

2. Positions & margin sync

Exposes clearinghouseState equivalents — account value, total margin used, maintenance margin, cross/isolated mode, leverage per asset, and liquidation price — into a normalised schema. Deltas can be streamed as Kafka events or CSV snapshots.

Use: automated margin-call alerting and daily risk reports that combine Dexly positions with CEX accounts.

3. Order and fill history

Structured export of open, filled and cancelled orders: order id, cloid, side, size, price, trigger, time-in-force, fee and fill time. Supports paging by time window and by wallet address.

Use: trade reconciliation and best-execution reports for funds trading on Hyperliquid via Dexly.

4. Funding, orderbook & mark data

Real-time funding rate, predicted funding, L2 orderbook snapshots, trade prints and mark price per market. Delivered over WebSocket with a REST fallback for backfill.

Use: feed a quant signal pipeline or a third-party charting product with institution-grade on-chain perp data.

5. HIP-3 market catalog

Hyperliquid's HIP-3 framework lets third parties deploy their own perp markets (indices, commodities, long-tail assets). We maintain a nightly catalog job that pulls active perp dexes, maxLeverage, szDecimals and listing status, so your frontend or pricing engine always knows which symbols are tradeable inside Dexly today.

Use: dynamic symbol onboarding for a portfolio tracker that wants to follow new on-chain markets as soon as they launch.

6. PnL, fees & ledger

Historical ledger of deposits, withdrawals, funding payments, referral rewards and realized PnL, reshaped into a double-entry friendly format suitable for accounting imports.

Use: monthly tax and accounting packs for traders who need a clean general-ledger view instead of raw on-chain transfers.

Scenario A — Fund risk dashboard

Context: A crypto fund has 12 trading wallets split across desk members, all using Dexly on mobile and Hyperliquid on desktop.

Data & API: positions, clearinghouseState, fills, funding history per wallet, aggregated on our side into a single /v1/desk/exposure REST response.

OpenFinance mapping: Same pattern as a consent-based account-aggregation service: explicit per-wallet authorization, read-only scope, append-only audit log.

Scenario B — Accounting & tax export

Context: A trader needs a monthly CSV that their accountant can reconcile with bank statements.

Data & API: Ledger of deposits, withdrawals, funding, realized PnL, fees; reformatted into a double-entry CSV plus a PDF summary. Endpoint: GET /v1/ledger?wallet=0x…&from=…&to=….

OpenFinance mapping: Equivalent to a statement export in retail banking — same deliverable, just sourced from on-chain perp activity instead of a current account.

Scenario C — Market-making backfill

Context: A small market maker wants orderbook and trade prints for research across 40 Hyperliquid markets (including HIP-3 listings).

Data & API: WebSocket subscription to l2Book and trades, plus REST candleSnapshot for backfill. Normalized parquet files delivered to S3.

OpenFinance mapping: Mirrors market-data vendor patterns (Refinitiv / Bloomberg feeds) adapted to an on-chain order book.

Scenario D — Compliance & audit trail

Context: A regulated prop firm needs proof that all trades on its books actually came from firm-owned wallets used in Dexly.

Data & API: Wallet allowlist, signed message attestations, fills cross-checked with on-chain Hyperliquid events, exposed via a /v1/compliance/attest endpoint.

OpenFinance mapping: Consent + strong customer authentication patterns from PSD2 / SCA, translated into wallet signature + device attestation.

1. Request — positions snapshot

POST /api/v1/dexly/positions
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "wallet": "0x4A...f12c",
  "include": ["assetPositions", "marginSummary", "liquidationPx"]
}

200 OK
{
  "wallet": "0x4A...f12c",
  "equity": "128450.22",
  "marginSummary": { "accountValue": "128450.22", "totalMarginUsed": "31200.10" },
  "positions": [
    {
      "coin": "ETH",
      "szi": "-12.4",
      "entryPx": "3482.5",
      "unrealizedPnl": "-142.18",
      "leverage": { "type": "cross", "value": 10 },
      "liquidationPx": "3891.7"
    }
  ]
}

2. WebSocket — orderbook & fills

// Subscribe to L2 book + user fills
ws.send(JSON.stringify({
  method: "subscribe",
  subscription: { type: "l2Book", coin: "BTC" }
}));

ws.send(JSON.stringify({
  method: "subscribe",
  subscription: { type: "userFills", user: "0x4A...f12c" }
}));

// Incoming frame (trimmed)
{
  "channel": "userFills",
  "data": {
    "fills": [
      { "coin": "BTC", "px": "64210.5", "sz": "0.25",
        "side": "B", "time": 1734028812345,
        "fee": "0.80", "oid": 98765432 }
    ]
  }
}

3. Webhook — HIP-3 market onboarding

POST https://customer.example.com/hooks/hip3
X-Signature: sha256=...
Content-Type: application/json

{
  "event": "market.listed",
  "dex": "perp-dex-03",
  "symbol": "GOLD-PERP",
  "category": "commodity",
  "maxLeverage": 20,
  "szDecimals": 3,
  "firstSeenAt": "2026-04-17T02:14:55Z"
}

// On error we retry with exponential backoff (1s, 5s, 30s, 5m, 30m)
// and expose a replay endpoint: GET /v1/webhooks/replay?from=...

Compliance & privacy

Dexly is a non-custodial interface, which shapes how we design every integration: we never ask customers for seed phrases, and never persist raw private keys. Read-only flows use Hyperliquid agent wallets (API wallets) that can sign trading actions but cannot withdraw funds, matching Hyperliquid's own security guidance.

For customers who process EU or UK users, pipelines are configured under GDPR and UK DPA 2018: explicit consent per wallet, data-minimisation, a documented retention window and a signed Data Processing Agreement. Where Open Banking parallels apply, we align with PSD2 / SCA patterns (strong customer authentication on each new device, short-lived tokens).

On the crypto side we track evolving rules — MiCA in the EU and FATF's Travel Rule — and can add counterparty tagging, travel-rule metadata and sanctioned-address screening to any export pipeline. We do not offer investment advice and mirror Dexly's own notice that leveraged perps carry significant risk.

Data flow / architecture

A typical pipeline has four nodes and stays intentionally boring so it is easy to audit:

1. Client — Dexly mobile app + Hyperliquid node RPC / WebSocket.
2. Ingestion — our stateless collectors handle auth, rate limiting, and schema validation.
3. Storage — normalized events in Postgres + cold parquet on object storage for backfill.
4. Output — REST + WebSocket APIs, signed webhooks, and CSV / Excel exports consumed by the customer's BI, risk or accounting stack.

Every layer emits structured logs, and we ship a minimal Grafana dashboard (lag, error rate, per-wallet coverage) with the source code.

Aster DEX

Multi-chain perp DEX (BNB, Ethereum, Solana, Arbitrum) that pushes very high leverage and stock-style perps. Similar data needs — positions, orders, funding — with an additional layer of yield-bearing collateral events to capture.

dYdX (v4)

Professional on-chain order book on its own Cosmos app-chain. Integrators frequently ask for unified transaction exports across Dexly/Hyperliquid and dYdX, especially for fund reporting.

GMX

Pool-based (GLP) perp DEX on Arbitrum and Avalanche. The data model is different — LP positions and pool PnL — but it routinely sits next to Hyperliquid exposure in treasury dashboards.

Lighter

ZK-rollup-based DEX on Ethereum with near-CEX performance. Its zero-fee retail structure and verifiable matching produce yet another orderbook feed that fits alongside Dexly in a multi-venue data lake.

Drift Protocol

Solana-native perp DEX using a hybrid DAMM/DLOB/JIT model. Users who bridge between Solana and Hyperliquid often need a single PnL view spanning both networks.

Aevo

Derivatives-focused L2 known for pre-launch futures and unified margin. Integration patterns mirror Hyperliquid's — fills, funding, positions — with the extra wrinkle of options data.

MUX Protocol

Cross-chain aggregator routing across Arbitrum, BNB Chain, Avalanche and Optimism. Customers combining MUX with Dexly typically want a chain-agnostic order view.

Kwenta (Synthetix)

Synthetix-powered perps front-end on Optimism. Its debt-pool model contrasts with Hyperliquid's book-based design, but the downstream reporting shape is similar.

Gunbot

Automated trading bot with a documented Hyperliquid integration — a good reference point for how non-custodial wallet-signed API flows can be productised for retail users.

UniDex

Aggregator-style perp frontend across multiple chains. Integrators that list UniDex alongside Dexly usually need a normalised symbol map to reconcile identical instruments across venues.

Deliverables checklist

• API specification (OpenAPI / Swagger) covering every endpoint we expose on top of Dexly / Hyperliquid
• Protocol & auth report — WalletConnect session topology, agent-wallet signing, Privy flow observations
• Runnable source code (Python / Node.js / Go) for positions, orders, fills, PnL and HIP-3 catalog
• WebSocket client with reconnect, backfill and idempotent event replay
• Automated test suite (unit + golden-file integration tests) and Postman collection
• Compliance pack — consent template, retention policy, GDPR DPA draft, travel-rule checklist
• Grafana dashboard + alerting rules for lag, error rate and per-wallet coverage

Engagement models

• Source code delivery from $300 — you receive runnable API source and documentation; payment after delivery on your acceptance.
• Pay-per-call API billing — hit our hosted endpoints and pay only for the calls you make. No upfront fee, ideal for usage-based teams.
• Optional retainer for HIP-3 market tracking and monthly protocol-change monitoring.

About our studio

We are a small, senior studio focused on App interface integration and authorized API integration. Our engineers come from mobile teams, fintech backends, derivatives exchanges and cloud platforms. We have shipped integrations against custodial exchanges, open-banking aggregators and, increasingly, on-chain perp venues like Hyperliquid, dYdX and Aevo.

Workflow stays the same regardless of venue: protocol analysis → build → validation → compliance. We prefer documented public APIs and authorized reverse engineering of app traffic over anything grey-area, and we sign NDAs and DPAs by default.

Customers describe the target app and what they need to do with the data; we deliver either runnable source code or a hosted endpoint that speaks a stable schema, with the paperwork, tests and dashboards that production teams actually care about.

Contact

Share the target app name (already known: Dexly — Trade on Hyperliquid) and a short description of the data or flows you need. We reply within one business day with scope, timeline and a fixed quote.

Open contact page

Prefer pay-per-call? Mention it in your message and we will provision a sandbox key on our hosted Dexly / Hyperliquid endpoints.

Engagement workflow

1. Scope call — confirm which Dexly / Hyperliquid surfaces matter (positions, fills, HIP-3, PnL, etc.).
2. Protocol analysis & API design — 2–5 business days depending on coverage.
3. Build & internal validation — 3–8 business days, with daily progress updates.
4. Docs, examples, test cases and Postman collection — 1–2 business days.
5. Handover & acceptance window — typical first delivery lands in 5–15 business days.

FAQ

Do you need my seed phrase or private key?

What if Hyperliquid changes an endpoint?

Can you cover both Dexly Android and iOS traffic?

Do you handle multi-venue projects?