Notification Settings Setup
Deprecated: This endpoint is marked deprecated. Use the current notification settings endpoint if available, or contact Netevia support for the recommended replacement.
This endpoint allows partners to configure notification preferences for the authenticated user, including enabling or disabling email and push notifications and registering the devices that should receive push alerts. The response mirrors the saved configuration, including the full list of registered devices and their metadata.
Endpoint
POST /settings/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
Call this endpoint during onboarding or whenever a user changes their notification preferences in your application. Use it to register new mobile devices for push notifications or to toggle email and push channels on or off. Because the endpoint is deprecated, plan to migrate to the current notification settings endpoint when it becomes available.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
emailEnabled | boolean | No | Whether email notifications are enabled for this user |
pushEnabled | boolean | No | Whether push notifications are enabled for this user |
Devices | array of device objects | No | List of devices to register for push notifications |
Devices[].deviceId | string | Yes (per device) | Unique identifier for the device |
Devices[].deviceName | string | Yes (per device) | Human-readable name for the device |
{
"emailEnabled": true,
"pushEnabled": true,
"Devices": [
{
"deviceId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"deviceName": "John's iPhone 15"
},
{
"deviceId": "f9e8d7c6-b5a4-3210-fedc-ba9876543210",
"deviceName": "John's iPad Pro"
}
]
}Response
200 OK
| Field | Type | Description |
|---|---|---|
emailEnabled | boolean | Whether email notifications are enabled |
pushEnabled | boolean | Whether push notifications are enabled |
Devices | array | List of registered devices with status metadata |
Devices[].deviceId | string | Unique identifier of the registered device |
Devices[].deviceName | string | Human-readable name of the device |
Devices[].creationDate | string (date-time) | ISO 8601 timestamp when the device was registered |
Devices[].isDeleted | boolean | Whether the device has been removed from the account |
Devices[].deletionDate | string (date-time) or null | ISO 8601 timestamp of device deletion, if applicable |
Devices[].isActive | boolean | Whether the device is currently active for push delivery |
{
"emailEnabled": true,
"pushEnabled": true,
"Devices": [
{
"deviceId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"deviceName": "John's iPhone 15",
"creationDate": "2026-01-15T10:30:00Z",
"isDeleted": false,
"deletionDate": null,
"isActive": true
},
{
"deviceId": "f9e8d7c6-b5a4-3210-fedc-ba9876543210",
"deviceName": "John's iPad Pro",
"creationDate": "2026-03-22T08:15:00Z",
"isDeleted": false,
"deletionDate": null,
"isActive": true
}
]
}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields or validation error (e.g., deviceId or deviceName absent in a device entry) |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions |
| 404 | Resource not found |
| 500 | Internal server error |
Common Mistakes
- Omitting
deviceIdordeviceNameinside aDevicesentry — both fields are required when providing any device object, and requests will fail validation if either is missing or empty. - Sending a non-boolean value (e.g., the string
"true") foremailEnabledorpushEnabled— the API strictly expects JSON booleantrueorfalse. - Relying on this endpoint for new integrations — this endpoint is deprecated; verify with Netevia support whether a newer notification settings endpoint should be used instead.
Related Endpoints
GET /settings/notifications— Retrieve the current notification settings for the authenticated userPOST /api/auth/v2— Obtain a Bearer token for authenticationPOST /api/auth/refresh— Refresh an expiring Bearer token
Example
curl -X POST https://api.banking.netevia.dev/settings/notifications \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"emailEnabled": true,
"pushEnabled": true,
"Devices": [
{
"deviceId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"deviceName": "John'\''s iPhone 15"
}
]
}'