User Management Service
Resource Attribute Management
The Resource Attribute Management service provides functionality to manage attributes associated with resources, including creation, retrieval, updating, and deletion of resource attributes.
Resource Attribute Operations
Get Resource Attribute by IDs GET /api/v1/resource-attribute/
| Resource URL | /api/v1/resource-attribute/ |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| resourceId | integer | Yes | ID of the resource |
| attributeId | integer | Yes | ID of the attribute |
Example Request
Example Response
Update Resource Attribute PUT /api/v1/resource-attribute/
| Resource URL | /api/v1/resource-attribute/ |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Request Body
Example Request
Example Response
Delete Resource Attribute DELETE /api/v1/resource-attribute/
| Resource URL | /api/v1/resource-attribute/ |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| resourceId | integer | Yes | ID of the resource |
| attributeId | integer | Yes | ID of the attribute to delete |
Example Request
Example Response
Get All Resource Attributes GET /api/v1/resource-attribute
| Resource URL | /api/v1/resource-attribute |
|---|---|
| Response Format | JSON |
| Requires Authentication | Yes |
| Rate Limited | Yes |
| HTTPS | Yes |
Example Request
Example Response
Create Resource Attribute POST /api/v1/resource-attribute
| Resource URL | /api/v1/resource-attribute |
|---|---|
| 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: