Skip to main content

Documentation Index

Fetch the complete documentation index at: https://hypernode-docs.polynode.dev/llms.txt

Use this file to discover all available pages before exploring further.

Decodes #N coin names or numeric asset_ids into structured outcome metadata. Use this when you have a coin reference from somewhere (a fill, an order) and need to know what market + side it’s for.

​
Endpoint

GET /v1/coins/:coin
The :coin path parameter accepts:
  • #N (URL-encoded as %23N) — e.g. /v1/coins/%230
  • A bare integer N — e.g. /v1/coins/0
  • A full asset_id — e.g. /v1/coins/100000000

​
Response

{
  "coin": {
    "raw": "#0",
    "outcome_id": 0,
    "side_index": 0,
    "asset_id": 100000000,
    "side_label": "Yes",
    "market_title": "BTC >= $78213 by 2026-05-03 06:00 UTC (1d)"
  },
  "outcome": {
    "outcome_id": 0,
    "name": "Recurring",
    "title": "BTC >= $78213 by 2026-05-03 06:00 UTC (1d)",
    "status": "active",
    "underlying": "BTC",
    "target_price": "78213",
    "expiry_str": "20260503-0600"
  }
}
FieldDescription
coin.rawThe #N form
coin.outcome_idDecoded N / 10
coin.side_indexDecoded N % 10
coin.asset_id100_000_000 + N
coin.side_label"Yes" for side 0, "No" for side 1
coin.market_titleHuman-readable composed title
outcomeFull outcome metadata (or null if not found)

​
Why use this

When a webhook gives you a fill with coin: "#0", you don’t have to maintain a coin → market map yourself. Resolve it once, cache it client-side. The market_title is suitable for direct display.

​
Examples

curl -H "X-API-Key: hip4_live_..." \
  "https://hip4.polynode.dev/api/v1/coins/%230"