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

# Run the Pendo NPS survey job now

> Starts the NPS survey job (202), as Run now of the survey subtype does on the app's monitoring page. The job has no saved query: it reads the survey settings of GET /v1/integrations/pendo/config. With no dates, the window starts at the earlier of 8 days ago and 1 day before the start of the last completed run, and never more than 90 days back. `start_date` and `end_date` (YYYY-MM-DD, sent together, at most 90 days apart) read that window again: a response that is already stored is skipped. When a run of the job is already in flight, nothing starts and that run comes back (200, already_running). A 409 means the CRM has not synced yet, which every non-CRM integration waits for, or that Pendo has no saved config (`version` 0), where the job would read nothing: save the survey settings first. Poll GET /v1/integrations/pendo/runs/{run_id} for the outcome.



## OpenAPI

````yaml /api/statisfy-api.openapi.json post /v1/integrations/pendo/surveys/runs
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/pendo/surveys/runs:
    post:
      tags:
        - integrations
      summary: Run the Pendo NPS survey job now
      description: >-
        Starts the NPS survey job (202), as Run now of the survey subtype does
        on the app's monitoring page. The job has no saved query: it reads the
        survey settings of GET /v1/integrations/pendo/config. With no dates, the
        window starts at the earlier of 8 days ago and 1 day before the start of
        the last completed run, and never more than 90 days back. `start_date`
        and `end_date` (YYYY-MM-DD, sent together, at most 90 days apart) read
        that window again: a response that is already stored is skipped. When a
        run of the job is already in flight, nothing starts and that run comes
        back (200, already_running). A 409 means the CRM has not synced yet,
        which every non-CRM integration waits for, or that Pendo has no saved
        config (`version` 0), where the job would read nothing: save the survey
        settings first. Poll GET /v1/integrations/pendo/runs/{run_id} for the
        outcome.
      operationId: integrations_pendo_start_surveys_run
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: false
              properties:
                end_date:
                  anyOf:
                    - type: string
                    - type: 'null'
                  default: null
                  description: Read responses to this day (YYYY-MM-DD)
                  title: End Date
                start_date:
                  anyOf:
                    - type: string
                    - type: 'null'
                  default: null
                  description: >-
                    Read responses from this day (YYYY-MM-DD). Send it with
                    end_date
                  title: Start Date
              type: object
        required: false
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IntegrationRunStarted'
          description: Successful Response
        '202':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IntegrationRunStarted'
          description: Accepted
      security:
        - HTTPBearer: []
components:
  schemas:
    IntegrationRunStarted:
      properties:
        message:
          title: Message
          type: string
        run_id:
          description: The new run, or the one already in flight
          title: Run Id
          type: integer
        started_at:
          format: date-time
          title: Started At
          type: string
        status:
          description: >-
            scheduled (202): the run starts now; already_running (200): a run of
            this subtype is in flight
          enum:
            - scheduled
            - already_running
          title: Status
          type: string
      required:
        - status
        - run_id
        - started_at
        - message
      title: IntegrationRunStarted
      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.