> ## Documentation Index > Fetch the complete documentation index at: https://docs.closient.com/llms.txt > Use this file to discover all available pages before exploring further. # List the caller's stored trait preferences > Returns the caller's full ``TraitPreference`` list — allergens to avoid, certifications required, dietary stances. Read-only; writes go through the dashboard at ``/preferences/`` (HTMX form, session-authenticated). Fresh accounts get a ``200`` with an empty list. Each row's ``trait`` slug is normalized lower-snake-case so it can be passed directly into ``POST /search/api/v1/search/session`` constraints (``exclude_allergens`` for ALLERGEN-category rows; ``require_certifications`` for DIETARY/RELIGIOUS/SOURCING rows). ## OpenAPI ````yaml /openapi/openapi-account.json get /account/api/v1/preferences openapi: 3.1.0 info: title: Account API version: 1.0.0 description: > Authenticate and manage users, organizations, and API keys. ## Authentication All endpoints require an API key passed via the `X-API-Key` HTTP header, unless otherwise noted. ``` X-API-Key: csb__ ``` Generate API keys in **Settings > API Keys** in your dashboard, or via the Account API. Session-based (cookie) authentication is also accepted for browser-based access. ## Rate Limits | Tier | Requests / minute | Requests / day | |-------------|-------------------|----------------| | Default | 300 | 10,000 | | Custom | Contact us | Contact us | Rate-limit headers are included on every response so callers can self-throttle without hitting our 429s ("informed governor"): - `RateLimit-Policy` — every active window, e.g. `300;w=60, 10000;w=86400` - `RateLimit-Limit` — quota for the **most-restrictive** currently-active window - `RateLimit-Remaining` — requests left in that window - `RateLimit-Reset` — seconds until that window resets (relative; clock-skew safe) Legacy `X-RateLimit-*` aliases are also emitted for back-compat. `X-RateLimit-Reset` keeps the absolute Unix-timestamp shape to avoid breaking existing consumers. When rate-limited, you receive `429 Too Many Requests` with a `retry_after_seconds` field in the error envelope and a `Retry-After` header. ## Pagination List endpoints return paginated results in this envelope: ```json { "data": [...], "pagination": { "page": 1, "page_size": 25, "total_count": 342, "total_pages": 14, "has_next": true, "has_previous": false } } ``` Use `?page=2&page_size=50` query parameters. Maximum page size is 100. ## Error Responses All errors conform to [RFC 9457 Problem Details](https://www.rfc-editor.org/rfc/rfc9457) with `Content-Type: application/problem+json`: ```json { "type": "https://closient.com/docs/errors/not_found", "title": "Not Found", "status": 404, "detail": "The requested resource was not found.", "error_code": "not_found", "retryable": false, "timestamp": "2026-03-31T12:00:00+00:00" } ``` Common error codes: `unauthorized` (401), `forbidden` (403), `not_found` (404), `validation_error` (422), `rate_limited` (429), `internal_error` (500). termsOfService: https://www.closient.com/terms/ servers: - url: https://www.closient.com security: [] tags: - name: Account description: Authenticate and introspect the current user and API key. - name: Organizations description: Create and manage organizations (businesses). - name: Members description: Invite, update, and remove organization members. - name: API Keys description: Create, list, and revoke API keys. - name: Preferences description: >- Read the authenticated user's stored trait preferences (allergens, dietary stances, certifications). Writes happen through the dashboard's HTMX form, not this API. externalDocs: description: Closient Documentation url: https://docs.closient.com paths: /account/api/v1/preferences: get: tags: - Preferences summary: List the caller's stored trait preferences description: >- Returns the caller's full ``TraitPreference`` list — allergens to avoid, certifications required, dietary stances. Read-only; writes go through the dashboard at ``/preferences/`` (HTMX form, session-authenticated). Fresh accounts get a ``200`` with an empty list. Each row's ``trait`` slug is normalized lower-snake-case so it can be passed directly into ``POST /search/api/v1/search/session`` constraints (``exclude_allergens`` for ALLERGEN-category rows; ``require_certifications`` for DIETARY/RELIGIOUS/SOURCING rows). operationId: apps_accounts_api_preferences_list_preferences parameters: [] responses: '200': description: OK content: application/json: schema: items: $ref: '#/components/schemas/TraitPreferenceOut' title: Response type: array security: - APIKeyHeaderAuth: [] - OAuthTokenAuth: [] - SessionAuth: [] components: schemas: TraitPreferenceOut: description: |- A single stored preference row. Returned by ``GET /account/api/v1/preferences``. The ``trait`` slug is lower-snake-case (``"tree_nuts"``, ``"vegan"``) so it can be passed directly into search constraints; the human-readable form is in ``trait_label``. examples: - category: ALLERGEN stance: AVOID trait: peanuts trait_label: Peanuts - category: DIETARY stance: REQUIRE trait: vegan trait_label: Vegan - category: SOURCING stance: PREFER trait: organic trait_label: Organic properties: trait: description: >- Lower-snake-case slug for the trait — pass directly into search constraints like ``exclude_allergens`` / ``require_certifications`` depending on the ``category``. title: Trait type: string trait_label: description: Human-readable trait name as stored on ``Trait.name``. title: Trait Label type: string category: $ref: '#/components/schemas/TraitCategoryEnum' description: >- Which axis the trait sits on. ``ALLERGEN`` preferences feed ``exclude_allergens``; ``DIETARY`` / ``RELIGIOUS`` / ``SOURCING`` feed ``require_certifications``. stance: $ref: '#/components/schemas/TraitStanceEnum' description: >- How the user feels about the trait. ``AVOID`` / ``REQUIRE`` are hard filters; ``PREFER`` is a ranking boost; ``NEUTRAL`` is recorded but not acted on. required: - trait - trait_label - category - stance title: TraitPreferenceOut type: object TraitCategoryEnum: description: |- Mirror of ``preferences.Trait.Category``. Categories partition the trait space into allergen / dietary / religious / sourcing concerns. Agents key off this to know which filter slot a preference should drive at search time (an ``ALLERGEN`` preference flows into ``exclude_allergens``; a ``DIETARY`` or ``SOURCING`` preference flows into ``require_certifications``). enum: - ALLERGEN - DIETARY - RELIGIOUS - SOURCING - OTHER title: TraitCategoryEnum type: string TraitStanceEnum: description: |- Mirror of ``preferences.TraitPreference.Stance``. ``AVOID`` and ``REQUIRE`` are hard filters; ``PREFER`` is a ranking boost; ``NEUTRAL`` is a recorded-but-don't-act stance (useful when a user has dismissed a UI prompt but hasn't expressed a preference). enum: - AVOID - REQUIRE - PREFER - NEUTRAL title: TraitStanceEnum type: string securitySchemes: APIKeyHeaderAuth: type: apiKey in: header name: X-API-Key OAuthTokenAuth: type: http scheme: bearer SessionAuth: type: apiKey in: cookie name: sessionid ````