Team

An organization team. Teams group org members for shared configuration. Each org has exactly one system team named "General" which is created automatically and cannot be deleted. Every team carries four role-contact slots embedded as full contact resources: registrant_contact and admin_contact are required on live teams; tech_contact and billing_contact are optional and may be null. The member_preview field is a capped, embedded snapshot of the team's most-recently-active members so frontends can render avatar stacks without a second round-trip. Use /teams/{team_id}/members for the full paginated list.

  • Resource type identifier, always "team"

  • Embedded billing contact. Optional; null when unset.

    Properties: 25
  • Capped preview of the team's most-recently-active members, plus the team's full member count. Always present; empty for newly created teams or when preview enrichment fails.

    Properties: 3
  • Creation timestamp in RFC 3339 UTC form

  • Last-update timestamp in RFC 3339 UTC form

  • Stable identifier for the team

  • Identifier of the owning organization

  • Display name (e.g. "General", "London")

  • URL-safe slug, unique within the org

  • True when this is the org's system team. Its slug is locked and the row cannot be deleted; name and other fields remain editable.

  • Embedded registrant contact. Required on live teams; clearing on update is rejected. Null only on pre-backfill rows.

    Properties: 25
  • Embedded admin contact. Required on live teams; clearing on update is rejected. Null only on pre-backfill rows.

    Properties: 25
  • Embedded technical contact. Optional; null when unset.

    Properties: 25