---
title: "Create a CoreWeave integration account"
method: POST
path: "/api/v2/integration-interfaces/coreweave-cloud/accounts"
tags: ["CoreWeave Integration"]
---

# Create a CoreWeave integration account

`POST /api/v2/integration-interfaces/coreweave-cloud/accounts`

## Request

- Base URL: `https://api.datadoghq.com`
- URL: `https://api.datadoghq.com/api/v2/integration-interfaces/coreweave-cloud/accounts`
- Auth: one of:
  - API key in header `DD-API-KEY` and API key in header `DD-APPLICATION-KEY`
  - OAuth 2
    - Authorization code: `/oauth2/v1/authorize`
    - Token URL: `/oauth2/v1/token`

Create a CoreWeave integration account.

## Request body

- CoreWeaveCloudIntegrationAccountCreateRequest: Request payload to create a CoreWeave integration account.
  - `data` CoreWeaveCloudIntegrationAccountCreateData, required: Data envelope for creating a CoreWeave integration account.
    - `attributes` CoreWeaveCloudIntegrationAccountCreateAttributes, required: Writable attributes used to create a CoreWeave integration account.
      - `authentication` CoreWeaveCloudIntegrationAccountAuthenticationRequest, required: API token authentication, the only method CoreWeave integration accounts support. Create the token in the CoreWeave Cloud console under Access Tokens; it starts with `CW-SECRET-`. The user who owns the token must have the Observability Viewer role, because tokens inherit their user's permissions.
        - `api_token` string, required: Secret CoreWeave API access token used to authenticate with CoreWeave. Values that do not start with `CW-SECRET-` are rejected with a `422` response.
        - `auth_type` 'coreweave_api_token', required: The authentication method type.
      - `dataflows` CoreWeaveCloudIntegrationDataflowsRequest: Data Datadog collects from CoreWeave, keyed by dataflow id. Each dataflow turns on a distinct kind of collection: set `enabled` to start or stop it. Defaults listed on each dataflow apply when the account is created; on update, omitted dataflow ids keep their current values. Collection runs with the API access token in `authentication`, whose user must have the Observability Viewer role; a dataflow enabled without that role is stored but collects no data.
        - `coreweave-cloud-logs` CoreWeaveCloudLogsIntegrationDataflowRequest: Service logs for CoreWeave-managed components in each CoreWeave region: the CKS control plane (such as `kube-apiserver` and `etcd`), CoreWeave add-on services in the `cw-*` and `kube-system` namespaces, SUNK, and node system logs such as `kubelet` and `containerd`. Logs from your own workloads and Kubernetes audit logs are not collected. Logs are sent with `source:coreweave`, with CoreWeave log labels such as `namespace`, `app`, and `systemd_unit` added as tags.
          - `enabled` boolean: Whether Datadog collects this data. Defaults to `false`; set to `true` to start collection.
        - `coreweave-cloud-metrics` CoreWeaveCloudMetricsIntegrationDataflowRequest: Metrics from your CoreWeave organization: CoreWeave service metrics collected through its PromQL-compatible Prometheus endpoint, plus the `coreweave.*` namespaces from CoreWeave products such as Kubernetes, Database, Distributed File Storage, Inference, and Object Storage. Compute metrics (`coreweave.bare_metal`, `coreweave.gpu`, `coreweave.nccl`, and `coreweave.node`) are in Preview. Container metrics are not collected; install the Datadog Agent on your clusters for those.
          - `enabled` boolean: Whether Datadog collects this data. Defaults to `true`; set to `false` to stop collection.
      - `name` string, required: Human-readable name of the CoreWeave integration account.
      - `settings` CoreWeaveCloudIntegrationAccountSettingsRequest, required: Settings for creating the CoreWeave integration account.
        - `account_tags` string[]: Tags added to all metrics and logs collected from this CoreWeave account. Defaults to no tags.
        - `cluster_filters` string[]: Tag-filter rules limiting metric collection to matching clusters, for cost savings. Include rules (`key:value`) are combined with OR, exclusion rules (`!key:value`) are then applied with AND, and `?` and `*` are wildcards; for example `cluster:prod-*` collects only matching clusters and `!cluster:dev` excludes a cluster. Defaults to no filters: every cluster is collected. Only cluster-scoped metrics are filtered; billing and object storage metrics are always collected.
    - `type` 'integration-account', required: The type of the integration account resource. Always `integration-account`.

## Response `201`

Created

- CoreWeaveCloudIntegrationAccountResponse: Response payload for a single CoreWeave integration account.
  - `data` CoreWeaveCloudIntegrationAccountResponseData, required: Data envelope of a CoreWeave integration account, including server-assigned identity.
    - `attributes` CoreWeaveCloudIntegrationAccountResponseAttributes, required: Attributes of a CoreWeave integration account returned in responses.
      - `authentication` CoreWeaveCloudIntegrationAccountAuthenticationResponse: The API token authentication method configured on the account.
        - `auth_type` 'coreweave_api_token', required: The authentication method type.
      - `dataflows` CoreWeaveCloudIntegrationDataflowsResponse: Data Datadog collects from CoreWeave, keyed by dataflow id.
        - `coreweave-cloud-logs` CoreWeaveCloudLogsIntegrationDataflowResponse: Service logs for CoreWeave-managed components in each CoreWeave region: the CKS control plane (such as `kube-apiserver` and `etcd`), CoreWeave add-on services in the `cw-*` and `kube-system` namespaces, SUNK, and node system logs such as `kubelet` and `containerd`. Logs from your own workloads and Kubernetes audit logs are not collected. Logs are sent with `source:coreweave`, with CoreWeave log labels such as `namespace`, `app`, and `systemd_unit` added as tags.
          - `enabled` boolean: Whether Datadog collects this data. Absent when the dataflow has never been configured, in which case the documented default applies.
        - `coreweave-cloud-metrics` CoreWeaveCloudMetricsIntegrationDataflowResponse: Metrics from your CoreWeave organization: CoreWeave service metrics collected through its PromQL-compatible Prometheus endpoint, plus the `coreweave.*` namespaces from CoreWeave products such as Kubernetes, Database, Distributed File Storage, Inference, and Object Storage. Compute metrics (`coreweave.bare_metal`, `coreweave.gpu`, `coreweave.nccl`, and `coreweave.node`) are in Preview. Container metrics are not collected; install the Datadog Agent on your clusters for those.
          - `enabled` boolean: Whether Datadog collects this data. Absent when the dataflow has never been configured, in which case the documented default applies.
      - `name` string, required: Human-readable name of the CoreWeave integration account.
      - `settings` CoreWeaveCloudIntegrationAccountSettingsResponse, required: Settings configured on the CoreWeave integration account.
        - `account_tags` string[]: Tags added to all data collected from this CoreWeave account.
        - `cluster_filters` string[]: Tag-filter rules limiting metric collection to matching clusters. Absent when no filters are configured.
    - `id` string, required: Server-generated unique identifier of the CoreWeave integration account.
    - `type` 'integration-account', required: The type of the integration account resource. Always `integration-account`.

## Other responses

- `400`: Bad Request
- `403`: Forbidden
- `404`: Not Found
- `422`: The server cannot process the request because it contains invalid data.
- `429`: Too many requests

## Changes

- **2026-11-17** `5eef128a87a0`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/changes/api/v2/integration-interfaces/coreweave-cloud/accounts/post.md)

---

[API](https://skmtc.dev/datadog/apis/datadog-api-v2-collection.md) - [All operations](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/llms.txt) - [OpenAPI document](https://skmtc.dev/datadog/apis/datadog-api-v2-collection/revisions/8d1a5e5973da?raw)
