Temp API

Temporary holding area for short-lived endpoints

The Temp API is a temporary holding area for endpoints that do not yet have a permanent home in the main Raydium APIs. This service is intended for rapid prototyping, internal tools, and features under active development.

Hosts

Environment	Host
Mainnet	temp-api-v1.raydium.io
Devnet	temp-api-v1-devnet.raydium.io

Stability warning

This service has no API stability guarantees. Endpoints may change, be deprecated, moved to another service, or removed entirely without notice. Use this API only for:

• Internal tools and scripts
• Features in active development
• Non-critical paths that can tolerate breakage
• Testing and prototyping

Do not depend on this API for production dApps or critical integrations.

Overview

This service currently exposes:

• /cp-creator-fee — Retrieve accumulated creator fees for a wallet across CPMM pools.
• /limit-order/order/list — A wallet’s currently-parked CLMM limit orders (open and partially-filled) served from the indexer cache.
• /limit-order/history/order/list-by-user — A wallet’s historical (closed) CLMM limit orders, with optional poolId / mint1 / mint2 / hideCancel filters; cursor-paginated via nextPageId.
• /limit-order/history/event/list-by-pda — Per-PDA event log (open / increase / decrease / settle / close) for one or more limit-order PDAs; cursor-paginated via nextPageId.

Common patterns

Check creator fees for a wallet

curl -s "https://temp-api-v1.raydium.io/cp-creator-fee?wallet=<your-wallet-pubkey>"

Returns a list of pools where the wallet is the creator, along with accumulated but unclaimed creator fees in Token A and Token B.

List a wallet’s currently-parked CLMM limit orders

curl -s "https://temp-api-v1.raydium.io/limit-order/order/list?wallet=<your-wallet-pubkey>"

Returns both fully-unfilled and partially-filled orders. Each row is a decoded LimitOrderState (PDA, pool, owner, tick, side, FIFO cohort phase, total/filled amounts) plus the pool context needed to call SettleLimitOrder, including a precomputed pendingSettle amount.

The active-orders endpoint is unpaginated — it returns all of the wallet’s currently-cached orders in one payload.

List a wallet’s closed limit orders

curl -s "https://temp-api-v1.raydium.io/limit-order/history/order/list-by-user?wallet=<your-wallet-pubkey>&size=50"

Returns a page of historical orders, each summarized with fillStatus (NONE / PARTIAL / FULL) and the input/output amounts at the time the order left the active set. Append &nextPageId=<previous response's nextPageId> to fetch the next page.

Pull the event timeline for a specific order

curl -s "https://temp-api-v1.raydium.io/limit-order/history/event/list-by-pda?pda=<limit-order-pda>"

pda may be a single key or a comma-separated list. Each row is one on-chain mutation (open / increase / decrease / settle / close) with txid, slot, block time, signed-by-owner-or-keeper flag (autoRunner), and the input/output deltas in human units.

Empty result

If the wallet has no records cached, the active-orders endpoint returns:

{
  "id": "...",
  "success": true,
  "data": { "rows": [] }
}

The history endpoints return the same { rows: [], nextPageId?: ... } shape with an empty rows array. The legacy /cp-creator-fee endpoint instead returns "data": [] for backward compatibility.

Related docs

See CPMM for pool structure and creator fee mechanics, and CLMM → Instructions for the on-chain limit-order flow these endpoints surface.