---
title: "What system events can I subscribe to for notifications?"
slug: "what-system-events-can-i-subscribe-to"
tags: ["notification service ", "subscription ", "system event"]
updated: 2025-04-16T13:24:12Z
published: 2025-04-16T13:24:12Z
canonical: "support.lusid.com/what-system-events-can-i-subscribe-to"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lusid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What system events can I subscribe to for notifications?

You can subscribe to:

- LUSID system events that occur in the core investment data management platform itself.
- LUSID system events that occur in ecosystem applications such as [Drive](/v1/docs/drive), [Scheduler](/v1/docs/scheduler) and [Luminesce](/v1/docs/luminesce-and-lumipy).
- Non-LUSID events that you trigger yourself by calling the [TriggerManualEvent](https://www.lusid.com/docs/api/notification/endpoints/manual-event/TriggerManualEvent/) API. You could of course attach a webhook to that event to call a LUSID API that then triggers a LUSID system event, and so on.

> **Note**: System events are not the same as [instrument events](/v1/docs/what-is-an-event-in-lusid).

To see the list of system events you can subscribe to, either:

- Sign in to the [LUSID web app](https://www.lusid.com/app/home) and navigate to **Notifications Management > Subscriptions**. Click the **Create subscription** button and view the **Event Type** dropdown. ![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/image(737).png?sv=2026-02-06&spr=https&st=2026-11-09T06%3A14%3A36Z&se=2026-11-09T07%3A14%3A36Z&sr=c&sp=r&sig=MPYNG0Dm0z7ueDw3ukrzHD2R9X4qgdtRzHvGn8T1beA%3D)
- [Obtain an API access token](/v1/docs/how-do-i-obtain-and-use-a-short-lived-api-access-token-from-okta) and call the [ListEventTypes](https://www.lusid.com/docs/api/notification/endpoints/event-types/ListEventTypes) API, for example:

```shell
curl -X GET "https://<your-domain>.lusid.com/notification/api/eventtypes"
  -H "Authorization: Bearer <your-API-access-token>"
```

The response contains a list of system events and their attributes. The following snippet shows the detail of the response for the LUSID `PortfolioCreated` system event. Note attributes common to all system events are in the `headerSchema`, while attributes specific to this system event are in the `bodySchema`:

```json
{
  "values": [
    {
      "id": "PortfolioCreated",
      "displayName": "Portfolio Created",
      "description": "An event of this type is fired whenever a PortfolioCreated event is created in LUSID",
      "application": "Lusid",
      "headerSchema": [
        { 
          "name": "eventType",
          "type": "String" 
        },
        { 
          "name": "requestId",
          "type": "String" 
        },
        { 
          "name": "userId",
          "type": "String" 
        },
        { 
          "name": "action",
          "type": "String" 
        },
        { 
          "name": "entityType",
          "type": "String" 
        },
        { 
          "name": "timestamp",
          "type": "String" 
        },
        { 
          "name": "href",
          "type": "String" 
        }
      ],
      "bodySchema": [
        { 
          "name": "portfolioScope",
          "type": "String" 
        },
        { 
          "name": "portfolioCode",
          "type": "String" 
        }
      ]
      "href": "https://<your-domain>.lusid.com/notification/api/eventtypes/PortfolioCreated"
    },
    ...
  ],
}
```

Note the following:

- You use the `id` of a system event (in this case, `PortfolioCreated`) to subscribe to it in the `eventType` field of a [subscription](/v1/docs/how-do-i-subscribe-to-an-event):

```plaintext
"matchingPattern": {
   "eventType": "PortfolioCreated",
   "filter": "Body.portfolioScope eq 'Finbourne-Examples'"
   }
```
- You can use attributes of a system event (in this case, `Body.portfolioScope` and `Body.portfolioCode`) in [condition filters](/v1/docs/using-lusid-filtering-syntax-to-subscribe-to-events-conditionally) (to subscribe to system events conditionally) and [mustache templates](/v1/docs/using-mustache-templates-to-enrich-notifications) (to enrich notification messages).