# Per-application audience growth

Open **Developer Apps → View growth** for a 30- or 90-day chart. No external
analytics service or tracking script is required in the integrating application.

Read the same aggregate data with an owner-delegated `applications:read` credential:

```http
GET /api/developer/v1/applications?action=growth&client_id=YOUR_CLIENT_ID&days=30
Host: hybrid-id.com
Authorization: Bearer YOUR_DEVELOPER_CREDENTIAL
```

The authenticated owner can also use the portal's read-only
`GET /api/identity/applications?action=growth&client_id=...&days=30` endpoint.
Neither endpoint requires a fresh MFA step. Credentials cannot read another
owner's app. Disabled apps retain readable history. No individual IDs, emails,
profile fields or credentials appear in the response.

The response envelope is `{ "success": true, "data": ... }`. Data has `client_id`,
`days`, `timezone: "UTC"`, `as_of` (ISO timestamp), `users_history_start` (UTC date),
`guests_status` (`available` or `unavailable`) and exactly 30 or 90 ascending
`points`, each containing `date`, `hybrid_id_users` and `unclaimed_guests`.
See the [ApplicationGrowth schema](https://hybrid-id.com/integrations/developer-openapi.json).

- **Hybrid ID users:** cumulative distinct identities issued an app token, including
  new and existing Hybrid ID accounts. Repeat logins do not increase this total.
  This is not a count of newly created Hybrid ID accounts or monthly active users.
- **Unclaimed guests:** app-scoped guest profiles created on or before that date,
  minus those explicitly linked by that date. It can go down. Claiming multiple
  guests into one existing user does not create additional unique users.
- Past dates show end-of-day totals; today is partial. Days without changes carry
  the previous total. Both series use UTC and a shared linear chart scale.
- Existing user records lack first-sign-in timestamps: the initial baseline keeps
  the current total. Dates before `users_history_start` are `null`, not zero or
  interpolated. New unique users are recorded durably on sign-in, whether anyone
  opens the chart or not. Guest history is reconstructed from authoritative native
  creation/link timestamps, so existing guest history is available immediately.
- A guest-service outage returns `guests_status: "unavailable"` and null guest
  values while preserving available user totals. Retry on explicit refresh or
  reopening; never interpret null as zero. No quota or billing rules change.

Invalid periods return 400, invalid credentials 401, insufficient scope 403,
non-owned/missing apps 404, throttling 429, unavailable provider 503. Existing
exact-owner developer exceptions remain unchanged. Sign-in uniqueness and guest
history are separate sources, not a conversion funnel or a billing ledger.
