Implement Admin List Users API

[thlpkee20-wq]

Description
Implement GET /api/admin/users for an admin role to list users with optional filters and pagination. Require admin JWT or API key. Do not expose in public OpenAPI if internal-only.

Requirements and context

• Implement only in new files. Add src/routes/admin/users.ts and use user repository. Do not modify package.json, src/index.ts. Add admin auth check (middleware or inline).

Suggested execution

• Branch: git checkout -b feature/admin-list-users
• Add route and tests. Example commit message: feat(api): add admin list users endpoint

Guidelines

• Only new route file under src/routes/admin/. Timeframe: 96 hours.

[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

[jayjayScript]

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

over Letter: Admin List Users API Implementation
I'm applying for this task because backend API challenges like this are exactly where I thrive. Implementing secure, filtered list endpoints with proper admin authorization is the kind of problem-solving that keeps me sharp—balancing clean architecture with security requirements.
I have solid experience building REST APIs with TypeScript, authentication middleware, and repository patterns. This task aligns perfectly with my skills: scoped routes, JWT validation, and clean separation of concerns without touching core files.
I'm ready to deliver a well-tested, production-ready implementation within the 96-hour window.

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

[drips-wave]

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

🧑‍💻 @jayjayScript: 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 🌊

[Christopherdominic]

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

Hi 👋

I’d like to work on this issue.

I’ve reviewed the description and acceptance criteria, and I’m confident I can implement the required changes following the project’s guidelines and coding standards. I’ll ensure proper testing and documentation where applicable.

Please assign this issue to me — I’ll get started right away. 🚀

Thank you!

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

[rosemary21]

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

Please assign i can quickly complete before deadline . I’d be glad to take on this issue because it involves a combination of secure access control, clean API design, and scalable data retrieval (filters + pagination) — all of which are critical in admin-facing functionality. Admin endpoints are especially sensitive, and implementing them correctly helps ensure operational visibility without compromising security.

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

[SamixYasuke]

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

Hello maintainer, I can get this done ASAP, thanks

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

[Jayrodri088]

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

I'll create src/routes/admin/users.ts implementing GET /api/admin/users for admin role user listing with pagination (limit, offset) and optional filters (username, email, status, createdAfter, createdBefore). Admin auth via JWT role check (user.role === 'admin') or API key header validation using existing auth middleware pattern, returning 401/403 for unauthorized access.

Query uses Prisma findMany() with select excluding sensitive fields (password hash, 2FA secret), supports sorting (createdAt desc), and total count for pagination metadata. Response: { users: User[], total: number, page: number, pages: number }. Excluded from public OpenAPI via @ApiHideEndpoint() or file-based routing convention. Includes rate limiting and audit logging. ETA: 3 hours

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

[meshackyaro]

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

I'll like to work on this issue because I'm familiar with the codebase. Please assign this to me

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

[AliFikan94]

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

I'm eager to contribute to RevoraOrg/Revora-Backend, which appears to be building a robust backend (likely Node.js/NestJS + PostgreSQL based on similar Stellar ecosystem repos) for managing users, startups, investors, and offerings in a Stellar-powered platform—possibly for tokenized assets, investments, or ecosystem tools. Implementing a secure, efficient Admin List Users API (e.g., GET /admin/users with pagination, filters by role/email/status, role-based access control, and proper serialization) is a foundational piece for admin dashboards, user management, compliance, and overall platform ops. It aligns perfectly with other Revora issues like login, registration, offerings CRUD, and investment flows.Relevant experience:Built and deployed multiple admin/user management APIs in NestJS/Express backends, including paginated list endpoints with Prisma/TypeORM queries, role guards (e.g., @roles
('admin')), filtering (status, role, search), and secure output (exclude sensitive fields like passwords/hashes).
Implemented RBAC and JWT auth for admin routes in Stellar/Soroban-related projects, ensuring only authorized admins can access user lists while complying with data privacy basics.
Handled pagination (cursor-based or offset/limit), sorting, and search in production APIs serving 1k+ users, with tests via Jest/Supertest.
Familiar with PostgreSQL queries for efficient user listing (joins, indexes on email/role), error handling, and logging for audit trails.

I can deliver a clean PR including:New controller/service/route for the admin users list endpoint.
Query params support (page, limit, search, role filter, etc.).
Admin guard/decorator + serialization to hide sensitive data.
Integration with existing auth/DB setup (assuming Prisma or similar).
Unit/integration tests and Swagger/OpenAPI docs update.
Clear README additions or comments.

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