> ## 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.

# Refetch your organization's events from the last 30 days

> Published events, oldest first, at most 1,000 per call and no cursor: when a call returns 1,000, call again with `since` set to the last `occurred_at` and drop the `event_id`s you already have. The filters are query parameters; the request has no body.



## OpenAPI

````yaml https://api.develop.fourdos.dev/openapi/partner.json post /v1/events
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/events:
    post:
      tags:
        - Events
      summary: Refetch your organization's events from the last 30 days
      description: >-
        Published events, oldest first, at most 1,000 per call and no cursor:
        when a call returns 1,000, call again with `since` set to the last
        `occurred_at` and drop the `event_id`s you already have. The filters are
        query parameters; the request has no body.
      operationId: listRecentEvents
      parameters:
        - name: since
          in: query
          required: false
          description: >-
            ISO 8601 UTC datetime. Events at or after it; defaults to 30 days
            ago, and an earlier value is moved up to that.
          schema:
            type: string
            format: date-time
        - name: types
          in: query
          required: false
          description: >-
            Comma-separated event types. `xp.redeemed` matches exactly;
            `identity.*` matches every type starting `identity.`.
          schema:
            type: string
      responses:
        '200':
          description: The events
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/EventEnvelope'
        '401':
          description: '`UNAUTHORIZED`: no valid credential'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            `FORBIDDEN`: the credential has no organization, for example a
            platform admin session with no active organization
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: '`VALIDATION_ERROR`: `since` is not an ISO 8601 UTC datetime'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - partnerApiKey: []
        - adminSession: []
components:
  schemas:
    EventEnvelope:
      type: object
      properties:
        id:
          type: string
        event_id:
          type: string
        event_type:
          type: string
        event_version:
          type: integer
          minimum: -9007199254740991
          maximum: 9007199254740991
        org_id:
          type:
            - string
            - 'null'
        occurred_at:
          type: string
        payload: {}
      required:
        - id
        - event_id
        - event_type
        - event_version
        - org_id
        - occurred_at
        - payload
      additionalProperties: false
    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.