# Event Notifications

Filebase Event Notifications are triggered by changes in data within your storage buckets, allowing you to automate workflows and tasks against IPFS content in real-time.

You can use Event Notifications in many types of workflows. Here are some examples:

* Transcoding video files after upload
* Recording object CIDs to a database after a pre-signed URL object upload
* Triggering a file download on a server to fetch the latest updates

### Supported Event Types

The following event types are supported:

* s3:ObjectCreated:\*
* s3:ObjectCreated:Copy
* s3:ObjectCreated:MultipartUpload
* s3:ObjectCreated:Pin
* s3:ObjectCreated:Put
* s3:ObjectCreated:WebUpload
* s3:ObjectRemoved:\*
* s3:ObjectRemoved:Delete

### Event Payloads

Events are JSON-based and are sent using an HTTP POST request. 

The endpoint URL must be an application or server that can accept HTTP POST requests. A 200 OK response code must be returned. If a non-200 code is returned, Filebase will consider the event delivery a failure and retry sending.

This is what an example event looks like:

```json
{
  "events": [
    {
      "accountId": "1f657f8d-50ab-5e8c-808c-f7c0c4f8be1a",
      "bucketId": "b5a7ff07-2e07-5aee-b859-eaa136c5d723",
      "bucketName": "my-bucket",
      "eventId": "3900a5ad-93e1-4264-864a-5e65d74e7a4e",
      "eventTimestamp": 1727805541,
      "eventType": "s3:ObjectCreated:WebUpload",
      "eventVersion": 1,
      "matchedRuleName": "EasyEvents-All",
      "objectName": "my-file",
      "objectSize": 119762,
      "objectCid": "QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR"
    }
  ]
}
```

### Configuring Notifications

Event Notifications are configured and set at the bucket level. This means each bucket can have it's own unique event configuration. Event configurations can be created, modified, or removed by using the Filebase Dashboard or API.

**Dashboard**

1. Login to the **Filebase Dashboard** and navigate to the **Buckets** page.
2. Open the **Options** menu for a bucket and select **Configure Events**.
3. Choose the desired **Events Configuration** and set an **Endpoint URL**.

<figure><img src="https://3861818989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lyjw7dWpiQtUFDa1pO0%2Fuploads%2FxByM072AvB4lSpD20Kaq%2Fimage.png?alt=media&#x26;token=d430cefb-4d5a-4295-94de-344ff1aee849" alt="" width="425"><figcaption><p>Configure Events Options Menu</p></figcaption></figure>

<figure><img src="https://3861818989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lyjw7dWpiQtUFDa1pO0%2Fuploads%2FrpvyQsNYDZPuAMtvZb7x%2Fimage.png?alt=media&#x26;token=75685eda-ec5a-4ae6-8927-d1d324ed48ff" alt="" width="563"><figcaption><p>Configure Events Dialog</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.filebase.com/ipfs-pinning/event-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.