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

# Get Org Cues Issue Flow

> Daily raised/resolved cues with the end-of-day open backlog, over ``[start, end]`` inclusive.

Each point is ``{date, raised, resolved, open}``: ``raised`` and ``resolved`` count the cues that
opened and closed that day, and ``open`` is the backlog standing at the day's end. The series
holds ``open(day) = open(day-1) + raised - resolved``; cues opened before ``start`` are not
attributed to day one but form the opening backlog the first day starts from.

Derived by folding each cue's fact stream, so a cue reopened and reclosed counts each time and a
**discarded** cue counts as resolved — an operator write-off has left the backlog just as a
genuine resolution has. Days are UTC calendar days. The range spans at most
``MAX_ISSUE_FLOW_SPAN_DAYS`` days — one point per day, so an unbounded range would build an
unbounded response.

The org's existence is already guaranteed by ``organization_access_required`` (the token's member
must belong to ``org_id``), so no separate lookup is needed.



## OpenAPI

````yaml https://app.podero.com/api/partners/v2.0/openapi.json get /api/partners/v2.0/org/{org_id}/cues/issue-flow
openapi: 3.1.0
info:
  title: Podero Partner API
  version: '2.0'
  description: >-
    This API provides a unified interaction point for Podero's partner
    companies.


    The goal of this API is to give partners easily integratable endpoints that
    don't require extensive software

    development. For this reason, the endpoints focus around user and device
    management, setting of preferences

    and high level device controls.


    While direct control of devices is implemented for special use cases such as
    pause power, we abstract away low level

    direct device steering so developers and partners can focus on delivering
    maximum value to end users.
  termsOfService: https://www.podero.com/terms-and-conditions
servers: []
security: []
paths:
  /api/partners/v2.0/org/{org_id}/cues/issue-flow:
    get:
      tags:
        - Organization
      summary: Get Org Cues Issue Flow
      description: >-
        Daily raised/resolved cues with the end-of-day open backlog, over
        ``[start, end]`` inclusive.


        Each point is ``{date, raised, resolved, open}``: ``raised`` and
        ``resolved`` count the cues that

        opened and closed that day, and ``open`` is the backlog standing at the
        day's end. The series

        holds ``open(day) = open(day-1) + raised - resolved``; cues opened
        before ``start`` are not

        attributed to day one but form the opening backlog the first day starts
        from.


        Derived by folding each cue's fact stream, so a cue reopened and
        reclosed counts each time and a

        **discarded** cue counts as resolved — an operator write-off has left
        the backlog just as a

        genuine resolution has. Days are UTC calendar days. The range spans at
        most

        ``MAX_ISSUE_FLOW_SPAN_DAYS`` days — one point per day, so an unbounded
        range would build an

        unbounded response.


        The org's existence is already guaranteed by
        ``organization_access_required`` (the token's member

        must belong to ``org_id``), so no separate lookup is needed.
      operationId: integrations_api_api_v2_organizations_router_get_org_cues_issue_flow
      parameters:
        - in: path
          name: org_id
          schema:
            description: The organization ID of the user's organization
            format: uuid
            title: Org Id
            type: string
          required: true
          description: The organization ID of the user's organization
        - in: query
          name: start
          schema:
            description: First day of the series (inclusive), UTC
            format: date
            title: Start
            type: string
          required: true
          description: First day of the series (inclusive), UTC
        - in: query
          name: end
          schema:
            description: Last day of the series (inclusive), UTC
            format: date
            title: End
            type: string
          required: true
          description: Last day of the series (inclusive), UTC
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                items:
                  $ref: '#/components/schemas/IssueFlowPointOutput'
                title: Response
                type: array
      security:
        - OAuth2: []
components:
  schemas:
    IssueFlowPointOutput:
      description: >-
        One day of the issue-flow series. ``open`` is the backlog standing at
        the day's end;

        ``raised``/``resolved`` are that day's cue opens and closes (a discarded
        cue counts as resolved).
      properties:
        date:
          format: date
          title: Date
          type: string
        raised:
          title: Raised
          type: integer
        resolved:
          title: Resolved
          type: integer
        open:
          title: Open
          type: integer
      required:
        - date
        - raised
        - resolved
        - open
      title: IssueFlowPointOutput
      type: object
  securitySchemes:
    OAuth2:
      type: oauth2
      flows:
        password:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}
        clientCredentials:
          tokenUrl: /api/partners/v2.0/auth/token
          scopes: {}

````