Skip to content
EyesOnItDocumentation6.1

Replace Notification Profile

PUT /api/v1/notification-profiles/{profileId}

Access

Section titled “Access”

Authentication options declared in the contract include user cookie session or bearer service token.

The shared authentication policy requires organizationNotifications:manage. Resource access also depends on the caller’s role, organization, camera grants, and the operation’s validation.

User-session writes require recent authentication.

The handler requires an EyesOnIt system administrator. Use an administrator user session for this operation.

Authentication and permissions explains tokens, cookies, CSRF, and workspace context.

Parameters

Section titled “Parameters”
Name Location Required Type Description and constraints
profileId path Yes string (uuid)
If-Match header Yes integer minimum 1
X-EyesOnIt-Session-Id header No string (uuid) The sessionId the caller expects. Required when switching workspaces and for cookie requests after workspace rotation. A mismatched value returns 409 with X-EyesOnIt-Workspace-Changed: 1. Bootstrap with getCurrentPrincipal; never replay a mutation automatically after changing context. Bearer clients do not use this header.
X-CSRF-Token header No string Required for unsafe requests authenticated by CookieSession; ignored for bearer clients. minimum length 32. maximum length 256

Request body

Section titled “Request body”

Required.

application/json — NotificationProfileBody.

Field Type Required Description and constraints
name string Yes minimum length 1. maximum length 128
enabled boolean No default true
configuration WebhookNotificationProfileConfig or GenetecNotificationProfileConfig or SmtpNotificationProfileConfig or EmailNotificationProfileConfig or TelegramNotificationProfileConfig or SmsNotificationProfileConfig or SlackNotificationProfileConfig or TeamsNotificationProfileConfig Yes
secretRef string or null No
allowArtifacts boolean No default false

cURL request template

Section titled “cURL request template”

Set the connection variables described in Get started. Replace each additional EOI_… variable with the parameter value for this request. Prepare the body file using the request schema above. This template sends the request when run.

Terminal window
curl --fail-with-body --silent --show-error \
  --request PUT \
  --cookie "${EOI_COOKIE_JAR}" \
  --header "X-EyesOnIt-Session-Id: ${EOI_SESSION_ID}" \
  --header "X-CSRF-Token: ${EOI_CSRF_TOKEN}" \
  --header "If-Match: ${EOI_IF_MATCH}" \
  --header "Content-Type: application/json" \
  --data-binary @request.json \
  "${EOI_API_BASE_URL}/notification-profiles/${EOI_PROFILEID}"

Contract responses

Section titled “Contract responses”

The table records responses declared by the OpenAPI contract. See Errors and status codes for the runtime error envelope and shared failures.

Status Description Media type Body
200 Successful Response application/json NotificationProfileResponse
422 Validation Error application/json HTTPValidationError

Operation identifier replaceNotificationProfile. Browse Notification profiles.

Image preview