UpdateTeamRequest

Body for updating a team. All fields are optional. The slug on the system team is immutable; the name is editable. The four role-contact fields use pointer semantics so the handler can distinguish "field absent" (no change) from "field present as empty string" (clear the slot to null). The registrant and admin slots cannot be cleared; supplying an empty string for either returns 422. Tech and billing accept an empty string to clear, unless a domain inheriting from the team sits on a TLD that requires the role (422 team.update.role_required_by_domain). Any non-empty value must resolve to an active contact in the caller's org, and a slot that changes must name a contact carrying every detail a registration needs (a name, email, phone and postal address). Resubmitting the contact a slot already holds is not a change and is not judged. enabled disables (false) or enables (true) a custom team, and may be the only field. While a team is disabled, only a request that also enables it may change its name, slug or contacts.

  • Updated display name.

  • Updated URL-safe slug. Pattern ^[a-z0-9][a-z0-9-]{0,62}$.

  • Updated registrant contact id. Required slot; non-empty values must reference an active contact, complete for registration when the slot changes. Empty string is rejected (422).

  • Updated admin contact id. Required slot; non-empty values must reference an active contact, complete for registration when the slot changes. Empty string is rejected (422).

  • Updated technical contact id. Optional slot; a contact must be complete for registration when the slot changes. Empty string clears the slot to null, refused (422) while a domain inheriting from the team sits on a TLD that requires a tech contact.

  • Updated billing contact id. Optional slot; a contact must be complete for registration when the slot changes. Empty string clears the slot to null, refused (422) while a domain inheriting from the team sits on a TLD that requires a billing contact.

  • Whether the team takes new domains, members and grants. false disables a custom team under any plan; the system team cannot be disabled. true enables a disabled team and requires a plan that includes custom teams. Sending the team's current state changes nothing.