Endpoint to Fetch Users

🛠️ Fetching Users

📋 Endpoints Required

• GET /api/v1/users — List all resources (paginated)
• GET /api/v1/users/:id — Get a single resource by ID

🗂️ Data Schema

Describe or paste the expected request/response shape below.

NA - GET requests

---

## ✅ Acceptance Criteria
- [X] All endpoints return correct HTTP status codes
- [ ] Input validation is applied to request bodies and query params
- [X] Errors return consistent, descriptive JSON responses
- [ ] Endpoints are protected by appropriate auth/authorization middleware
- [X] Pagination supported on the list endpoint
- [X] Unit tests cover each endpoint (happy path + error cases)
- [X] Integration tests pass in CI
- [ ] OpenAPI / Swagger docs updated

---

## 🔒 Auth & Permissions
<!-- Describe which roles can access endpoints -->

---

## 🔗 Related

<!-- Any related links -->
---

## 💬 Additional Context
<!-- Any edge cases, business rules, soft deletes, cascades, rate limits, or other notes -->

Start by locating the API entry points that serve GET /api/v1/users and GET /api/v1/users/:id. Review the existing endpoint tests and authentication, validation, and OpenAPI conventions before determining which unchecked acceptance criteria remain. Done means the listed validation, authorization, and documentation requirements are addressed without regressing the checked criteria.