# API-Based Monitoring Astral supports data ingestion through **API-based monitoring**, enabling direct integration with cloud platforms, SaaS applications, and security services that expose events and telemetry via programmatic interfaces. This capability allows Astral to collect security-relevant information without relying on local agents or file-based logging, making it particularly effective for distributed and cloud-native environments. Through API integrations, Astral can retrieve events related to authentication activity, configuration changes, administrative actions, resource usage, and other service-level operations. This approach ensures continuous visibility into environments where traditional log collection is limited or not applicable, while preserving consistency with on-premises monitoring models. All data collected via APIs is processed through Astral’s unified ingestion and analysis pipeline. Events are analyzed, interpreted, normalized, and correlated with telemetry from other sources such as network monitoring, file-based logs, and infrastructure signals. This correlation enriches API-derived events with broader operational and security context, enabling more accurate detection and investigation. By incorporating API-based monitoring into the Astral SIEM, cloud and SaaS activity becomes an integral part of the overall security monitoring strategy. These events seamlessly feed into Inopli’s Response and RPA capabilities, allowing identification, prioritization, and automated response actions to be applied consistently across both cloud and traditional environments. --- # 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.inopli.com/astral/data-ingestion/log-sources/api-based-monitoring.md?ask= ``` 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.