Feed audit thread / history (most recent first)
GET /task/v1/feeds/{feed_key}/history
Operation id: getFeedHistory
Description
Returns feed audit history ordered by action_time descending (most recent first). If transaction_key is not provided, it is extracted from the feed record automatically (an extra feed lookup is required when omitted). Empty history → NO_DATA_FOUND error (not an empty array).
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
feed_key | Integer | Yes | Unique feed identifier (→ E105 if ≤ 0 or missing) |
Response Fields — feed_threads[*]
| Field | Type | Description |
|---|---|---|
feed_key | Integer | Feed identifier |
action_seq | String | Action label (e.g. "Reviewed", "Event Viewed") |
user_id | String | ID of the user who performed the action |
user_name | String | Display name |
user_level | Integer | Permission level at time of action |
creation_time | String | Formatted timestamp |
result | String | Outcome description |
action_id | String | Action type code (e.g. VIEW_EVENT); may be absent |
comments | String | Comments attached (empty string if none) |
attachments | String | Comma-separated attachment IDs (empty string if none) |
attach_names | String | Attachment display names (empty string if none) |
comment_flag | String | "1" if comments exist, "0" otherwise |
form_flag | String | "1" if form data attached |
attach_flag | String | "1" if attachments present |
request_params | String | JSON string of request parameters |
context_params | String | JSON string of context parameters |
param_params | String | Additional parameter data |
form_params | String | Form-related parameters |
Error Scenarios
| Scenario | HTTP | Error Code | Message |
|---|---|---|---|
Missing / invalid X-reflexis-csrf-token-X | 401 | E202 | User session is invalid |
Missing or invalid feed_key (≤ 0) | 400 | E105 | Please provide valid feedKey. |
| No thread data found | 200 | NO_DATA_FOUND | No data found |
| DB connection error (AuditActionDao null) | 500 | E500 | AuditActionDao is not initialized |
| Unexpected server-side error | 500 | E500 | Unexpected server error. |
Error Codes Reference
| Code | Description |
|---|---|
E105 | Invalid or missing feedKey parameter |
E202 | User session is invalid |
E500 | Unexpected server error |
NO_DATA_FOUND | No thread data available |
Tags: MyWorkFeeds
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
feed_key | integer | Yes | Unique numeric feed identifier |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
transaction_key | string | No | Transaction key for filtering specific thread history. Auto-extracted from feed if omitted. |
Security
- ApiKeyHeader (apiKey)
- APIGEE API key header validated by VerifyAPIKey policy.
- AuthTokenHeader (apiKey)
- Session authentication token validated server-side against the user session store.
Responses
200 — Success — feed_threads[] or NO_DATA_FOUND
Content type: application/json
400 — E105 — invalid or missing feed_key
Content type: application/json
401 — Missing or invalid X-reflexis-csrf-token-X session token
Content type: application/json
500 — Unexpected server-side error
Content type: application/json
Response models
200 — Success — feed_threads[] or NO_DATA_FOUND
Content type: application/json
Schema
JSON object (structure varies by endpoint).
{
"type": "object",
"description": "JSON object (structure varies by endpoint)."
}
Example:
{
"feed_threads": [
{
"feed_key": 42893020,
"action_seq": "Event Viewed",
"user_id": "SYSADMIN",
"user_name": "System Administrator",
"user_level": 0,
"creation_time": "10-03-2026 04:31 AM",
"result": "Event viewed by the user",
"action_id": "VIEW_EVENT",
"comments": "",
"attachments": "",
"comment_flag": "",
"form_flag": "",
"attach_flag": ""
}
]
}
400 — E105 — invalid or missing feed_key
Content type: application/json
Schema
| Property | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Always "ER" for error responses |
errorCode | string | Yes | Application-level error code (e.g. E202, E105, E404) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E202",
"response": "User session is invalid"
},
"required": [
"status",
"errorCode",
"response"
],
"properties": {
"status": {
"type": "string",
"description": "Always \"ER\" for error responses",
"enum": [
"ER"
]
},
"errorCode": {
"type": "string",
"description": "Application-level error code (e.g. E202, E105, E404)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
401 — Missing or invalid X-reflexis-csrf-token-X session token
Content type: application/json
Schema
| Property | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Always "ER" for error responses |
errorCode | string | Yes | Application-level error code (e.g. E202, E105, E404) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E202",
"response": "User session is invalid"
},
"required": [
"status",
"errorCode",
"response"
],
"properties": {
"status": {
"type": "string",
"description": "Always \"ER\" for error responses",
"enum": [
"ER"
]
},
"errorCode": {
"type": "string",
"description": "Application-level error code (e.g. E202, E105, E404)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"errorCode": "E202",
"response": "User session is invalid"
}
500 — Unexpected server-side error
Content type: application/json
Schema
| Property | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Always "ER" for error responses |
errorCode | string | Yes | Application-level error code (e.g. E202, E105, E404) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E202",
"response": "User session is invalid"
},
"required": [
"status",
"errorCode",
"response"
],
"properties": {
"status": {
"type": "string",
"description": "Always \"ER\" for error responses",
"enum": [
"ER"
]
},
"errorCode": {
"type": "string",
"description": "Application-level error code (e.g. E202, E105, E404)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"errorCode": "E302",
"response": "Internal server error"
}