> For the complete documentation index, see [llms.txt](https://docs.korewireless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.korewireless.com/kore/developers/event-streams/events.md). # Events ## Event Types Event types are the various kinds of events that you can configure in your streaming rule to receive at your destination. Each Event Type includes a reference to the schema, which defines the event type that the resource represents. The list of available events is listed below. ### Available Events The following is a list of all the products that leverage the event stream you can subscribe to. | Product | Event Types Overview | Getting Started | | --------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | Super SIM | Event on your devices' connection status and the data sessions | [Connection Events](https://docs.korewireless.com/en-us/supersim/get-started/get-started-with-super-sim-connection-events) | ## Event Schemas Schemas define the structure and format of the event data, serving as a crucial contract between our event stream and your destination. This helps to provide a clear and formal description of event content. You can review the event schema and explore the data fields before creating a rule to subscribe to them. Schemas are versioned, ensuring compatibility and seamless integration as your systems develop. When creating a streaming rule, you can select your preferred schema version, giving you control over the exact event structure you'll receive. Every event you receive, regardless of the type, will be of type `application/json` and follows the [CloudEvents](https://cloudevents.io/) [format](https://github.com/cloudevents/spec/blob/v1.0/spec.md). An example is as follows: ```json { "data": { ... }, "id": "fff521c2-c7db-4b53-a5a0-c5d5d01f66ce", "time": "2024-09-25T19:09:48.5842087+00:00", "type": "com.kore.eventstreams.test.event", "source": "kore-events", "dataschema": "/schemas/test/1", "specversion": "1.0", "datacontenttype": "application/json" } ``` ## Event Data Object Schema The schema of the ‘data’ schema object follows [JSON Schema](https://json-schema.org/), specifically [draft-07](https://json-schema.org/draft-07/schema), which is also described in the event schema definition of each event type. {% hint style="info" %} Each event type defines its own unique data object schema. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.korewireless.com/kore/developers/event-streams/events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.