HTTP / HTTPS API
| Typically Used By | Developers; Organizations with custom applications; API-first approaches |
| Description | A RESTful API endpoint that allows direct ingestion of logs from applications and custom scripts via HTTP or HTTPS protocols. |
| Official Vendor Documentation | https://www.rfc-editor.org/info/rfc9110/ |
| Setup Difficulty | 3 (Moderate) |
| Useful for | DevOps , SecOps |
| Primary Use Case | Custom log ingestion via API |
| Scenarios not Recommended | High-volume logging without batching; Environments with unreliable network connections |
| Data Volume Handling | Medium |
| Authentication Method | Token-based |
| Fault Tolerance | Medium |
| Additional Tools Required | None |
HTTP/HTTPS API ingestion provides a direct, flexible method for sending log data and events to Falcon LogScale Collector using standard HTTP POST requests. This approach enables applications, scripts, and services to push data directly to LogScale without requiring intermediate agents or collectors. The HTTP API supports both structured (JSON) and unstructured data formats, making it ideal for custom applications, serverless functions, webhooks, IoT devices, and any system capable of making HTTP requests. With built-in support for batching, compression, and authentication via bearer tokens, the HTTP API provides a simple yet powerful ingestion method that integrates seamlessly into modern application architectures and CI/CD pipelines.
HTTP / HTTPS API ingest flowThe following diagram shows how HTTP / HTTPS API log data flows through Log Collector's ingestion pipeline, highlighting specific parser types applied to the log data before data is compressed, stored in the repository, and indexed for searching: