Server APITeams

Update a team

Update the team information by ID.

Path parameters

team_idstringRequired

Request

This endpoint expects an object.
client_read_only_metadatamap from strings to anyOptional

Client read-only, server-writable metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client. The client can read this data, but cannot modify it. This is useful for things like subscription status.

server_metadatamap from strings to anyOptional
Server metadata. Used as a data store, only accessible from the server side. You can store secret information related to the team here.
display_namestringOptional

Human-readable team display name. This is not a unique identifier.

profile_image_urlstringOptional
URL of the profile image for team. Can be a Base64 encoded image. Must be smaller than 100KB. Please compress and crop to a square before passing in.
client_metadatamap from strings to anyOptional
Client metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client.

Response

Successful response
created_at_millisdouble

The time the team was created (the number of milliseconds since epoch, January 1, 1970, UTC)

idstring
The unique identifier of the team
display_namestring

Human-readable team display name. This is not a unique identifier.

server_metadatamap from strings to anyOptional
Server metadata. Used as a data store, only accessible from the server side. You can store secret information related to the team here.
profile_image_urlstringOptional
URL of the profile image for team. Can be a Base64 encoded image. Must be smaller than 100KB. Please compress and crop to a square before passing in.
client_metadatamap from strings to anyOptional
Client metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client.
client_read_only_metadatamap from strings to anyOptional

Client read-only, server-writable metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client. The client can read this data, but cannot modify it. This is useful for things like subscription status.