For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
LoginGet Started
DocsAPI ReferenceChangelog
DocsAPI ReferenceChangelog
    • Home
  • Getting Started
  • Infrastructure
    • GPU VMs
    • Cloud VMs
    • Object Storage
      • Core Concepts
      • Upload Your First Object
      • Buckets
        • Bucket Policies
        • Lifecycle Management
        • CORS
        • Custom Domains
        • Event Notifications
      • Objects
      • Mount a Bucket as a Filesystem
      • Metrics
      • API Tokens
      • Static Site Hosting
      • CDN integration
      • Pricing
      • Limits
    • Block Storage
  • Network & Security
    • Load Balancer
    • DNS
    • CDN
    • Firewalls
    • SSL Certificates
  • Tools
    • Backups
    • Snapshots
    • ISOs
    • SSH Keys
    • API Tokens
    • Secret Manager
    • Container Registry
  • Platform Fundamentals
    • Projects and tenancy model
    • IAM
    • Networking overview
    • Billing and usage
    • Limits and quotas
    • SLA and reliability
  • Tutorials
    • Deploy a web app
    • Host a static website with object storage
    • Run an AI model on a GPU VM
    • Set up a load-balanced architecture
    • Backup and disaster recovery
    • Multi-region deployment
  • Migration Guides
    • Migrate from AWS
    • Migrate from GCP
    • Migrate from Vultr and Linode
    • Move S3 workloads to IBEE Object Storage
    • VM image migration
  • Reference
    • Pricing
    • Regions
    • Limits
    • Error codes
    • Service level agreement
  • Support
    • Contact Support
    • Create a request
    • Troubleshooting guides
    • Visit ibee.ai
LogoLogo
LoginGet Started
On this page
  • Before you begin
  • Add a webhook notification
  • Troubleshooting
  • Related
InfrastructureObject StorageBuckets

Event Notifications

Was this page helpful?
Edit this page
Previous

Objects

Next
Built with

Event notifications send a POST request to your webhook URL whenever objects are created or deleted in a bucket. Use prefix and suffix filters to target specific paths or file types.

Before you begin

  • An active IBEE Cloud project with a verified account
  • A bucket (Create a bucket)
  • A publicly accessible HTTPS endpoint to receive webhook POST requests

Add a webhook notification

1

Open bucket settings

Open your bucket in the portal, click the Settings tab, then click Event Notifications.

2

Add a notification

Click + Add Notification. The Add Notification modal appears with the subtitle “Configure webhook endpoint and event types.”

3

Configure the webhook

Webhook URL (required)

Helper: “The URL that will receive POST requests when events occur.” Placeholder: https://your-app.com/.

https://your-app.com/webhook

Event Types (required)

Helper: “Select which events should trigger notifications:“

EventDescription
Creation of a new objectTriggered when objects are uploaded
Deletion of an objectTriggered when objects are deleted

At least one event type must be selected.

4

Set filters (optional)

Expand Advanced Options — “Filter notifications to specific objects based on prefix or suffix:“

FilterPlaceholderHelper
Prefixe.g., uploads/Only trigger for objects with this path prefix
Suffixe.g., .jpgOnly trigger for objects with this file extension

Leave both empty to receive notifications for all objects in the bucket.

5

Save

Click Save Notification. The webhook appears in the Webhook Notifications list.

Troubleshooting

Webhook not receiving events Ensure the webhook URL is publicly accessible over HTTPS. IBEE sends POST requests — verify your endpoint is not blocking them.

Too many notifications Use the Prefix or Suffix filters under Advanced Options to limit notifications to specific paths or file types.

Notifications for wrong event type Check that the correct event types (Creation and/or Deletion) are selected for the notification.

Related

  • Buckets
  • Objects
  • Lifecycle
  • Bucket policies