Detail Notification by ID
This API returns detailed information about a specific notification identified by ID, including its read status.
Endpoint Details
| URL | /v1/notifications/id |
| Method | GET |
| Authorization | Bearer Token |
Request Headers
| Header | Type | Description |
|---|---|---|
| Content-Type | String | Must be application/json |
Request Path
To retrieve the details of a specific notification, use the following request format:
/v1/notifications/363bc3b6-74eb-40df-8c1c-04ec61e1dc7a
Path Parameter
| Parameter | Type | Description |
|---|---|---|
| id | UUID | Unique identifier of the notification |
Response
Here is an example of a response when viewing data details:
Response
{
"id": "363bc3b6-74eb-40df-8c1c-04ec61e1dc7a",
"title": "Key rotation scheduled",
"activity": "Auto-rotation set for ring crypto/72859af3-e342-4440-b8d0-c98acd9ac3e1 every 1h0m0s",
"description": "Key rotation schedule created",
"category": 2,
"category_id": "b2c3d4e5-f6a7-4b5c-9d0e-1f2a3b4c5d6e",
"severity": 3,
"type": 2,
"channels": [
2,
1
],
"config_notification_id": "9a91d205-ca27-4b0f-b767-7cc3e411137c",
"read_at": "2026-07-21T15:41:07+07:00",
"read_by": "0a937c60-0ed4-4d06-870a-2e284b54287d",
"read_by_name": "Admin Aplikasi",
"created_at": "2026-07-21T15:32:49+07:00"
}
Field Descriptions
| Field | Type | Description |
|---|---|---|
| id | UUID | Unique identifier of the notification |
| title | String | Title of the notification |
| activity | String | Detailed description of the activity that triggered the notification |
| description | String | Short description of the notification |
| category | Integer | Category code of the notification |
| category_id | UUID | Identifier of the notification category |
| severity | Integer | Severity code of the notification |
| type | Integer | Type code of the notification |
| channels | Array | List of channel codes the notification was delivered through |
| config_notification_id | UUID | Identifier of the notification configuration that produced it |
| read_at | String | Timestamp when the notification was read, in RFC 3339 format |
| read_by | UUID | Identifier of the user who read the notification |
| read_by_name | String | Display name of the user who read the notification |
| created_at | String | Creation timestamp in RFC 3339 date-time format |
info
- A valid Bearer Token is required to access this endpoint.
- The
idpath parameter must reference an existing notification. - The
read_at,read_by, andread_by_namefields are only present once the notification has been read. - The
categoryfield uses the following codes:1= Security & Access Control2= Key Lifecycle3= Backup & Recovery4= System Health & Performance5= Compliance & Audit Trail6= User & Role Management7= Network & Connectivity8= Integration & API Activity9= Operational & Maintenance
- The
severityfield uses the following codes:1= Critical2= High3= Medium4= Low
- The
channelsarray uses the following codes:1= Email2= Dashboard
- Timestamps are returned in RFC 3339 date-time format.