ObjectNotifications

Configuration for object event notifications via webhook. Receive HTTP callbacks when objects are created, updated, or deleted in your bucket.

Update behavior (partial updates supported):

• Omit field entirely: Keeps existing settings unchanged
• Include only enabled: Toggles notifications on/off while preserving all other config
• Include any field: Updates specified fields, preserves others (auth not re-required)
• Remove completely: Send {"enabled": false} with no other fields

Common operations:

// Enable notifications (preserves webhook, filter, auth)

{"enabled": true}

// Disable temporarily (keeps all config for later)

{"enabled": false, "webhook": "https://..."}

// Update webhook only (preserves auth, filter)

{"webhook": "https://new-endpoint.com"}

// Change auth type (replaces entire auth object)

{"auth": {"token": "new-token"}}

// Remove all notifications

{"enabled": false}

Note: Auth credentials are masked in responses. You don't need to re-send them when updating other fields.

enabled booleanrequired

Enable or disable notifications (webhook required when true)

webhook uri

HTTPS endpoint to receive notification events

Example: https://webhook.example.com/tigris-events

filter string

SQL WHERE clause to filter which objects trigger notifications (e.g., size comparisons)

Example: size > 1000000

authobject

Authentication credentials for webhook endpoint

basic_user string

Basic auth username

basic_pass password

Basic auth password

token password

Bearer token for authorization

ObjectNotifications

{

"enabled": true,

"webhook": "https://webhook.example.com/tigris-events",

"filter": "size > 1000000",

"auth": {

"basic_user": "string",

"basic_pass": "string",

"token": "string"

}

}