Pagination standard (cursor vs offset)

[aji70]

Description
The goal is to standardize list APIs. Choose cursor-based or offset-based pagination and apply to subscriptions, creators, and posts list endpoints. Use consistent query params (e.g. limit, cursor or offset) and response shape (next_cursor or total).

Tasks

• Define standard params and response shape
• Implement cursor or offset in subscriptions list
• Implement in creators list
• Implement in posts list
• Add tests for empty, one page, next page

Acceptance Criteria

• All list endpoints use same pagination pattern
• Clients can page through all results
• Tests pass

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[okekefrancis112]

@okekefrancis112 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I would like to apply to this issue. I’m a full-stack smart contract and backend engineer with experience building and integrating production systems across web2 and web3. I work with NestJS, Node.js, TypeScript, and SQL/NoSQL databases to design clean, scalable APIs, and I’ve also built and integrated smart contracts, including working with Soroban on Stellar to manage contract state, construct transactions, and connect on-chain logic with backend services. I’m comfortable navigating existing codebases, following established project patterns, and contributing well-documented, testable changes that are easy to review and maintain in an open source environment.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @okekefrancis112 to this issue.

[drips-wave]

Congratulations, @okekefrancis112! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @okekefrancis112: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @okekefrancis112 as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @okekefrancis112: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.