Get merged MyWork configuration for requested types

GET /task/v1/config/list

Operation id: getMyWorkConfigList

Description

Returns one or more MyWork configuration domains merged into a flat config_list object. Fields from all requested types appear at the same level under config_list. When multiple types are requested via comma-separation, fields are merged in enum declaration order: calendar → feed → attachment → smart_search → refresh → filter → feed_component.

Authentication: domainId and langCode are always resolved from the validated session.

Valid Config Types

Response Fields Reference

calendar fields

feed fields

attachment fields

refresh fields

filter fields

feed_component fields

Error Scenarios

Error Codes Reference

Tags: MyWorkConfig

Parameters

Query parameters

Security

• AuthTokenHeader (apiKey)
  • Session authentication token validated server-side against the user session store.

Responses

200 — Success — {status: OK, config_list: {...}}. All requested type fields

appear flat under config_list. When config_type=ALL or omitted, all 7 type field sets are merged together.

Content type: application/json

400 — E203 — Invalid config type. Returned when config_type contains an unrecognised token.

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, config_list: {...}}. All requested type fields

appear flat under config_list. When config_type=ALL or omitted, all 7 type field sets are merged together.

Content type: application/json

Schema

JSON object (structure varies by endpoint).

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

Example:

{
  "status": "OK",
  "config_list": {
    "default_calendar_view": "",
    "gantt_date_span": "10",
    "calendar_setup": [
      {
        "key": "CALENDAR",
        "value": "My Projects",
        "on_click": "FV",
        "view": "A",
        "default": {
          "layout": "M",
          "view": "P"
        }
      }
    ],
    "feed_status_data": {
      "p": {
        "display_text": "In Progress"
      },
      "r": {
        "display_text": "Reviewed"
      },
      "c": {
        "display_text": "Completed"
      },
      "e": {
        "display_text": "Expired"
      },
      "f": {
        "display_text": "Force Closed"
      },
      "n": {
        "display_text": "New"
      },
      "o": {
        "display_text": "Overdue"
      }
    },
    "feed_date_span": "15",
    "no_records": "20",
    "overdue_date_span": 6,
    "allow_bulk_action": "Y",
    "allowed_attachments": "png,gif,jpg,jpeg,pdf,docx,pptx,xlsx,csv,txt,zip,mp4",
    "max_upload_size": 1048576,
    "comment_max_attach_count": 5,
    "button_max_attach_count": 3,
    "feed_refresh_rate": 15000,
    "msg_refresh_rate": 60000,
    "filter_date_range": 31,
    "max_feed_notes_characters": "8000",
    "max_filter_name_characters": "255",
    "list_task_limit": 5,
    "feed_config_details": []
  }
}

400 — E203 — Invalid config type. Returned when config_type contains an unrecognised 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": "E203",
  "response": "Invalid config type. Valid values: calendar, feed, attachment, smart_search, refresh, filter, feed_component, all, or comma-separated combination"
}

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