Overview
You can report telemetry events directly to the Cylestio platform using this API.
API Specification
Section titled “API Specification”Endpoint
Section titled “Endpoint”Access the API by sending a POST request to the following endpoint:
https://api.cylestio.com/v1/telemetryEach request must contain the following headers in addition to the body:
Content-Type: application/jsonAuthorization: Bearer <jwt_token>Authentication
Section titled “Authentication”Authentication is done by exchanging an access key for a JWT token using the SDK that Cylestio provides. The JWT token must be included in the Authorization header:
Authorization: Bearer <jwt_token>Note: The access key can be obtained from the Cylestio management UI.
Response Codes
Section titled “Response Codes”- 200/201: Event successfully received
- 400: Bad request (invalid event format)
- 401: Authentication failed (invalid/expired JWT token)
- 403: Forbidden (insufficient permissions)
- 500: Internal server error
Quick Start Example
Section titled “Quick Start Example”Here’s a complete example of sending a session start event:
cURL Request
Section titled “cURL Request”curl -X POST https://api.cylestio.com/v1/telemetry \ -H "Content-Type: application/json" \ -H "Authorization: Bearer <your_jwt_token>" \ -d '{ "schema_version": "1.0", "timestamp": "2024-01-15T10:25:00.000Z", "trace_id": "session1234567890123456789012345678901234", "span_id": "sess1234567890ab", "name": "session.start", "level": "INFO", "agent_id": "my-agent", "session_id": "session-xyz789", "attributes": { "user.id": "user-456", "client.type": "gateway" } }'Success Response
Section titled “Success Response”HTTP 201 Created — Event successfully received and processed.
Next Steps: Check out the Event Structure page for the complete schema, or Event Types for all supported events like LLM calls and tool executions.