POST Notification Settings Types

POST Notification Settings Types

This endpoint allows partners to configure notification delivery preferences for a user profile. You can specify, for each notification type, whether email and/or push notifications should be enabled. The request accepts an array of notification setting objects, enabling bulk configuration in a single call.

Endpoint

POST /settings/NotificationSettingsTypes

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 onboarding a new user and establishing their notification preferences, or when a user updates their communication settings through your application. This is the appropriate endpoint for enabling or disabling email and push notifications on a per-notification-type basis for a given user profile.

Request Body

The request body is a JSON array of notification settings type objects.

notificationType Enum Values

[
  {
    "userProfileId": 10042,
    "emailEnabled": true,
    "pushEnabled": true,
    "notificationType": 1
  },
  {
    "userProfileId": 10042,
    "emailEnabled": false,
    "pushEnabled": true,
    "notificationType": 2
  },
  {
    "userProfileId": 10042,
    "emailEnabled": true,
    "pushEnabled": false,
    "notificationType": 3
  }
]

Response

200 OK

A successful response indicates the notification settings were saved. The response body may be empty or contain a success confirmation.

{}

Error Codes

Common Mistakes

• Sending a single object instead of an array — the request body must always be a JSON array, even when configuring settings for only one notification type.
• Using an invalid notificationType value — only 0, 1, 2, and 3 are accepted; any other integer will result in a 400 error.
• Omitting userProfileId — every object in the array must include the user profile ID to associate the settings correctly.
• Sending duplicate notificationType entries for the same userProfileId in a single request — this may cause unpredictable results; each notification type should appear at most once per call.

Related Endpoints

• GET /settings/NotificationSettingsTypes — Retrieve existing notification settings types for a user profile
• POST /api/auth/v2 — Obtain a Bearer token for authentication
• POST /api/auth/refresh — Refresh an expiring Bearer token

Example

curl -X POST https://api.banking.netevia.dev/settings/NotificationSettingsTypes \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '[
    {
      "userProfileId": 10042,
      "emailEnabled": true,
      "pushEnabled": true,
      "notificationType": 1
    },
    {
      "userProfileId": 10042,
      "emailEnabled": false,
      "pushEnabled": true,
      "notificationType": 2
    }
  ]'