Skip to main content
POST
Update Notification Config
Use this API to update the in-app notification service configuration for a workspace. At least one of useNotificationService or notificationServiceConfig must be provided. The config is deep-merged with the existing value, so omitted sub-fields are preserved.
This endpoint uses API-key-level auth: pass x-velt-api-key and x-velt-auth-token as headers. You can obtain these from the Get Auth Tokens endpoint.
The numeric delay/batching fields must be integers within these ranges, otherwise the request is rejected with INVALID_ARGUMENT:
  • delayConfig.delaySeconds: 1015552000 (10 seconds to 6 months)
  • batchConfig.document.batchWindowSeconds / batchConfig.user.batchWindowSeconds: 10604800 (10 seconds to 1 week)
  • batchConfig.document.maxActivities / batchConfig.user.maxActivities: 250
Defaults on first enable. If you enable the service (useNotificationService: true) and the stored config has no triggers yet (defaults are seeded even if delayConfig / batchConfig already exist), a default set of triggers is seeded automatically: the standard comment triggers and all huddle triggers are turned on. Delay and batching stay off — no delayConfig or batchConfig is written by the seeding. Existing non-trigger fields are preserved, and any notificationServiceConfig values you send in the same request are merged on top of these defaults.
The response data echoes the latest post-write state as { useNotificationService, notificationServiceConfig } — the same shape returned by Get Notification Config. Fields not part of your request fall back to the existing stored values.

Endpoint

POST https://api.velt.dev/v2/workspace/notificationconfig/update

Headers

x-velt-api-key
string
required
Your API key.
x-velt-auth-token
string
required

Body

Params

data
object
required

Example Request

Example Response

Success Response

Failure Response