User

A user account in the Acme identity platform.

Users are the primary subject of authentication, billing, and support workflows. Changing the shape of this message is a PACKAGE-breaking change.

Reading a user

• Identity: id is a stable UUID; email is the required login address.
• Lifecycle: state, created_at, and updated_at describe the account.
• Profile: display_name, nickname, and preferences hold presentation choices. Postal details use the Address message.

Example JSON

This response uses the ProtoJSON mapping: field names become lower camel case and enum values remain strings.

{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "email": "alex@example.com",
  "displayName": "Alex Chen",
  "state": "USER_STATE_ACTIVE",
  "createdAt": "2026-01-15T09:30:00Z",
  "preferences": {
    "marketingOptIn": false,
    "locale": "en-GB",
    "timeZone": "Europe/London"
  }
}

Creating an account

1. Set the required email and choose a display_name of 1 to 80 characters.
2. Add profile preferences or up to five postal addresses as needed.
3. Omit the output-only id, created_at, and updated_at fields from input.

Privacy: email and phone fields carry PII annotations. Their masking and hashing policies describe how consumers should handle sensitive data; the schema itself does not redact values.