Feed message info (RRC_FEED_MSG snapshot)
GET /task/v1/feeds/{feed_key}/feed-msg-info
Operation id: getFeedMsgInfo
Description
Returns the feed message details document from MongoDB RRC_FEED_MSG for the given feed_key. Next-gen equivalent of legacy POST /service/feed/retrieveFeedMsgDetails.
The response is a passthrough of the stored document under feed_msg_info (keys in snake_case). Field presence varies by msg_type — only five core fields are written on every normal feed creation: feed_key, domain_id, msg_type, txn_dtm, transaction_key.
URL fields: When attr_why_url, attr_how_url, or attr_info_url exist:
is_redirect=false(default): externalhttpURLs are masked asRD|URLis_redirect=true: full URLs with instance-variable substitution
See devdocs/api/nextgen/task-execution/MYWORK_API_CONTRACT_FeedMsgInfo.md for field semantics and client guidance.
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
feed_key | Integer | Yes | Unique numeric feed identifier (→ E105 if ≤ 0) |
Query Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
is_redirect | Boolean | No | false | URL masking vs full redirect URL resolution |
Error Scenarios
| Scenario | HTTP | Error Code | Message |
|---|---|---|---|
Missing X-reflexis-csrf-token-X header | 400 | E112 | X-reflexis-csrf-token-X header is mandatory |
| Invalid or expired token | 401 | E204 | Invalid or expired token |
Missing or invalid feed_key (non-numeric or ≤ 0) | 400 | E105 | feed_key is mandatory |
| No RRC_FEED_MSG row for feed | 200 | E404 | No data found |
| Unexpected server-side error | 500 | E500 | Unexpected server error. |
Tags: MyWorkFeeds
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
feed_key | integer | Yes | Unique numeric feed identifier |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
is_redirect | boolean | No | When false, external http URLs in attr_why_url / attr_how_url / attr_info_url are returned as RD|URL. When true, URLs are fully resolved with session variable substitution. |
Security
- AuthTokenHeader (apiKey)
- Session authentication token validated server-side against the user session store.
Responses
200 — Success — {status: OK, feed_msg_info: {...}}
Content type: application/json
400 — E105 — invalid or missing feed_key
Content type: application/json
401 — Invalid or expired X-reflexis-csrf-token-X token (HTTP 401)
Content type: application/json
500 — Unexpected server-side error
Content type: application/json
Response models
200 — Success — {status: OK, feed_msg_info: {...}}
Content type: application/json
Schema
JSON object (structure varies by endpoint).
{
"type": "object",
"description": "JSON object (structure varies by endpoint)."
}
Example:
{
"status": "OK",
"feed_msg_info": {
"feed_key": "<FEED_KEY>",
"domain_id": "<DOMAIN_ID>",
"msg_type": "<MSG_TYPE>",
"txn_dtm": "<TXN_DTM>",
"transaction_key": "<TRANSACTION_KEY>",
"attr_feed_title": "<FEED_TITLE>",
"attr_feed_description": "<FEED_DESCRIPTION>",
"attr_unit_id": "<UNIT_ID>",
"attr_profile_id": "<PROFILE_ID>",
"attr_start_date_time": "<START_DATE_TIME>",
"attr_end_date_time": "<END_DATE_TIME>",
"attr_why_url": "RD|URL"
}
}
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. E204, E112, E302) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
},
"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. E204, E112, E302)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
401 — Invalid or expired X-reflexis-csrf-token-X token (HTTP 401)
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. E204, E112, E302) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
},
"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. E204, E112, E302)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
}
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. E204, E112, E302) |
response | string | Yes | Human-readable error message |
{
"type": "object",
"example": {
"status": "ER",
"errorCode": "E204",
"response": "Invalid or expired token"
},
"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. E204, E112, E302)"
},
"response": {
"type": "string",
"description": "Human-readable error message"
}
}
}
Example:
{
"status": "ER",
"errorCode": "E302",
"response": "Internal server error"
}