User Management Service
Resource Management
The Resource Management service provides functionality to manage resources in the system, including creating, retrieving, updating, and deleting resources.
Resource Operations
Get Resource by ID GET /api/v1/resource/{resourceId}
| Resource URL | /api/v1/resource/{resourceId} |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Parameters
| Parameter | Description | Required |
|---|---|---|
| resourceId | ID of resource to retrieve | Yes |
Example Request
Example Response
Update Resource PUT /api/v1/resource/{resourceId}
| Resource URL | /api/v1/resource/{resourceId} |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Parameters
| Parameter | Description | Required |
|---|---|---|
| resourceId | ID of resource to update | Yes |
Request Body
Example Request
Example Response
Delete Resource DELETE /api/v1/resource/{resourceId}
| Resource URL | /api/v1/resource/{resourceId} |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Parameters
| Parameter | Description | Required |
|---|---|---|
| resourceId | ID of resource to delete | Yes |
Example Request
Example Response
Get All Resources GET /api/v1/resource
| Resource URL | /api/v1/resource |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Example Request
Example Response
Create Resource POST /api/v1/resource
| Resource URL | /api/v1/resource |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Request Body
Example Request
Example Response
HTTP Response Codes
| HTTP Code | Message |
|---|---|
| 200 | Success |
| 204 | No Content |
| 400 | Bad Request |
| 401 | Unauthorized |
| 403 | Invalid Input |
| 404 | Invalid or not found type |
All endpoints require proper authentication through Bearer token in the Authorization header. The token should be included in all API requests in the headers: