GET /v1/users/featured returns 404, POST /v1/users/:id/follow returns 400 #76
Description
Summary
Three user-related endpoints on the /quran-reflect/v1 service return unexpected error codes during E2E testing.
1. GET /quran-reflect/v1/users/featured → 404 Not Found
The featured users endpoint returns 404 as if the route doesn't exist on the prelive environment.
Request:
GET https://apis-prelive.quran.foundation/quran-reflect/v1/users/featured
Headers: x-auth-token: <valid token>, x-client-id: <client id>
Expected: A list of featured users (or empty array).
Actual: 404 Not Found
2. POST /quran-reflect/v1/users/{followeeId}/toggle-follow → 400 Bad Request
Attempting to follow a user returns 400 Bad Request.
Request:
POST https://apis-prelive.quran.foundation/quran-reflect/v1/users/6d6798c4-4a4a-4df6-b137-8d893d999bda/toggle-follow
Body: {"action": "follow"}
Headers: x-auth-token: <valid token>, x-client-id: <client id>
Expected: Follow toggled successfully.
Actual: 400 Bad Request
3. POST /quran-reflect/v1/users/{followerId}/remove-follower → 400 Bad Request
Attempting to remove a follower returns 400.
Request:
POST https://apis-prelive.quran.foundation/quran-reflect/v1/users/fake-id/remove-follower
Headers: x-auth-token: <valid token>, x-client-id: <client id>
Note: The fake ID would explain a 404, but 400 suggests a request format issue rather than a missing resource.
Context
Other user endpoints on the same service work fine with the same token:
GET /quran-reflect/v1/users/:id→ 200 ✓GET /quran-reflect/v1/users/search→ 200 ✓GET /quran-reflect/v1/users/:id/followers→ 200 ✓GET /quran-reflect/v1/users/:id/following→ 200 ✓GET /quran-reflect/v1/users/my-rooms→ 200 ✓
Tested against: https://apis-prelive.quran.foundation/quran-reflect/v1