LynceaAPI

Decline invitation

POST
/api/v1/me/invitations/{invitationId}/decline

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

invitationId*string

Response Body

application/json

curl -X POST "https://api.monitoring.crahe-arthur.com/api/v1/me/invitations/string/decline"
{
  "id": "string",
  "tenantId": {},
  "email": "string",
  "orgRole": {},
  "status": {},
  "invitedByUserId": {},
  "acceptedUserId": {},
  "expiresAt": "string",
  "respondedAt": "string",
  "createdAt": "string",
  "updatedAt": "string"
}

Accept invitation

Previous Page

Send logs

OpenTelemetry Protocol (OTLP) over HTTP — logs signal. Path follows the OTLP/HTTP spec literally (`/v1/logs`, no `/api/` prefix). **Authentication** : pass an API key with scope `write:logs` as `Authorization: Bearer lyn_live_xxx` (or `lyn_test_xxx`). API keys are created via `POST /api/v1/projects/{projectId}/api-keys`. **Body** : OTLP `ExportLogsServiceRequest` payload. Both `application/x-protobuf` (default for OTel SDKs and the OTel Collector) and `application/json` are accepted. `Content-Encoding: gzip` and `deflate` are decoded transparently. **Limits** : raw body 4 MiB ; decompressed body 16 MiB. Per-API-key and per-tenant token-bucket rate limit applied (see plan EPS quota). **v1 contract** : full-success only — the API never reports per-record rejects. Any record that fails normalization downstream goes to the DLQ asynchronously (Kafka `logs.dlq`).