Public Info API

#Introduction

The PangoPerps Public Info API provides read-only market, account, and platform data through one unauthenticated query endpoint. Set the type field to choose from 24 query types. No API key or signature is needed, including for queries that look up an account by wallet address. Monetary values are returned as decimal strings so clients can process the raw data and calculate their own indicators. This interface has a rate-limit pool separate from the REST and WebSocket APIs.

It is useful for public dashboards, AI trading agents, quantitative analysis, copy-trading tools, address monitoring, and strategy backtesting. It can retrieve an address's positions, orders, fills, and PnL, as well as aggregated market or platform data. It is read-only: it cannot place orders, move funds, or change account settings.

#Quick start

Each request is a JSON POST to the same endpoint. The type field selects the query.

Market snapshot:

curl -s -XPOST -H "Content-Type: application/json" \
  https://api.orderly.org/v1/public/query \
  -d '{"type":"marketSummary"}'

Account state for a wallet:

curl -s -XPOST -H "Content-Type: application/json" \
  https://api.orderly.org/v1/public/query \
  -d '{"type":"accountState","address":"0x1234567890abcdef1234567890abcdef12345678","broker_id":"pangoperps"}'

Check the available request quota:

curl -s -XPOST -H "Content-Type: application/json" \
  https://api.orderly.org/v1/public/query \
  -d '{"type":"rateLimitStatus"}'

#Endpoint

POST https://api.orderly.org/v1/public/query
Content-Type: application/json

{ "type": "<query type>", "...": "..." }

Every query uses this URL. Include the query parameters in the JSON request body. The type value determines which handler processes the request.

#Response format

Success:

{
  "success": true,
  "data": {
    "...": "query-specific result"
  },
  "ts": 1779269143700
}

Error:

{
  "success": false,
  "code": "INVALID_PARAM",
  "message": "...",
  "type": "<requested type>",
  "ts": 1779269143700
}

ts is the server's response timestamp in milliseconds since the Unix epoch (UTC).

#Error codes

A RATE_LIMIT_EXCEEDED response also includes retry_after as a millisecond epoch and a Retry-After HTTP header in seconds.

#Address resolution

For requests with an address, the service looks up the accounts associated with that wallet. Use the optional broker_id and account_id fields to narrow the result:

For PangoPerps-scoped account lookups, set broker_id to pangoperps. If no matching account exists, the API returns ADDRESS_NOT_FOUND with HTTP status 404. The accountState and feeRate response formats differ depending on whether an account_id is included; see their individual sections.

#Pagination

Paginated queries return data.next_cursor. Submit that value as cursor in the next request. The value is an opaque Base64 cursor; pass it back as-is rather than parsing it. It is null when the final page has been reached. Cursor internals differ by query and can change.

marketSummary, marketTrades, fundingComparison, orderbook, and rateLimitStatus return their bounded result in one response and do not paginate.

#Time conventions

• All timestamps are Unix epoch milliseconds in UTC.
• Valid timestamp values range from 0 through 253402300799000 (year 9999). Values outside this range return INVALID_PARAM.
• Some queries align their default lookback period to UTC day boundaries; the applicable query section identifies those defaults.

#Rate limits

This API uses a quota separate from the REST and WebSocket interfaces: calls here do not use their quota, and their calls do not use this quota. Usage is measured in weight units per IP over a rolling one-minute window. An anonymous IP has a default allowance of 1,200 weight units per minute. Each query type consumes the following weight; lighter queries are preferable for frequent polling.

Every response includes:

X-RateLimit-Limit: 1200
X-RateLimit-Remaining: 1148
X-RateLimit-Reset: 1779269200000
X-RateLimit-Weight: 2

X-RateLimit-Weight reports the weight charged for that request. X-RateLimit-Reset gives the end of the current window as a millisecond epoch.

When the quota is exceeded, the server responds with HTTP 429 and includes a Retry-After header (seconds):

{
  "success": false,
  "code": "RATE_LIMIT_EXCEEDED",
  "message": "Rate limit exceeded. Retry after 1779269200000",
  "retry_after": 1779269200000,
  "ts": 1779269143700
}

#rateLimitStatus

This query reports the calling IP's quota state for the current rolling one-minute window. Its weight is 0, so checking it does not consume quota and it can be called on each polling iteration.

Request:

{ "type": "rateLimitStatus" }

Response:

{
  "success": true,
  "data": {
    "limit": 1200,
    "remaining": 500,
    "reset": 1779269200000,
    "tier": "default"
  },
  "ts": 1779269143700
}

#Data freshness

The table gives worst-case age for each query or field; data is often newer. Polling more frequently than these windows does not make the underlying data fresher. X-Data-Freshness records the server response time, not the generation time of the data.

For multi-source bundles, sections can have different ages. agentContext and positionContext reflect the oldest section in their bundle. Trade fills within 24 hours are real time; older fills are read from an archive that refreshes hourly.

#Query types

The 24 types are grouped as follows:

#Market data

• candles
• fundingComparison
• fundingRateHistory
• liquidations
• marketDetail
• marketSummary
• marketTrades
• orderbook

#Account data

• accountState
• accounts
• agentContext
• feeRate
• fundingPayments
• historicalOrders
• openOrders
• orderStatus
• portfolio
• positionContext
• trades
• userDepositsWithdrawals
• whaleContext

#Platform data

• platformPositions
• topAddresses