Manage Teams and Members

Update or insert a specific team by its origin or id

put/api/teams/{originOrId}

Update or insert a specific team by its origin or id. In case a team with the given origin or id is found it will be updated. If there is no team found a new team will be created and the given originOrId is used as origin.

spec.display fully replaces the existing display values. spec.members is reconciled declaratively — the resulting membership is exactly the set given in the request body (adds and removes are computed against the current membership).

Parameters 1

originOrIdpathrequired

The origin or id of the team.

string

bash

Sample request123456789101112131415161718192021
curl --request PUT 'https://api.eu-west-1.aws.dash0.com/api/teams/123e4567-e89b-42d3-a456-426614174000' \
  --header "Authorization: Bearer ${DASH0_AUTH_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data-raw '{
  "kind": "Dash0Team",
  "metadata": {
    "name": "Example"
  },
  "spec": {
    "display": {
      "name": "Example",
      "color": {
        "from": "example",
        "to": "example"
      }
    },
    "members": [
      "example"
    ]
  }
}'

Server

Request body required

References TeamDefinitionV1Alpha1

v1alpha1 team definition. metadata.name is the team's technical name (used e.g. as the CRD name in an operator manifest or a Terraform resource ID), spec.display carries the human-facing attributes (name, description, color) and spec.members is the declarative list of member IDs that make up the team. metadata.name and spec.display.name are persisted independently.

TeamApiVersion

Optional on write requests for backwards compatibility: defaults to dash0.com/v1alpha1 when omitted. Always populated on read responses.

"dash0.com/v1alpha1"

stringrequired

"Dash0Team"

TeamMetadatarequired

TeamSpecrequired

Responses

The updated or created team.