Get notification settings

Get Notification Settings

Deprecated: This endpoint is marked as deprecated. Use the current notification settings endpoint for new integrations.

This endpoint retrieves the authenticated user's notification preferences, including whether email and push notifications are enabled. It also returns a list of connected devices that are registered for push notifications, along with each device's status and registration metadata.

Endpoint

GET /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

Use this endpoint to display a user's current notification preferences within a settings or profile screen. It is useful for checking whether a user has email or push notifications active before prompting them to update their preferences. The device list can help identify which mobile or web devices are registered to receive push alerts.

Response

200 OK

FieldTypeDescription
emailEnabledbooleanIndicates whether email notifications are enabled for the user
pushEnabledbooleanIndicates whether push notifications are enabled for the user
Devicesarray|nullArray of connected device objects registered for push notifications
Devices[].deviceIdstring|nullUnique identifier for the device
Devices[].deviceNamestring|nullHuman-readable name of the device
Devices[].creationDatestring (date-time)Date and time the device was registered
Devices[].isDeletedbooleanWhether the device has been removed/deregistered
Devices[].deletionDatestring (date-time)|nullDate the device was deleted; presence indicates device is considered deleted (extended device info only)
Devices[].isActivebooleanWhether the device is currently active (extended device info only)
{
  "emailEnabled": true,
  "pushEnabled": true,
  "Devices": [
    {
      "deviceId": "d1a2b3c4-5678-90ab-cdef-1234567890ab",
      "deviceName": "iPhone 14 Pro",
      "creationDate": "2025-03-15T10:22:00Z",
      "isDeleted": false,
      "deletionDate": null,
      "isActive": true
    },
    {
      "deviceId": "e9f8a7b6-4321-dcba-fedc-0987654321ef",
      "deviceName": "Chrome on Windows",
      "creationDate": "2024-11-01T08:00:00Z",
      "isDeleted": true,
      "deletionDate": "2025-01-20T14:35:00Z",
      "isActive": false
    }
  ]
}

Error Codes

CodeWhen it happens
401Token missing, expired, or invalid
403Insufficient permissions
500Internal server error

Common Mistakes

  • Not refreshing the Bearer token before calling this endpoint; tokens expire after 10 minutes and will result in a 401 response.
  • Treating the Devices array as always populated; it is nullable and may be null if no devices have been registered.
  • Relying on this endpoint for new integrations; it is deprecated and may be removed in a future API version.

Related Endpoints

  • POST /settings/notifications — Create or update notification settings for the authenticated user
  • PUT /settings/notifications — Update existing notification settings
  • GET /settings/notifications/devices — Retrieve registered device information for push notifications

Example

curl -X GET https://api.banking.netevia.dev/settings/notifications \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Response

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json