Post by Arman about Orca DEX ($ORCA)

$ORCA RCA I tested Orca’s public pool API. GET /pools?size=2 returned two pools, but the API overview and pool response example show meta.next, while the live response uses meta.cursor.next.

Following the documented structure could make a client stop after that first page. Passing the value of meta.cursor.next as the next query parameter returned two more distinct pools. Both test runs gave the same result.

Suggestion: update both examples to match the OpenAPI schema, which already has the correct nesting. Could you also add a complete second-page request? That would help someone building a pool picker avoid leaving out results without realizing it.

Only the first two pages were tested. No wallet was connected and no transactions were sent.

Links:
https://docs.orca.so/api-reference/overview#response-format

https://docs.orca.so/api-reference/whirlpools

https://api.orca.so/docs