Update team information
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Updated name for the team (1-512 characters)
Support email for service provider customers to use
Address for the team, typically used in email footers
Platform name to use for service provider clients
Whether to use the ChatOps onboarding group
Whether to enable manager ChatOps
Deprecated — values sent here are silently ignored. Use PUT /notification/subscription/team-channel to manage escalation inboxes.
Deprecated — values sent here are still written to the legacy column AND mirrored onto the team's notification_subscription escalation rows (which the send path reads). Teams without escalation recipients cannot store an override and fall back to the per-type default. Prefer managing escalation settings via notification_subscription.
Whether to enable test mode
Whether this demo team should be automatically deleted and recreated weekly
Message to display when ChatOps account is locked (max 25,000 characters)
Whether to enable automatic identity containment
Whether to enable automatic endpoint containment
Whether to enable automatic file containment
Welcome message for ChatOps workflows (max 25,000 characters)
Whether ChatOps requires second factor authentication
Maximum ChatOps operations allowed per day (minimum 0)
Maximum automatic containments allowed per day (minimum 0)
Delay in minutes before escalating ChatOps failures (1-60 minutes)
Whether to disable the maximum ChatOps limit
Signature for ChatOps communications (max 1,200 characters)
Subject line for ChatOps communications (max 1,200 characters)
Deprecated — values sent here are still written to the legacy column AND mirrored onto the team's notification_subscription escalation rows (which the send path reads). Teams without escalation recipients fall back to rich-formatting on by default. Prefer managing escalation settings via notification_subscription.
When managed by a service provider, denotes the team that is used for internal operations across their clients
Subscription SKU tier for the team
identity, adr Contract/subscription start date (ISO string)
Contract/subscription end date (ISO string)
Whether this team is a proof-of-value trial
When true, source system updates are skipped for detections managed by a third party (e.g. Falcon Complete)
Response
Unique identifier for the team
Name of the team
Whether this is a demo team
Whether this demo team is automatically deleted and recreated weekly
Whether the team is in test mode
Delay in minutes before escalating ChatOps failures
How long monitors run for this team, in hours
Whether automatic identity containment is enabled
Whether automatic endpoint containment is enabled
Whether automatic file containment is enabled
Deprecated — escalation emails are now stored in notification_subscription. Use GET /notification/subscription/team-channel?type=NEW_CASE_ESCALATION instead.
Lists new case escalation subscription emails for this team: the team's own emails plus any emails inherited from the parent Service Provider.
URL of the team logo
Whether ChatOps requires second factor authentication
Message to display when ChatOps account is locked
Timestamp when the team was created
Deprecated — escalation rich-formatting is now stored per recipient in notification_subscription.
Whether manager ChatOps is enabled
Signature for ChatOps communications
Subject line for ChatOps communications
Whether to auto-subscribe service provider users to notifications for this team
Subscription SKU tier for the team
identity, adr Active add-on SKUs for the team
data Whether this team is a proof-of-value trial
Whether to skip source system updates for detections managed by a third party (e.g. Falcon Complete)
Whether the team has completed the onboarding checklist
Welcome message for ChatOps workflows
Platform name to use for service provider clients
Maximum ChatOps operations allowed per day
Maximum automatic containments allowed per day
Deprecated — the escalation subject is now stored per recipient in notification_subscription (null → scope-aware per-type default).
Whether this team is a service provider
Name of the parent team if this is a sub-team
ID of the parent team if this is a sub-team
Whether the parent team is a service provider (null when no parent)
Whether this is an operating team for service providers
Whether to use the ChatOps onboarding group
Whether to allow bulk SMS invites without limit checks
The number of billable users for the team
The number of billable endpoints for the team
The number of team members where the team is their parent team (excluding external members)
Support email for service provider customers to use
Address for the team, typically used in email footers
Contract/subscription start date
Contract/subscription end date
License ID used for billing user counts (null = derived counting)
License ID used for billing endpoint counts (null = derived counting)

