Delete a feed note
DELETE /task/v1/feeds/{feed_key}/notes/{notes_id}
Operation id: deleteFeedNote
Description
Deletes the specified note from the feed.
Path parameters are bound as Integer (required = false). Invalid, null, or non-numeric values are caught by the global ApiExceptionHandler (MethodArgumentTypeMismatchException) and return structured 400 responses. Validation of mandatory/existence checks is delegated to validateFeedKeyAndNoteIDForDelete in MyWorkFeedApiUtils, consistent with the PUT pattern.
Alternate malformed routes are also supported:
DELETE /task/v1/feeds/notes/{notes_id}— missingfeed_keyDELETE /task/v1/feeds/{feed_key}/notes/— missingnotes_id
No @SkipAuthorization and no @AuthorizationDefinition on the DELETE route. The auth token is validated on entry (invalid token throws ApiUnauthorizedException E204). Feed existence is validated inside validateFeedKeyAndNoteIDForDelete.
See devdocs/api/nextgen/task-execution/MYWORK_API_CONTRACT_FeedNotes.md for full error matrix and data-store validation notes (RRC_FEED, FEED_NOTES).
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 |
Null / missing / literal null feed_key | 400 | E105 | feed_key is mandatory |
Non-numeric feed_key | 400 | E159 | feed_key must be a valid positive number |
Null / missing / literal null notes_id | 400 | E118 | notes_id is mandatory |
Non-numeric notes_id | 400 | E160 | notes_id must be a valid positive number |
feed_key not found (RRC_FEED) | 404 | E174 | The Feed with FEED_KEY : {feed_key} does not exist |
notes_id not found or already deleted | 404 | E405 | The given notes_id is not found |
| Unexpected server-side error | 500 | E302 | Internal server error |
Tags: MyWorkFeeds
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
feed_key | integer | Yes | Unique numeric feed identifier |
notes_id | integer | Yes | Unique note identifier |
Security
- AuthTokenHeader (apiKey)
- Session authentication token validated server-side against the user session store.
Responses
200 — Success — {status: OK, message: "Feed note deleted successfully."}
Content type: application/json
400 — Invalid path parameter (missing or non-numeric feed_key / notes_id).
Content type: application/json
401 — Invalid or expired X-reflexis-csrf-token-X token (HTTP 401)
Content type: application/json
404 — Feed not found or note not found.
Content type: application/json
500 — Unexpected server-side error
Content type: application/json
Response models
200 — Success — {status: OK, message: "Feed note deleted successfully."}
Content type: application/json
Schema
JSON object (structure varies by endpoint).
{
"type": "object",
"description": "JSON object (structure varies by endpoint)."
}
400 — Invalid path parameter (missing or non-numeric feed_key / notes_id).
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"
}
404 — Feed not found or note not found.
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"
}
}
}
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"
}