Update a Special Notification

The PUT /netevia/support/notifications endpoint allows support administrators to update an existing special notification in the Netevia banking application. By supplying the notification ID along with the updated fields, you can modify a notification's subject, body, audience roles, group category, severity level, or scheduled publication time. This endpoint ensures that all active notifications reflect accurate and current information for the targeted user segments.

Endpoint

PUT /netevia/support/notifications

Authentication

Bearer token required. Obtain via:

POST https://api.banking.netevia.dev/api/auth/v2

Include in header: Authorization: Bearer {token}
Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.

When to use

Use this endpoint when a previously created special notification needs to be corrected or refreshed — for example, to update the body text of a scheduled maintenance alert, change the target audience roles, or reschedule the publication time. This is also appropriate when a notification's severity level needs to be escalated from Info to Warning due to a developing situation. Any support workflow that manages broadcast communications to banking application users should route notification edits through this endpoint.

Request Body

{
  "id": 1042,
  "subject": "Scheduled Maintenance — Updated Window",
  "body": "Our scheduled maintenance window has been updated to Sunday, June 14 from 2:00 AM to 4:00 AM ET. Some services may be temporarily unavailable during this time.",
  "group": "Notifications",
  "level": "Warning",
  "publicationTime": "2026-06-13T06:00:00Z",
  "htmlLink": "https://status.netevia.com/maintenance-june-2026",
  "roles": ["Consumer", "MainUser", "SubUser"],
  "userIds": null
}

Response

200 OK

{
  "id": 1042,
  "createdDate": "2026-06-08T14:23:00Z",
  "updatedDate": "2026-06-09T09:15:42Z",
  "subject": "Scheduled Maintenance — Updated Window",
  "body": "Our scheduled maintenance window has been updated to Sunday, June 14 from 2:00 AM to 4:00 AM ET. Some services may be temporarily unavailable during this time.",
  "group": "Notifications",
  "level": "Warning",
  "publicationTime": "2026-06-13T06:00:00Z",
  "htmlLink": "https://status.netevia.com/maintenance-june-2026",
  "roles": ["Consumer", "MainUser", "SubUser"],
  "userIds": null
}

Error Codes

Common Mistakes

• Omitting the id field — the notification ID is required in the request body and is the only way the system identifies which record to update.
• Supplying an invalid enum value for group or level (e.g., "WARN" instead of "Warning") — use exact casing as documented.
• Setting publicationTime to a past date — notifications scheduled in the past may publish immediately or be rejected depending on platform configuration.
• Exceeding the 1000-character limit on subject or htmlLink — the request will return a 400 error.
• Sending userIds alongside roles without understanding precedence — when userIds is populated, targeting may narrow to those specific users regardless of the roles array.

Related Endpoints

• POST /netevia/support/notifications — Create a new special notification
• GET /netevia/support/notifications — Retrieve a list of existing special notifications
• DELETE /netevia/support/notifications/{id} — Delete a special notification by ID

Example

curl -X PUT https://api.banking.netevia.dev/netevia/support/notifications \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "id": 1042,
    "subject": "Scheduled Maintenance — Updated Window",
    "body": "Our scheduled maintenance window has been updated to Sunday, June 14 from 2:00 AM to 4:00 AM ET. Some services may be temporarily unavailable during this time.",
    "group": "Notifications",
    "level": "Warning",
    "publicationTime": "2026-06-13T06:00:00Z",
    "htmlLink": "https://status.netevia.com/maintenance-june-2026",
    "roles": ["Consumer", "MainUser", "SubUser"]
  }'