> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fourdos.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Read a member's stored attribute values

> The stored values on your organization's enabled, active attribute definitions. Unset and cleared values are absent, and a member with none returns `{ "values": [] }`. Core profile fields such as `dob` have no attribute value and are read from `GET /v1/users/{userId}` instead. A partner admin session reads its own organization; a platform admin session reads its active organization. Member sessions are refused with 404.



## OpenAPI

````yaml https://api.develop.fourdos.dev/openapi/partner.json get /v1/users/{userId}/attributes
openapi: 3.1.0
info:
  title: 4D OS Partner API
  version: 0.1.0
  description: >-
    REST API for 4D OS partners. Authenticate with your organization API key:
    `Authorization: Bearer <key>`.


    Requests and responses are JSON with `snake_case` field names. Errors share
    one envelope: `{ "error": { "code", "status", "message", "details"? } }`.


    Mutating endpoints that declare it accept an `Idempotency-Key` header so
    retries are safe.


    Bulk-migrating members? See the [Migrating to 4D
    guide](https://docs.fourdos.dev/walkthroughs/migrate-existing-members) for
    the canonical import schema, a worked example, and the `/v1/imports`
    sequence.
servers:
  - url: https://api.develop.fourdos.dev
security:
  - partnerApiKey: []
tags:
  - name: Users
    description: Create, read, and manage users and their org membership
  - name: Imports
    description: Bulk member import jobs (staging → validate → commit)
  - name: Consents
    description: Record, list and withdraw a member's consents and agreements
  - name: Rewards
    description: A member's reward catalog, claims and reward codes
  - name: XP
    description: >-
      A member's balance, earning headroom, expiry and boosts, and what each
      event pays
  - name: Tiers
    description: Read your organization's tier ladder
  - name: Webhooks
    description: Register webhook endpoints. Deliveries are not sent yet.
  - name: Events
    description: Refetch your organization's events from the last 30 days
  - name: API keys
    description: Issue, list, and revoke server-side organization API keys
  - name: Modules
    description: >-
      Publish private modules, install visible modules, and manage their
      credentials
  - name: Ingest
    description: Receive signed native events from an installed module
  - name: Engagement
    description: Browser event tracking (publishable keys) and tracking-key management
  - name: Revenue
    description: Report sales and refunds for the club's revenue dashboards
  - name: Ad delivery
    description: Fill a club site's ad slots, for anonymous or signed-in fans
  - name: Ad entries
    description: Fans entering a sponsor's draw, reported by the club's backend
paths:
  /v1/users/{userId}/attributes:
    get:
      tags:
        - Users
      summary: Read a member's stored attribute values
      description: >-
        The stored values on your organization's enabled, active attribute
        definitions. Unset and cleared values are absent, and a member with none
        returns `{ "values": [] }`. Core profile fields such as `dob` have no
        attribute value and are read from `GET /v1/users/{userId}` instead. A
        partner admin session reads its own organization; a platform admin
        session reads its active organization. Member sessions are refused with
        404.
      operationId: listMemberAttributeValues
      parameters:
        - name: userId
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: The stored values
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/StoredAttributeValues'
        '401':
          description: '`UNAUTHORIZED`: no valid credential'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: >-
            `NOT_FOUND`: the user is not a member of your organization, the id
            is malformed, or the caller is a member session
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - partnerApiKey: []
        - adminSession: []
components:
  schemas:
    StoredAttributeValues:
      type: object
      properties:
        values:
          type: array
          items:
            type: object
            properties:
              key:
                type: string
              value:
                description: The stored JSON value, with its JSON type kept.
              provenance:
                type: string
                enum:
                  - registration
                  - import
                  - partner_api
                  - admin
                  - self
                description: Who wrote the value.
              updated_at:
                type: string
                format: date-time
            required:
              - key
              - value
              - provenance
              - updated_at
      required:
        - values
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
            status:
              type: integer
            message:
              type: string
            details:
              type: object
              additionalProperties: true
          required:
            - code
            - status
            - message
      required:
        - error
  securitySchemes:
    partnerApiKey:
      type: http
      scheme: bearer
      description: >-
        Organization API key (`org_...`) sent as `Authorization: Bearer <key>`.
        Keys are scoped to one organization; every request operates within that
        tenant.
    adminSession:
      type: http
      scheme: bearer
      description: >-
        Partner admin session token sent as `Authorization: Bearer <token>`.
        Obtained by signing in (console or the email OTP endpoints) and
        completing the second factor; see the Authentication page.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.