# Get user settings

Returns a canonical snapshot of user settings including profile fields, roles, capabilities,
onboarding status, notification defaults, and integration capabilities. This is the single
source of truth for frontend gating decisions.

Endpoint: GET /me/settings
Version: 0.1.0
Security: bearerAuth

## Response 200 fields (application/json):

  - `profile` (object, required)

  - `profile.display_name` (string,null, required)
    User display name
    Example: "John Doe"

  - `profile.profile_photo_url` (string,null, required)
    Profile photo URL (must start with https://)
    Example: "https://example.com/photo.jpg"

  - `profile.email_verified_at` (string,null, required)
    ISO timestamp when email was verified, or null if not verified
    Example: "2025-01-01T00:00:00.000Z"

  - `roles` (array, required)
    User roles (ARTIST, BRAND, INFLUENCER, or ADMIN)
    Enum: "ARTIST", "BRAND", "INFLUENCER", "ADMIN"

  - `capabilities` (object, required)

  - `capabilities.can_join_campaigns` (boolean, required)
    Whether user can join campaigns (true for INFLUENCER or ADMIN)
    Example: true

  - `capabilities.can_create_campaigns` (boolean, required)
    Whether user can create campaigns (true for BRAND, ARTIST, or ADMIN)

  - `onboarding_status` (object, required)

  - `onboarding_status.is_complete` (boolean, required)
    Whether core onboarding is complete (all 4 universal requirements met)
    Example: true

  - `onboarding_status.missing` (array, required)
    List of missing onboarding requirements
    Enum: "display_name", "profile_photo", "email_verified", "role_assigned"

  - `notification_defaults` (object,null, required)
    User notification preferences (key-value pairs)
    Example: {"email":true,"push":false}

  - `integration_capabilities` (array, required)
    Read-only summaries of platform integration capabilities
    Example: []

  - `integration_capabilities.platform` (string, required)
    Social platform identifier
    Enum: "INSTAGRAM", "TIKTOK"

  - `integration_capabilities.status` (string, required)
    Current capability state of the integration
    Enum: "NOT_CONNECTED", "VALID", "LIMITED", "ERROR"

  - `integration_capabilities.capabilities` (object, required)
    Platform-specific capability flags
    Example: {"canReadProfile":false,"canReadMedia":false,"canReadInsights":false}

  - `integration_capabilities.reason_code` (string,null, required)
    Machine-readable reason code for the current status
    Example: "NOT_CONNECTED"

  - `integration_capabilities.reason_message` (string,null, required)
    Human-readable message explaining the current status
    Example: "Account not connected"

  - `integration_capabilities.last_verified_at` (string,null, required)
    ISO timestamp of last verification (null if not connected)

## Response 401 fields (application/json):

  - `error` (string, required)
    Error code that identifies the type of error. This is a stable identifier that can be used
for programmatic error handling. Common codes include:
- NOT_FOUND - Resource not found
- VALIDATION_ERROR - Input validation failed
- PERMISSION_DENIED - User lacks permission for the action
- CONFLICT - Request conflicts with current resource state
- UNAUTHORIZED - Authentication required
- INTERNAL_SERVER_ERROR - Unexpected server error
    Example: "VALIDATION_ERROR"

  - `message` (string, required)
    User-friendly error message that should always be displayed to end users. This message is
designed to be clear, actionable, and free of technical details.

This field is always present and contains the primary message for end users.
    Example: "The email address you entered is not valid. Please check the format and try again."

  - `technicalMessage` (string)
    Optional technical message for developers. Contains detailed information including IDs,
error codes, and technical context. Only included when it differs from the user-friendly
message field. When present, developers can use this for debugging while end users
should see the message field.
    Example: "Campaign with ID campaign_123 not found"

  - `details` (object)
    Additional error details (optional). May contain structured information about the error,
such as validation field errors or additional context.

  - `requestId` (string)
    Unique request identifier for tracing. Included in X-Request-ID header and can be used
to correlate errors with server logs.
    Example: "550e8400-e29b-41d4-a716-446655440000"

  - `timestamp` (string, required)
    ISO 8601 timestamp when the error occurred
    Example: "2024-01-01T00:00:00Z"

## Response 404 fields (application/json):

  - `error` (string, required)
    Error code that identifies the type of error. This is a stable identifier that can be used
for programmatic error handling. Common codes include:
- NOT_FOUND - Resource not found
- VALIDATION_ERROR - Input validation failed
- PERMISSION_DENIED - User lacks permission for the action
- CONFLICT - Request conflicts with current resource state
- UNAUTHORIZED - Authentication required
- INTERNAL_SERVER_ERROR - Unexpected server error
    Example: "VALIDATION_ERROR"

  - `message` (string, required)
    User-friendly error message that should always be displayed to end users. This message is
designed to be clear, actionable, and free of technical details.

This field is always present and contains the primary message for end users.
    Example: "The email address you entered is not valid. Please check the format and try again."

  - `technicalMessage` (string)
    Optional technical message for developers. Contains detailed information including IDs,
error codes, and technical context. Only included when it differs from the user-friendly
message field. When present, developers can use this for debugging while end users
should see the message field.
    Example: "Campaign with ID campaign_123 not found"

  - `details` (object)
    Additional error details (optional). May contain structured information about the error,
such as validation field errors or additional context.

  - `requestId` (string)
    Unique request identifier for tracing. Included in X-Request-ID header and can be used
to correlate errors with server logs.
    Example: "550e8400-e29b-41d4-a716-446655440000"

  - `timestamp` (string, required)
    ISO 8601 timestamp when the error occurred
    Example: "2024-01-01T00:00:00Z"