Get current team information
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
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)

