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

> Cumulative members joined and operational devices connected per day, over ``[start, end]``
inclusive. Each point is ``{date, users, devices}`` — the running totals standing at that UTC
day's end.

Survivorship parity with the client's ``connectedToDate`` fold: it counts only active members
(keyed on ``date_joined``) and non-soft-deleted devices (keyed on ``created_at``), so the curve
is up-only and matches today's numbers. Entities stamped before ``start`` form the day-one
baseline; entities stamped after ``end`` are excluded. It is not yet churn-aware — a later step,
and the only place a churn-aware count can come from.

Days are UTC calendar days. The range spans at most ``MAX_GROWTH_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}/growth
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}/growth:
    get:
      tags:
        - Organization
      summary: Get Org Growth
      description: >-
        Cumulative members joined and operational devices connected per day,
        over ``[start, end]``

        inclusive. Each point is ``{date, users, devices}`` — the running totals
        standing at that UTC

        day's end.


        Survivorship parity with the client's ``connectedToDate`` fold: it
        counts only active members

        (keyed on ``date_joined``) and non-soft-deleted devices (keyed on
        ``created_at``), so the curve

        is up-only and matches today's numbers. Entities stamped before
        ``start`` form the day-one

        baseline; entities stamped after ``end`` are excluded. It is not yet
        churn-aware — a later step,

        and the only place a churn-aware count can come from.


        Days are UTC calendar days. The range spans at most
        ``MAX_GROWTH_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_growth
      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/GrowthPointOutput'
                title: Response
                type: array
      security:
        - OAuth2: []
components:
  schemas:
    GrowthPointOutput:
      description: >-
        One day of the growth series: cumulative members joined and operational
        devices connected,

        standing at that day's end (survivorship-parity, so up-only).
      properties:
        date:
          format: date
          title: Date
          type: string
        users:
          title: Users
          type: integer
        devices:
          title: Devices
          type: integer
      required:
        - date
        - users
        - devices
      title: GrowthPointOutput
      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: {}

````