Dash0 acquires Polar Signals

Manage Teams and Members

Create a new team

post/api/teams

Create a new team in the organization.

bash
Sample request
123456789101112131415161718192021
curl --request POST 'https://api.eu-west-1.aws.dash0.com/api/teams' \
--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"
]
}
}'

Request body required

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

Successfully created the team.

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