You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create an API endpoint to retrieve the details of a registered user's information for the admin user. This endpoint will be part of the administration user management. Admin users can see in-depth information about a user using this endpoint
Acceptance Criteria
The endpoint should be accessible at GET /api/v1/admin/users/{id}.
The endpoint should accept HTTP GET requests.
The endpoint should retrieve up-to-date information about a registered user from the database using the provided user's ID.
The endpoint should return a 200 OK status code with the user's details in the response body
This endpoint should be secured and only accessible to an admin user
GET /api/v1/admin/users/3454 Response:
On a successful retrieval of the user details, the API should return a 200 OK status code. The response body should contain the user details:
Description
Create an API endpoint to retrieve the details of a registered user's information for the admin user. This endpoint will be part of the administration user management. Admin users can see in-depth information about a user using this endpoint
Acceptance Criteria
GET /api/v1/admin/users/3454
Response:
On a successful retrieval of the user details, the API should return a 200 OK status code. The response body should contain the user details:
Validation:
If the user's ID is missing or invalid, the API should return a 400 Bad Request status code with appropriate validation error messages:
If the user does not exist, the API should return a 404 Not Found status code with an appropriate message:
Purpose
To provide admin users with in-depth information about a registered user
Requirements
Expected Outcome
API endpoint allows admin users to retrieve user details by ID with appropriate validation and security measures.
Tasks:
Testing
The text was updated successfully, but these errors were encountered: