> ## 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 when a member's XP lapses > With expiry off, `{ "enabled": false, "window_days": null, "next": null, "schedule": [] }` for any id. With it on, a member who has never earned gets `next: null` and an empty `schedule`. 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}/xp-expiry 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}/xp-expiry: get: tags: - XP summary: Read when a member's XP lapses description: >- With expiry off, `{ "enabled": false, "window_days": null, "next": null, "schedule": [] }` for any id. With it on, a member who has never earned gets `next: null` and an empty `schedule`. A member session may name only its own user id; another id answers 404. operationId: getMemberXpExpiry parameters: - name: userId in: path required: true schema: type: string responses: '200': description: The expiry schedule content: application/json: schema: $ref: '#/components/schemas/MemberXpExpiry' '401': description: '`UNAUTHORIZED`: no valid credential' content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: >- `NOT_FOUND`: the id is malformed; with expiry on, the user is not a member of your organization; or a member session named another user content: application/json: schema: $ref: '#/components/schemas/Error' security: - partnerApiKey: [] - adminSession: [] - memberSession: [] components: schemas: MemberXpExpiry: type: object properties: enabled: type: boolean window_days: type: - integer - 'null' next: oneOf: - $ref: '#/components/schemas/XpExpiryBucket' - type: 'null' description: The earliest entry still ahead of now. schedule: type: array description: >- One entry per UTC day the member loses XP, earliest first. The first can already be past when the lapse run has not caught up; that XP is still spendable. items: $ref: '#/components/schemas/XpExpiryBucket' required: - enabled - window_days - next - schedule 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 XpExpiryBucket: type: object properties: amount: type: string description: A non-negative integer as a decimal string. expires_at: type: string format: date-time required: - amount - expires_at 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.