> ## Documentation Index > Fetch the complete documentation index at: https://docs.formo.so/llms.txt > Use this file to discover all available pages before exploring further. # Get User Frequency > Distribution of users by visit count over the selected window. Returns how many users visited 1, 2, 3+ times in the selected window - the data behind the dashboard's frequency histogram. ## OpenAPI ````yaml GET /v0/frequency openapi: 3.1.0 info: title: Formo Public API description: >- REST API for managing Formo projects, analytics, alerts, boards, charts, contracts, segments, and AI chat. **Auth.** All endpoints require a workspace API key with the appropriate scopes (see `x-api-scopes`). **Response shape.** Successful responses return the resource directly (or `{ data: [...], total, page, size, has_more }` for paginated lists). HTTP status carries success/failure; there is no envelope wrapping success bodies. **Errors.** Every non-2xx response uses the `Error` envelope: `{ error: { code, message, doc_url, param?, details? } }`. Branch on the machine-readable `code` (see `ErrorCode` enum) and follow `doc_url` to the matching section of the [errors reference](https://docs.formo.so/api/errors). **Idempotency.** Pass an `Idempotency-Key` header on POST/PUT/PATCH/DELETE to make retries safe; the response is cached for 24 h and replayed on duplicate keys. version: 0.1.0 contact: name: Formo url: https://formo.so servers: - url: https://api.formo.so description: API Server (boards, alerts, contracts, segments, profiles, query, import) - url: https://events.formo.so description: Events Server (event ingestion) security: - WorkspaceApiKey: [] tags: - name: Alerts description: Manage project alerts and notifications - name: Boards description: Manage dashboard boards - name: Charts description: Manage charts within boards - name: Contracts description: Manage blockchain contract monitoring - name: Segments description: Manage user segments - name: Profiles description: Wallet profiles and import - name: Query description: >- Execute SQL queries and call pre-built analytics endpoints (KPIs, top pages, lifecycle, retention, revenue). Requires the query:read scope. - name: Events description: Event ingestion API (events.formo.so) paths: /v0/frequency: get: tags: - Query summary: Get visit-frequency distribution operationId: getAnalyticsFrequency parameters: - $ref: '#/components/parameters/AnalyticsDateFrom' - $ref: '#/components/parameters/AnalyticsDateTo' - $ref: '#/components/parameters/AnalyticsFilters' - $ref: '#/components/parameters/AnalyticsIncludePreviousPeriod' - $ref: '#/components/parameters/AnalyticsBehaviorFilters' - $ref: '#/components/parameters/AnalyticsSourceFilter' - $ref: '#/components/parameters/AnalyticsChannelFilter' responses: '200': description: Visit frequency distribution content: application/json: schema: $ref: '#/components/schemas/AnalyticsResponse' example: meta: - name: project_id type: String - name: session_bucket type: String - name: user_count type: UInt64 - name: avg_session_per_user type: Float64 data: - project_id: proj_abc session_bucket: 1 session user_count: 412 avg_session_per_user: 1 - project_id: proj_abc session_bucket: 2 - 10 sessions user_count: 287 avg_session_per_user: 4.6 - project_id: proj_abc session_bucket: 10 - 30 sessions user_count: 76 avg_session_per_user: 16.2 - project_id: proj_abc session_bucket: 30 - 50 sessions user_count: 18 avg_session_per_user: 38.4 - project_id: proj_abc session_bucket: '> 50 sessions' user_count: 5 avg_session_per_user: 84 rows: 5 rows_before_limit_at_least: 5 '401': description: Invalid API key content: application/json: schema: $ref: '#/components/schemas/RestApiError' '403': description: Insufficient permissions content: application/json: schema: $ref: '#/components/schemas/RestApiError' components: parameters: AnalyticsDateFrom: name: date_from in: query schema: type: string format: date description: Inclusive start date (YYYY-MM-DD). Defaults to 7 days before date_to. AnalyticsDateTo: name: date_to in: query schema: type: string format: date description: Inclusive end date (YYYY-MM-DD). Defaults to today. AnalyticsFilters: name: filters in: query description: >- Array of filter conditions, JSON-encoded in the query string. Entries use `{ field, op, value }` and are combined with implicit AND. For example, filter traffic referred by Google with `[{"field":"referrer","op":"contains","value":"google"}]`, or filter a page with `[{"field":"page","op":"eq","value":"/pricing"}]`. For `in` / `nin`, pass a non-empty array value such as `["chrome","firefox"]` or a pipe-delimited string such as `"chrome|firefox"`. Array string members cannot contain a literal `|`, which is reserved as the Tinybird membership separator. Optional one-level nested `filters` use the same canonical envelope and membership rule. On the user-aggregate endpoints (lifecycle, frequency) the same array also carries profile-family entries: profile metrics (net_worth_usd, volume, revenue, points), social identity fields, a lifecycle entry ({"field":"lifecycle","op":"in","value":"New|Power user"}), and resource entries using the stable fields chains.balance, apps.balance, tokens.balance, and labels.value with named qualifier properties (chain_id, app_id, token_address, scope, tag_id). The retired per-family parameters (socials, chain_filters, app_filters, token_filters, label_filters, profile_filters, lifecycle_filter) are rejected. schema: type: string example: '[{"field":"referrer","op":"contains","value":"google"}]' AnalyticsIncludePreviousPeriod: name: include_previous_period in: query schema: type: boolean description: >- When `true`, returns both current and previous period metrics for week-over-week comparison. The previous period is non-overlapping and equal in length to the current range. AnalyticsBehaviorFilters: name: behavior_filters in: query description: >- JSON array filtering users by event-based behavior with counts and either an absolute date range or a window relative to the user's first event. Each entry is `{ event, op, times, date_from?, date_to?, event_type?, relative_to?, window? }`. When `relative_to: "first_seen"` is set, the matching events must occur within `window.value` `window.unit` (`hour` | `day`) after the user's first event; `date_from`/`date_to` are ignored. `event_type` narrows matching to a specific event-type column (`page`, `connect`, `disconnect`, `chain`, `signature`, `transaction`, `track`, `decoded_log`, `detect`, `identify`); for `track` and `decoded_log` the `event` field is the named identifier; for other types only the `type` column is matched. schema: type: string example: >- [{"event":"swap","event_type":"track","op":"gte","times":1,"relative_to":"first_seen","window":{"value":24,"unit":"hour"}}] AnalyticsSourceFilter: name: source_filter in: query description: >- JSON array filtering users by raw event source. Entries use the canonical envelope and `field` must be `source`. Distinct from `channel_filter`, which matches the classified acquisition channel. schema: type: string example: '[{"field":"source","op":"in","value":"web|mobile"}]' AnalyticsChannelFilter: name: channel_filter in: query description: >- JSON array filtering users by classified acquisition channel. Entries use the canonical envelope and `field` must be `channel_type`. Distinct from `source_filter`, which matches the raw SDK source. schema: type: string example: >- [{"field":"channel_type","op":"in","value":"Organic Search|Paid Social"}] schemas: AnalyticsResponse: type: object description: >- Analytics endpoint response. The `data` array contains the rows; the exact row shape depends on the endpoint. `meta` carries column type information for rendering, `rows` is the row count, and `statistics` holds query timing metadata. properties: data: type: array items: type: object additionalProperties: true meta: type: array items: type: object properties: name: type: string type: type: string rows: type: integer rows_before_limit_at_least: type: integer statistics: type: object additionalProperties: true RestApiError: $ref: '#/components/schemas/Error' description: >- Deprecated alias for `Error`. Existing endpoint specs reference this name; new specs should reference `Error` directly. Error: type: object description: >- Standard error envelope returned by every public API endpoint for any non-2xx response. The HTTP status code carries success/failure; the body provides a machine-readable `code`, a human-readable `message`, and a `doc_url` pointing at the matching section of the docs so agents can fetch context on the fly. properties: error: type: object required: - code - message - doc_url properties: code: $ref: '#/components/schemas/ErrorCode' message: type: string description: >- Human-readable error description. Wording may change between releases, so branch on `code`, not `message`. doc_url: type: string format: uri description: >- Link to the matching section of the errors reference at https://docs.formo.so/api/errors. param: type: string description: >- When the error pertains to a specific request field, the dotted path to that field (e.g. `body.trigger_filters.0.value`). details: type: object additionalProperties: true description: >- Code-specific extra context. For `INVALID_VALIDATION_REQUEST` this is a `{ fieldPath: message }` map of every Zod validation failure. required: - error ErrorCode: type: string description: >- Stable, enumerated error codes. New codes may be added in any release; clients should treat unknown codes as the closest matching HTTP status family. enum: - INTERNAL_SERVER_ERROR - INVALID_VALIDATION_REQUEST - UNAUTHORIZED - BAD_REQUEST - FORBIDDEN - NOT_FOUND - CONFLICT - INVALID_CHAIN_ID - CONTEXT_LIMIT_EXCEEDED - SERVICE_UNAVAILABLE - TOO_MANY_REQUESTS - IDEMPOTENCY_IN_PROGRESS - INVALID_IDEMPOTENCY_KEY securitySchemes: WorkspaceApiKey: type: http scheme: bearer description: >- Workspace API key (e.g. `formo_xxx`). Create one in the Formo dashboard under Team Settings > API. ````