InvergeDocs

Telescope

Request-journey ingestion (native and OTLP/HTTP JSON) and SDK config.

SDK-facing (API-key) Telescope ingest. Un-prefixed (/partner/...).

  • POST /partner/telescope — Nexus SDK batches (PHP, JS, Python, .NET).
  • POST /partner/telescope/otlp/v1/traces — OpenTelemetry OTLP/HTTP JSON, so any OTel-instrumented app in any language reports without a Nexus SDK.
  • GET /partner/telescope/config — what to record (sampling, ignored paths and types, redaction, paused). Also returned on every ingest response.

POST /partner/telescope

POST 202 x-api-key

Body — IngestTelescopeDto

Prop

Type

Request
curl -X POST 'https://services.inverge.net/partner/telescope' \
  -H 'x-api-key: nxs_live_xxx' \
  -H 'content-type: application/json' \
  -d '{
      "batches": [
        {}
      ]
    }'

GET /partner/telescope/config

GET 200 x-api-key
Request
curl -X GET 'https://services.inverge.net/partner/telescope/config' \
  -H 'x-api-key: nxs_live_xxx'

POST /partner/telescope/otlp/v1/traces

POST 200 x-api-key

OTLP/HTTP JSON. Responds with an empty ExportTraceServiceResponse.

Body — Record<string, unknown>

Request
curl -X POST 'https://services.inverge.net/partner/telescope/otlp/v1/traces' \
  -H 'x-api-key: nxs_live_xxx'

On this page