Get clearinghouse state

curl --request POST \
  --url 'https://api.hypedexer.com/info#clearinghouseState' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "clearinghouseState",
  "user": "0xabc..."
}
'

{}

{
  "error": "user or users required"
}

{
  "error": "Invalid API key"
}

{
  "error": "Upstream unreachable: connection refused"
}

POST

info#clearinghouseState

curl --request POST \
  --url 'https://api.hypedexer.com/info#clearinghouseState' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "type": "clearinghouseState",
  "user": "0xabc..."
}
'

{}

{
  "error": "user or users required"
}

{
  "error": "Invalid API key"
}

{
  "error": "Upstream unreachable: connection refused"
}

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:

clearinghouseState

user

string

Single Ethereum address

Example:

"0xabc..."

users

string[]

List of Ethereum addresses (multi-user mode)

dex

string

DEX filter

Example:

"ORCA"

Response

Clearinghouse state. Single user: upstream result directly. Multi-user: { address: result } map.

Option 1
Option 2

Single-user result (upstream response as-is)

Introduction

Live Data REST API

Live Data WebSocket API

Authorizations

Body

Response