Skip to content

API Introduction

Openfish exposes several HTTPS services. The current openfish.me deployment is an isolated meme environment: trading balances are denominated in the configured platform meme token, and the Bridge API only supports the configured BSC platform meme ERC-20.


https://api.openfish.me (port 3002)

The central trading service. Provides order book snapshots, live pricing, browse data, order lifecycle operations, and internal trading balance updates. Trading write operations require authenticated headers.

https://data.openfish.me (port 3003)

Aggregated analytics and portfolio data, including user positions, trades, activity feeds, open interest, and value endpoints.

https://gamma.openfish.me (port 3001)

The discovery and social layer. Surfaces markets, events, tags, comments, search results, and public profiles.

https://bridge.openfish.me (port 3004)

Meme bridge service for deposits and withdrawals. In the current meme environment it supports only the configured BSC platform meme ERC-20. It does not support USDC, USDC.e, Solana, Bitcoin, cross-chain swaps, or automatic conversion.


Read-only browse, market data, and public discovery endpoints are open to callers without credentials.

Trading operations on the CLOB API require L2 authentication headers. Administrative endpoints are only available through the admin server.


Before integrating an endpoint, check whether it is part of the current public product surface.

LevelUse
PublicSafe for unauthenticated public clients
AuthenticatedSafe for user-authenticated trading clients
BuilderSafe for builder-attributed integrations
Admin-only / InternalOperator-only, not for public clients
DisabledDo not integrate

See Endpoint Support Levels for the current matrix.