Base URL
Authentication
LogFleet uses two authentication methods:| Method | Header | Use Case |
|---|---|---|
| JWT Bearer | Authorization: Bearer {token} | Dashboard, user operations |
| API Key | X-API-Key: {key} | Edge agents |
API Groups
Authentication
User registration, login, and password management
Agents
Manage edge agents and their configurations
API Keys
Create and manage API keys for edge agents
Streaming
On-demand log streaming from edge agents
Metric Configs
Configure log-to-metric extraction rules
Edge API
Endpoints used by edge agents (API Key auth)
Request Format
All requests should include:Response Format
Successful responses return the requested data:Error Handling
Errors return appropriate HTTP status codes with details:Status Codes
| Code | Description |
|---|---|
200 | Success |
201 | Created |
204 | No Content (successful deletion) |
400 | Bad Request - Invalid parameters |
401 | Unauthorized - Invalid/missing auth |
403 | Forbidden - Insufficient permissions |
404 | Not Found - Resource doesn’t exist |
409 | Conflict - Resource already exists or version conflict |
429 | Too Many Requests - Rate limited |
500 | Internal Server Error |
Rate Limiting
API requests are rate limited per endpoint group:| Endpoint Group | Rate Limit |
|---|---|
| Authentication | 10 req/min |
| Dashboard | 60 req/min |
| Agents, API Keys | 100 req/min |
| Edge API | 1000 req/min |
| Streaming | 10 req/min |
Pagination
List endpoints support pagination:| Parameter | Type | Default | Description |
|---|---|---|---|
page | integer | 1 | Page number (1-indexed) |
page_size | integer | 20 | Items per page (max 100) |