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

# Integration health, per source and subtype

> The app's Integrations > View monitoring table: one row per (source, subtype) the workspace syncs, whether scheduled or started by events, with its status over the last 5 runs (healthy, degraded, failed, never_ran, disabled), the failure streak, whether it stopped or fell behind its schedule (`stale_status`), when it last succeeded and failed, its last run with its error, and its schedule: the cadence and the layer it comes from (the workspace's own, the integration's built-in, or Statisfy's default). Not paged: one row per sync. For a row's run history, GET /v1/integrations/{integration_key}/runs?subtype={subtype}. Read only.



## OpenAPI

````yaml /api/statisfy-api.openapi.json get /v1/integrations/monitoring
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/integrations/monitoring:
    get:
      tags:
        - integrations
      summary: Integration health, per source and subtype
      description: >-
        The app's Integrations > View monitoring table: one row per (source,
        subtype) the workspace syncs, whether scheduled or started by events,
        with its status over the last 5 runs (healthy, degraded, failed,
        never_ran, disabled), the failure streak, whether it stopped or fell
        behind its schedule (`stale_status`), when it last succeeded and failed,
        its last run with its error, and its schedule: the cadence and the layer
        it comes from (the workspace's own, the integration's built-in, or
        Statisfy's default). Not paged: one row per sync. For a row's run
        history, GET /v1/integrations/{integration_key}/runs?subtype={subtype}.
        Read only.
      operationId: integrations_monitoring
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IntegrationMonitoringResponse'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    IntegrationMonitoringResponse:
      properties:
        data:
          items:
            $ref: '#/components/schemas/IntegrationHealth'
          title: Data
          type: array
      required:
        - data
      title: IntegrationMonitoringResponse
      type: object
    IntegrationHealth:
      properties:
        enabled:
          description: >-
            False when it has no run in 30 days, no workspace schedule, and is
            not expected to run
          title: Enabled
          type: boolean
        failure_streak:
          description: >-
            Failed runs in a row, counting back from the newest finished run (at
            most 5); 0 when it succeeded
          title: Failure Streak
          type: integer
        integration_key:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The /v1/integrations key the source belongs to, for its runs and
            schedule; null for a job no integration owns (flows, CRM write-back,
            CSV imports)
          title: Integration Key
        is_scheduled:
          description: >-
            True for a sync the scheduler runs on a cadence; false for a job
            started by events or by hand
          title: Is Scheduled
          type: boolean
        last_failure_at:
          anyOf:
            - format: date-time
              type: string
            - type: 'null'
          description: When its newest failed run in the last 30 days started
          title: Last Failure At
        last_run:
          anyOf:
            - $ref: '#/components/schemas/MonitoringRun'
            - type: 'null'
          description: Its newest run in the last 30 days; null when none
        last_success_at:
          anyOf:
            - format: date-time
              type: string
            - type: 'null'
          description: When its newest completed run in the last 30 days started
          title: Last Success At
        schedule:
          $ref: '#/components/schemas/MonitoringSchedule'
        source:
          description: The sync's source, e.g. SALESFORCE, HUBSPOT, SNOWFLAKE, HANDLE_FLOWS
          title: Source
          type: string
        stale_status:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            Set when it was expected to run and did not: e.g. 'overdue (30h /
            24h)', 'stopped (0 runs)', 'configured, never ran', 'not
            dispatchable (subtype not in catalog)'. Null when on schedule,
            started on demand, disabled, or failing (a failure shows in
            `status`), as in the daily monitoring alert
          title: Stale Status
        status:
          description: >-
            Over its last 5 runs: healthy (none failed), degraded (some failed),
            failed (all failed). never_ran: expected to run (connected, with a
            schedule) but no run in 30 days. disabled: no run in 30 days and not
            expected to run. A run still going counts for neither
          enum:
            - healthy
            - degraded
            - failed
            - disabled
            - never_ran
          title: Status
          type: string
        subtype:
          description: >-
            The job subtype, e.g. default, delta, product_usage,
            account_custom_fields
          title: Subtype
          type: string
      required:
        - source
        - subtype
        - integration_key
        - status
        - enabled
        - is_scheduled
        - failure_streak
        - stale_status
        - last_success_at
        - last_failure_at
        - last_run
        - schedule
      title: IntegrationHealth
      type: object
    MonitoringRun:
      properties:
        duration_seconds:
          anyOf:
            - type: number
            - type: 'null'
          title: Duration Seconds
        ended_at:
          anyOf:
            - format: date-time
              type: string
            - type: 'null'
          title: Ended At
        id:
          description: The run's id, as /v1/integrations/{key}/runs/{run_id} takes it
          title: Id
          type: integer
        message:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The job's status text, such as a failed run's error, masked as a
            run's `message` is on /v1/integrations/{key}/runs; null when the job
            recorded none
          title: Message
        run_type:
          description: manual, bootstrap, periodic or unknown
          title: Run Type
          type: string
        started_at:
          format: date-time
          title: Started At
          type: string
        status:
          anyOf:
            - enum:
                - in_progress
                - completed
                - failed
              type: string
            - type: string
          description: in_progress, completed or failed
          title: Status
      required:
        - id
        - status
        - run_type
        - started_at
        - ended_at
        - duration_seconds
        - message
      title: MonitoringRun
      type: object
    MonitoringSchedule:
      properties:
        cadence:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The cadence it runs on: hourly, two_hours, four_hours, six_hours,
            twelve_hours, daily, weekly, semimonthly or monthly; null when the
            layer sets none. Null: no layer sets one
          title: Cadence
        interval_minutes:
          anyOf:
            - type: integer
            - type: 'null'
          description: >-
            How often it runs, in minutes, when `cadence` does not name it: a
            workspace schedule of 2880 minutes (two days) reads `weekly`. Null
            when `cadence` is the interval
          title: Interval Minutes
        layer:
          description: >-
            Where `cadence` comes from, highest first: db (the workspace's own
            schedule), hardcoded (the integration's built-in cadence), default
            (Statisfy's global default); none when no layer sets one
          enum:
            - db
            - hardcoded
            - default
            - none
          title: Layer
          type: string
        layers:
          $ref: '#/components/schemas/MonitoringScheduleLayers'
        weekly_detail:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            A weekly workspace schedule's day, time and timezone, e.g. 'Mon
            14:00 America/Los_Angeles'
          title: Weekly Detail
      required:
        - cadence
        - layer
        - weekly_detail
        - interval_minutes
        - layers
      title: MonitoringSchedule
      type: object
    MonitoringScheduleLayers:
      properties:
        db:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The workspace's own schedule (set in the app or the API): hourly,
            two_hours, four_hours, six_hours, twelve_hours, daily, weekly,
            semimonthly or monthly; null when the layer sets none
          title: Db
        default:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            Statisfy's global default cadence, for a scheduled sync: hourly,
            two_hours, four_hours, six_hours, twelve_hours, daily, weekly,
            semimonthly or monthly; null when the layer sets none
          title: Default
        hardcoded:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The integration's own built-in cadence: hourly, two_hours,
            four_hours, six_hours, twelve_hours, daily, weekly, semimonthly or
            monthly; null when the layer sets none
          title: Hardcoded
      required:
        - default
        - hardcoded
        - db
      title: MonitoringScheduleLayers
      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.