Update category/channel preferences optimistically
PATCH/api/v1/notification-preferences
Requires notifications.manage, an exact same-origin proof for cookie requests, and the current strong ETag. One to ten unique category and channel updates apply atomically; omitted pairs remain unchanged and Web Push cannot be enabled.
Request
Responses
- 200
- 401
- 403
- 412
- 421
- 428
Updated preference snapshot
Response Headers
Strong preference-matrix revision after the update
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The browser mutation did not originate from this application, or the authenticated member lacks the required permission
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The strong revision precondition is stale
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
Exactly one valid strong If-Match value is required
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.