curl or any other HTTP client. The API lets you manage forwarding endpoints and pipelines and list telemetry streams. These resources forward CoreWeave audit logs from the managed observability platform to your HTTPS destinations.
For a conceptual walkthrough of Telemetry Relay (what an endpoint, pipeline, and stream are, and how they wire together), see the CoreWeave Telemetry Relay overview. For Cloud Console procedures, see Configure Telemetry Relay.
- The API server is
https://api.coreweave.com. - Replace
[CW-API-TOKEN]in the examples on each operation page with your CoreWeave API access token. - Write operations (
POST,PATCH,DELETE) require the Telemetry Relay Admin role. Read operations (GET) require the Telemetry Relay Reader role. - For information on required permissions, see IAM Access Policies.
If you call a write operation (
POST, PATCH, DELETE) before your organization is enabled for self-service, the request returns 404 with "reason": "TELEMETRYRELAY_ORGANIZATION_NOT_FOUND". Contact Support to request enablement.Endpoints
The API exposes three resource families: forwarding endpoints, forwarding pipelines, and telemetry streams. Per-resource operations take the resource’sref.slug (a project-scoped human-readable name) as a path parameter, shown as {ref.slug} in the path templates below.