> ## 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. # List your published rewards with this member's verdict on each > Your organization's published rewards, newest first, each with whether this member can claim it now. Not paged. The member is not looked up: an id with no XP account in your organization is read with a balance of 0. A member session may name only its own user id; another id answers 404. ## OpenAPI ````yaml https://api.develop.fourdos.dev/openapi/partner.json get /v1/users/{userId}/rewards 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 `. 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}/rewards: get: tags: - Rewards summary: List your published rewards with this member's verdict on each description: >- Your organization's published rewards, newest first, each with whether this member can claim it now. Not paged. The member is not looked up: an id with no XP account in your organization is read with a balance of 0. A member session may name only its own user id; another id answers 404. operationId: listMemberRewardCatalog parameters: - name: userId in: path required: true schema: type: string responses: '200': description: The catalog content: application/json: schema: type: object properties: rewards: type: array items: $ref: '#/components/schemas/CatalogReward' required: - rewards '401': description: '`UNAUTHORIZED`: no valid credential' content: application/json: schema: $ref: '#/components/schemas/Error' '403': description: '`FORBIDDEN`: a platform admin session with no active organization' content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: >- `NOT_FOUND`: the id is malformed, or a member session named another user content: application/json: schema: $ref: '#/components/schemas/Error' security: - partnerApiKey: [] - adminSession: [] - memberSession: [] components: schemas: CatalogReward: type: object properties: id: type: string name: type: string description: type: string xp_cost: type: string description: A non-negative integer as a decimal string. remaining_stock: type: - string - 'null' description: Null when stock is unlimited. image_url: type: - string - 'null' description: An https URL, or null when the reward has no image. min_tier_id: type: string description: Present only on a tier-gated reward. min_tier_name: type: string description: Present only on a tier-gated reward. claimability: description: >- `affordable`, or `blocked` with one reason, checked in this order: `cap_reached`, `sold_out`, `tier_locked`, `short_xp`. oneOf: - type: object properties: state: const: affordable required: - state - type: object properties: state: const: blocked reason: const: cap_reached required: - state - reason - type: object properties: state: const: blocked reason: const: sold_out required: - state - reason - type: object properties: state: const: blocked reason: const: tier_locked required_tier: type: string xp_gap: type: string description: A non-negative integer as a decimal string. required: - state - reason - required_tier - xp_gap - type: object properties: state: const: blocked reason: const: short_xp shortfall: type: string description: A non-negative integer as a decimal string. required: - state - reason - shortfall required: - id - name - description - xp_cost - remaining_stock - image_url - claimability 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 `. 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 `. Obtained by signing in (console or the email OTP endpoints) and completing the second factor; see the Authentication page. memberSession: type: http scheme: bearer description: >- A signed-in member's session token sent as `Authorization: Bearer `. Accepted only on the operations that list it, and each of those says which user ids a member may name. Your backend uses the organization API key instead. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.