Unified feed details — one call, multiple section projections

GET /task/v1/feeds/{feed_key}/details

Operation id: getFeedDetails

Description

Returns complete feed detail data for a single feed shaped by the projection query parameter. The client requests only the sections it needs, avoiding multiple round-trips. Each section is fetched independently — a failure in one section does not abort others. Unrecognised projection names are silently ignored. Omitting projection (or leaving it empty) returns only the basic section.

Response wrapper: All sections appear under feed_details. Feed not found → entire response returns NO_DATA_FOUND (not per-section).

Path Parameters

Projection → Response Key Mapping

Key presence rules:

Exception: feed_notes is absent entirely (not []) when there are no notes.

feed_basic — Supplementary Fields

Standard feed record fields plus:

store_status[*] fields: cluster_id, cluster_child_id, message_type, stores[]

stores[*] fields: store_id, status, dept_id, profile_id, assign_user, last_update_time

feed_history — Field Reference

feed_actions — Field Reference

Error Scenarios

Error Codes Reference

Tags: MyWorkFeeds

Parameters

Path parameters

Query parameters

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 — {status: OK, feed_details: {feed_basic?, feed_contents?, feed_history?, ...}}

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 — {status: OK, feed_details: {feed_basic?, feed_contents?, feed_history?, ...}}

Content type: application/json

Schema

JSON object (structure varies by endpoint).

{
  "type": "object",
  "description": "JSON object (structure varies by endpoint)."
}

Example:

{
  "status": "OK",
  "feed_details": {
    "feed_basic": {
      "feed_key": 45739193,
      "feed_title": "Weekly Store Check",
      "status": "O",
      "priority": 1
    }
  }
}

400 — E105 — invalid or missing feed_key

Content type: application/json

Schema

{
  "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

{
  "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

{
  "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"
}