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

# List activities

> Pages through the workspace's activities, newest first: an account's timeline with filter[account][eq], a person's with filter[participant][eq]. Filter with `filter[<key>][<op>]=<value>` (conditions are ANDed; `in` repeats the parameter): `account`, `participant` (eq, in: ids), `type` (eq, in: email, meeting, slack, teams, ticket, survey, chatter, note, linkedin, marketing_event), `source` (eq, in: such as gmail, outlook_mail, zoom, gong, slack, zendesk, statisfy, manual, api), `sentiment` (eq, in: positive, neutral, negative), each taking one condition, and `date` (eq, gt, gte, lt, lte: YYYY-MM-DD, compared as whole UTC days), which takes several. Anything else is a 422. An activity with no date is not listed. An activity is anything on an account's timeline in the app: an email thread, a meeting (from any recorder), a Slack or Teams thread, a support ticket, a survey response, a Salesforce Chatter thread, a note logged in the app, a campaign's send, a LinkedIn conversation, a marketing event, or one another system pushed. `accounts` are the accounts whose timeline shows it; `participants` the people linked to it, each with their `type`. `sentiment` and `one_liner` are the AI's, or a person's where they changed it in the app. `meeting_id` is set on a meeting Statisfy's notetaker recorded.



## OpenAPI

````yaml /api/statisfy-api.openapi.json get /v1/activities
openapi: 3.1.0
info:
  description: >-
    The agent-first Statisfy API. Authenticate with an API key (`Authorization:
    Bearer stfy_live_…`), then call `GET /v1/meta/capabilities` to discover
    every operation and its schemas.
  title: Statisfy API
  version: 1.0.0
servers:
  - url: https://api.statisfy.com
    description: Production
security: []
paths:
  /v1/activities:
    get:
      tags:
        - activities
      summary: List activities
      description: >-
        Pages through the workspace's activities, newest first: an account's
        timeline with filter[account][eq], a person's with
        filter[participant][eq]. Filter with `filter[<key>][<op>]=<value>`
        (conditions are ANDed; `in` repeats the parameter): `account`,
        `participant` (eq, in: ids), `type` (eq, in: email, meeting, slack,
        teams, ticket, survey, chatter, note, linkedin, marketing_event),
        `source` (eq, in: such as gmail, outlook_mail, zoom, gong, slack,
        zendesk, statisfy, manual, api), `sentiment` (eq, in: positive, neutral,
        negative), each taking one condition, and `date` (eq, gt, gte, lt, lte:
        YYYY-MM-DD, compared as whole UTC days), which takes several. Anything
        else is a 422. An activity with no date is not listed. An activity is
        anything on an account's timeline in the app: an email thread, a meeting
        (from any recorder), a Slack or Teams thread, a support ticket, a survey
        response, a Salesforce Chatter thread, a note logged in the app, a
        campaign's send, a LinkedIn conversation, a marketing event, or one
        another system pushed. `accounts` are the accounts whose timeline shows
        it; `participants` the people linked to it, each with their `type`.
        `sentiment` and `one_liner` are the AI's, or a person's where they
        changed it in the app. `meeting_id` is set on a meeting Statisfy's
        notetaker recorded.
      operationId: activities_list
      parameters:
        - in: query
          name: limit
          required: false
          schema:
            default: 25
            maximum: 100
            minimum: 1
            type: integer
        - description: '`next_cursor` from the previous page'
          in: query
          name: cursor
          required: false
          schema:
            anyOf:
              - type: string
              - type: 'null'
            default: null
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ActivityPage'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    ActivityPage:
      properties:
        data:
          items:
            $ref: '#/components/schemas/Activity'
          title: Data
          type: array
        has_more:
          default: false
          title: Has More
          type: boolean
        next_cursor:
          anyOf:
            - type: string
            - type: 'null'
          title: Next Cursor
      required:
        - data
      title: ActivityPage
      type: object
    Activity:
      properties:
        accounts:
          description: The accounts whose timeline shows it
          items:
            type: string
          title: Accounts
          type: array
        date:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            When it happened, ISO 8601 UTC: a meeting's scheduled start, an
            email or chat thread's latest message (so a thread moves up as it
            grows). Null for one with no date, which the list leaves out
          title: Date
        id:
          title: Id
          type: string
        meeting_id:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            Set on a meeting Statisfy's notetaker recorded: its id at GET
            /v1/meetings/{meeting_id}, which links to its transcript
          title: Meeting Id
        one_liner:
          anyOf:
            - type: string
            - type: 'null'
          description: The AI's one-line summary
          title: One Liner
        participants:
          items:
            $ref: '#/components/schemas/Participant'
          title: Participants
          type: array
        sentiment:
          anyOf:
            - enum:
                - negative
                - neutral
                - positive
              type: string
            - type: 'null'
          description: >-
            positive, neutral or negative, as the AI judged it or a person set
            it
          title: Sentiment
        source:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The integration it came from, such as gmail, outlook_mail, zoom,
            gong, slack, zendesk, statisfy (a campaign's send), manual (logged
            in the app) or api (another system pushed it: `pushed.system` names
            it)
          title: Source
        title:
          anyOf:
            - type: string
            - type: 'null'
          title: Title
        type:
          anyOf:
            - enum:
                - email
                - meeting
                - slack
                - teams
                - ticket
                - survey
                - chatter
                - note
                - linkedin
                - marketing_event
              type: string
            - type: 'null'
          description: >-
            email, meeting, slack, teams, ticket (a support ticket), survey,
            chatter (Salesforce Chatter), note (logged in the app), linkedin (a
            LinkedIn conversation) or marketing_event (a form fill, web visit,
            webinar or event)
          title: Type
      required:
        - id
      title: Activity
      type: object
    Participant:
      description: A person on an activity, as every activity API gives them.
      properties:
        email:
          anyOf:
            - type: string
            - type: 'null'
          title: Email
        id:
          description: The person's id
          title: Id
          type: string
        name:
          anyOf:
            - type: string
            - type: 'null'
          title: Name
        type:
          anyOf:
            - enum:
                - user
                - contact
                - vendor
                - digital_worker
              type: string
            - type: 'null'
          description: >-
            user (a teammate), contact, vendor or digital_worker; null when
            unknown
          title: Type
      required:
        - id
      title: Participant
      type: object
  securitySchemes:
    HTTPBearer:
      scheme: bearer
      type: http
      description: >-
        An API key, sent as `Authorization: Bearer stfy_live_…`. See
        [Authentication](/rest-api/authentication) for how to get one and which
        scopes it needs.

````

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