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

# Count outreach emails and what became of them

> Counts the emails your digital workers sent unprompted in a range of days (`filter[sent_at][gte]` and `filter[sent_at][lt]`, YYYY-MM-DD; the last 30 days when left out; at most 400), narrowed by `worker`, `account` or `contact`, as one row or one per `group_by` (worker, week). Rates count only what can be seen: reply_rate over emails whose thread was recorded (reply_tracked), delivered, opened, clicked and dropped over emails with delivery events (delivery_tracked: the company address's), and bounced over the emails a bounce could be seen for (bounce_tracked, which also covers mailbox sends on a recorded thread). held, approved and dismissed count the drafts workers held for review, by when each was drafted.



## OpenAPI

````yaml /api/statisfy-api.openapi.json get /v1/outreach_emails/stats
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/outreach_emails/stats:
    get:
      tags:
        - outreach_emails
      summary: Count outreach emails and what became of them
      description: >-
        Counts the emails your digital workers sent unprompted in a range of
        days (`filter[sent_at][gte]` and `filter[sent_at][lt]`, YYYY-MM-DD; the
        last 30 days when left out; at most 400), narrowed by `worker`,
        `account` or `contact`, as one row or one per `group_by` (worker, week).
        Rates count only what can be seen: reply_rate over emails whose thread
        was recorded (reply_tracked), delivered, opened, clicked and dropped
        over emails with delivery events (delivery_tracked: the company
        address's), and bounced over the emails a bounce could be seen for
        (bounce_tracked, which also covers mailbox sends on a recorded thread).
        held, approved and dismissed count the drafts workers held for review,
        by when each was drafted.
      operationId: outreach_emails_stats
      parameters:
        - description: >-
            worker or week (weeks start Monday, UTC); one row for the whole
            range when left out
          in: query
          name: group_by
          required: false
          schema:
            anyOf:
              - enum:
                  - worker
                  - week
                type: string
              - type: 'null'
            default: null
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/OutreachStats'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    OutreachStats:
      properties:
        data:
          items:
            $ref: '#/components/schemas/OutreachStatsRow'
          title: Data
          type: array
        sent_at_gte:
          description: 'ISO 8601 UTC: the range counted, from'
          title: Sent At Gte
          type: string
        sent_at_lt:
          description: 'ISO 8601 UTC: the range counted, up to'
          title: Sent At Lt
          type: string
      required:
        - sent_at_gte
        - sent_at_lt
        - data
      title: OutreachStats
      type: object
    OutreachStatsRow:
      properties:
        approved:
          description: Held drafts a teammate sent
          title: Approved
          type: integer
        bounce_tracked:
          description: >-
            Sent emails a bounce could be seen for: the base of bounced. Larger
            than delivery_tracked, since a mailbox send's bounce comes back as a
            notice onto its thread even though nothing else about its delivery
            is ever reported
          title: Bounce Tracked
          type: integer
        bounced:
          title: Bounced
          type: integer
        clicked:
          title: Clicked
          type: integer
        delivered:
          title: Delivered
          type: integer
        delivery_tracked:
          description: >-
            Sent emails with delivery events (company address): the base of
            delivered, opened and clicked
          title: Delivery Tracked
          type: integer
        dismissed:
          description: Held drafts a teammate turned down
          title: Dismissed
          type: integer
        dropped:
          title: Dropped
          type: integer
        held:
          description: >-
            Drafts the worker held for review that still wait, by when each was
            drafted
          title: Held
          type: integer
        median_hours_to_reply:
          anyOf:
            - type: number
            - type: 'null'
          title: Median Hours To Reply
        opened:
          title: Opened
          type: integer
        opted_out:
          title: Opted Out
          type: integer
        replied:
          title: Replied
          type: integer
        reply_rate:
          anyOf:
            - type: number
            - type: 'null'
          description: replied / reply_tracked; null when nothing was tracked
          title: Reply Rate
        reply_tracked:
          description: 'Sent emails whose thread was recorded: the reply rate''s base'
          title: Reply Tracked
          type: integer
        sent:
          title: Sent
          type: integer
        spam_reports:
          title: Spam Reports
          type: integer
        unknown:
          description: Emails the mail provider never confirmed
          title: Unknown
          type: integer
        week:
          anyOf:
            - type: string
            - type: 'null'
          description: 'With group_by=week: the week''s Monday, YYYY-MM-DD'
          title: Week
        worker:
          anyOf:
            - $ref: '#/components/schemas/OutreachWorker'
            - type: 'null'
          description: With group_by=worker
      required:
        - sent
        - unknown
        - reply_tracked
        - replied
        - delivery_tracked
        - bounce_tracked
        - delivered
        - opened
        - clicked
        - bounced
        - dropped
        - spam_reports
        - opted_out
        - held
        - approved
        - dismissed
      title: OutreachStatsRow
      type: object
    OutreachWorker:
      properties:
        id:
          description: The digital worker's id, from GET /v1/digital_workers
          title: Id
          type: string
        name:
          anyOf:
            - type: string
            - type: 'null'
          description: Null when the worker was deleted
          title: Name
      required:
        - id
      title: OutreachWorker
      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.