Skip to main content
PATCH
/
v1beta1
/
telemetryrelay
/
endpoints
/
{ref.slug}
Update forwarding endpoint
curl --request PATCH \
  --url https://api.coreweave.com/v1beta1/telemetryrelay/endpoints/{ref.slug} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "ref": {
    "slug": "<string>"
  },
  "spec": {
    "displayName": "<string>"
  },
  "https": {}
}
'
{
  "endpoint": {
    "ref": {
      "slug": "<string>"
    },
    "spec": {
      "displayName": "<string>",
      "https": {
        "endpoint": "<string>",
        "tls": {
          "certificateAuthorityData": "<string>"
        }
      }
    },
    "status": {
      "createdAt": "2023-11-07T05:31:56Z",
      "updatedAt": "2023-11-07T05:31:56Z",
      "stateMessage": "<string>",
      "zonesActive": [
        {
          "zoneSlug": "<string>",
          "clusters": [
            {
              "id": "<string>"
            }
          ]
        }
      ],
      "credentialsConfigured": true,
      "credentialsUpdatedAt": "2023-11-07T05:31:56Z"
    }
  }
}

Authorizations

Authorization
string
header
default:Bearer [CW-API-TOKEN]
required

CoreWeave API access token sent as a bearer token.

Path Parameters

ref.slug
string
required

Body

application/json
ref
object
required

ForwardingEndpointRef uniquely identifies a forwarding endpoint within an organization.

Endpoints are referenced by a human-readable slug that must be unique per organization.

spec
object
required

Configuration for a forwarding endpoint. Includes a human-readable displayName and exactly one protocol-specific config. The protocol type is fixed at creation time and cannot be changed afterwards.

https
object

https credentials for HTTPS endpoints with basic auth.

Response

OK

endpoint
object

ForwardingEndpoint represents a destination where telemetry data can be forwarded. Endpoints are organization-scoped and identified by a unique slug. Self-service endpoints forward over HTTPS.

Last modified on June 15, 2026