/solscan/accounts/portfolio

POST /api/solscan/accounts/portfolio

Price: 1 credit

List the DeFi liquidity positions of a Solana account by its address

How to use it

List the DeFi liquidity (LP) positions of a Solana wallet by its address, ordered by value. Returns each position's id, pool, program (DEX), position type (e.g. clmm), the two pooled token mints and amounts, the position USD value, the current/lower/upper price range, whether it is in range, and the creation time.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• address string required — Solana account or token mint address (base58) (examples: "5tzFkiKscXHK5ZXCGbXZxdw7gTjjD1mBwuoFbhUvuAi9")
• count integer required — Max number of positions to return (min: 1)
• sort_order string — Order positions by value (default: "desc"; one of: "desc", "asc")

Response

• @type string (default: "SolscanDefiPosition")
• position_id string required
• pool_id string nullable
• program string nullable
• position_type string nullable
• token_address string nullable
• token_1 string nullable
• token_2 string nullable
• amount_1 number nullable
• amount_2 number nullable
• position_value number nullable
• current_price number nullable
• lower_price number nullable
• upper_price number nullable
• is_in_range boolean nullable
• created_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Account not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.