> For the complete documentation index, see [llms.txt](https://support.attackforge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.attackforge.com/app/modules/self-service-events-api.md). # Self-Service Events API {% hint style="info" %} See for Events docs. {% endhint %} ## Using the Events API The Events API can be used in two ways: 1. Through event-based triggers in [Flows](/app/modules/flows.md) 2. By connecting directly to the Events channel with a websocket client ## Accessing the Self-Service Events You can view which Events you have access to within the `Integration Docs` section available from the main menu:
Access to every Event is *disabled by default for every application user* - even for administrators. If the event shows a `padlock` - that means *you do not have access to that event*.
You can be given access to any Event in either of the following ways: 1. Administrator grants you direct access to an Event 2. Administrator grants a `Group` access to an Event, and you are a member of that group. ### Granting Individual User Access 1. From the `Users` module, select the user and click on `Access`
2. Expand `Events (Flows / Self-Service API)`. Click `Add Events`.
2. Select the required Events. Click `Add`.
### Granting Access to Groups {% hint style="info" %} When access to any Event is granted to a group - every Group Member within the group will receive access to that Event. {% endhint %} 1. From the `Groups` module, select the group and click on `Other Access`
2. Expand `Events (Flows / Self-Service API)`. Click `Add Events`.
3. Select the required Events. Click `Add`.
For more information - see [Getting Started](https://docs.attackforge.com/events-api/pages/getting-started) --- # 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://support.attackforge.com/app/modules/self-service-events-api.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.